Re: Bug in reboot when using scsi or virtio
Stuart Sheldon wrote: Thanks Avi, Should I test against the daily to verify? I've reproduced it locally and verified the fix, but of course additional confirmation is welcome. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bug in reboot when using scsi or virtio
2008/8/30 Avi Kivity <[EMAIL PROTECTED]>: > Stuart Sheldon wrote: >> >> Guest boots and runs fine, but does not see boot device on guest reboot >> if if=scsi or if=virtio is used. >> >> Boot Screen after reboot: >> Booting from Hard Disk... >> Boot from Hard Disk failed: could not read boot disk >> ... More failed boot devices that shouldn't boot anyway... >> FATAL: No bootable device >> >> > > This was caused by the extboot rom writing into itself, thus failing > checksum on the next reboot. I fixed this for kvm-75 by reloading the rom > on reset. Many many thanks! /Henrik Holst -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bug in reboot when using scsi or virtio
Thanks Avi, Should I test against the daily to verify? Stu Avi Kivity wrote: Stuart Sheldon wrote: Guest boots and runs fine, but does not see boot device on guest reboot if if=scsi or if=virtio is used. Boot Screen after reboot: Booting from Hard Disk... Boot from Hard Disk failed: could not read boot disk ... More failed boot devices that shouldn't boot anyway... FATAL: No bootable device This was caused by the extboot rom writing into itself, thus failing checksum on the next reboot. I fixed this for kvm-75 by reloading the rom on reset. -- Randomly Generated Fortune Tag: Many pages make a thick book. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bug in reboot when using scsi or virtio
Stuart Sheldon wrote: Guest boots and runs fine, but does not see boot device on guest reboot if if=scsi or if=virtio is used. Boot Screen after reboot: Booting from Hard Disk... Boot from Hard Disk failed: could not read boot disk ... More failed boot devices that shouldn't boot anyway... FATAL: No bootable device This was caused by the extboot rom writing into itself, thus failing checksum on the next reboot. I fixed this for kvm-75 by reloading the rom on reset. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bug in reboot when using scsi or virtio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Brian,
The last version I had been running is kvm-70. After copying the
extboot.bin from that version over to the share/kvm directory, the
system rebooted several times in scsi and virtio mode.
Please let me know if you would like me to build any additional versions
for testing.
Stu
Brian Jackson wrote:
> Can you try using the extboot.bin from the last version that worked for
> you?
>
>
>
> On Aug 29, 2008, at 1:43 PM, Stuart Sheldon wrote:
>
> Guest boots and runs fine, but does not see boot device on guest reboot
> if if=scsi or if=virtio is used.
>
> Boot Screen after reboot:
> Booting from Hard Disk...
> Boot from Hard Disk failed: could not read boot disk
> ... More failed boot devices that shouldn't boot anyway...
> FATAL: No bootable device
>
> CPU: Intel(R) Pentium(R) D CPU 3.00GHz
> KVM: kvm-74
> Host: Debian Lenny - Vanilla 2.6.26.2
> Guest: Debian Lenny - Vanilla 2.6.26.2
> Command: {
> export QEMU_AUDIO_DRV=oss
> qemu-system-x86_64 \
>-m 1024 \
>-std-vga \
>-soundhw es1370 \
>-name 'Debian Vitrual Host' \
>-net nic,macaddr=52:54:00:12:31:02 \
>-drive file=/projects/stu/kvm-drives/debian.img,if=scsi,boot=on \
>-net tap,ifname=tap2 -daemonize
> }
>
> Still exists with -no-kvm-* combinations.
> Software not built to run without kvm
>
> To reproduce, just bring the guest host up with either a if=scsi or
> if=virtio.
>
> Stu
>
>
- --
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
- --
Open up the window Let some air into this room I think I'm almost
chokin' From the smell of stale perfume And that cigarette you're
smoking 'Bout scared me half to death Open up the window, sucker
Let me catch my breath
-- Three Dog Night - "Mama Told Me Not to Come - Lyrics"
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAki4aMIACgkQK69Y+xPZrWZTHACfbeN8qlgVAIj+gK7l0eJ/qKce
RgkAn2tCIbkwpy2H2BZZ32H+PweAumB5
=1uc3
-END PGP SIGNATURE-
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bug in reboot when using scsi or virtio
Can you try using the extboot.bin from the last version that worked
for you?
On Aug 29, 2008, at 1:43 PM, Stuart Sheldon wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guest boots and runs fine, but does not see boot device on guest
reboot
if if=scsi or if=virtio is used.
Boot Screen after reboot:
Booting from Hard Disk...
Boot from Hard Disk failed: could not read boot disk
... More failed boot devices that shouldn't boot anyway...
FATAL: No bootable device
CPU: Intel(R) Pentium(R) D CPU 3.00GHz
KVM: kvm-74
Host: Debian Lenny - Vanilla 2.6.26.2
Guest: Debian Lenny - Vanilla 2.6.26.2
Command: {
export QEMU_AUDIO_DRV=oss
qemu-system-x86_64 \
-m 1024 \
-std-vga \
-soundhw es1370 \
-name 'Debian Vitrual Host' \
-net nic,macaddr=52:54:00:12:31:02 \
-drive file=/projects/stu/kvm-drives/
debian.img,if=scsi,boot=on \
-net tap,ifname=tap2 -daemonize
}
Still exists with -no-kvm-* combinations.
Software not built to run without kvm
To reproduce, just bring the guest host up with either a if=scsi or
if=virtio.
Stu
- --
If you took all the girls I knew When I was single And brought
them all together for one night I know theyd never match My sweet
imagination And everything looks worse in black and white
-- Paul Simon - "Kodachrome Lyrics"
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAki4Q24ACgkQK69Y+xPZrWbD3QCghTlNiadqbtdQpG3y/S5z/8Dz
VoQAoIQbJDXVbnjeN3jZW1kcRT86q/UI
=wp2/
-END PGP SIGNATURE-
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Bug in reboot when using scsi or virtio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guest boots and runs fine, but does not see boot device on guest reboot
if if=scsi or if=virtio is used.
Boot Screen after reboot:
Booting from Hard Disk...
Boot from Hard Disk failed: could not read boot disk
... More failed boot devices that shouldn't boot anyway...
FATAL: No bootable device
CPU: Intel(R) Pentium(R) D CPU 3.00GHz
KVM: kvm-74
Host: Debian Lenny - Vanilla 2.6.26.2
Guest: Debian Lenny - Vanilla 2.6.26.2
Command: {
export QEMU_AUDIO_DRV=oss
qemu-system-x86_64 \
-m 1024 \
-std-vga \
-soundhw es1370 \
-name 'Debian Vitrual Host' \
-net nic,macaddr=52:54:00:12:31:02 \
-drive file=/projects/stu/kvm-drives/debian.img,if=scsi,boot=on \
-net tap,ifname=tap2 -daemonize
}
Still exists with -no-kvm-* combinations.
Software not built to run without kvm
To reproduce, just bring the guest host up with either a if=scsi or
if=virtio.
Stu
- --
If you took all the girls I knew When I was single And brought
them all together for one night I know theyd never match My sweet
imagination And everything looks worse in black and white
-- Paul Simon - "Kodachrome Lyrics"
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAki4Q24ACgkQK69Y+xPZrWbD3QCghTlNiadqbtdQpG3y/S5z/8Dz
VoQAoIQbJDXVbnjeN3jZW1kcRT86q/UI
=wp2/
-END PGP SIGNATURE-
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
