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 "un
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
>>
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 n
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
-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
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 Sc
-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
