2008/7/28 Henrik Holst <[EMAIL PROTECTED]>: > 2008/7/28 Anthony Liguori <[EMAIL PROTECTED]>: >> Henrik Holst wrote: >>> >>> There is a boot regression in kvm-72: >>> >>> scsi and virtio images will not survive a "reboot" from within the >>> guest. Only drives with if=ide survives a rebooting of the guest. >>> >>> That is, this will create a guest that will survive any number of reboots: >>> qemu-system-x86_64 -M -drive file=a,if=ide,media=disk,boot=on -boot c >>> >>> While this will only survive the first boot: >>> qemu-system-x86_64 -M -drive file=a,if=scsi,media=disk,boot=on -boot c >>> OR >>> qemu-system-x86_64 -M -drive file=a,if=virtio,media=disk,boot=on -boot >>> c >>> >> >> What does "survive" mean? > > survive means that the drive is available after the guest has > rebooted. If we set if=virtio and start a guest everything is working > just fine. Then we type "reboot" in the guest and the guest reboots. > Now we halt in bios since the bios cannot find any bootable devices > anymore. If we use if=ide the bios will find the bootable devices just > like on kvm-71 and the guest simply starts again like on normal > hardware.
Since this probably is due to something in qemu it would be great if the release-log to kvm could include towards which revision of the qemu svn repository that was merged. Or am I to understand that the merge was performed on the same day as the new kvm release was released? I'm thinking of this line: - merge qemu-svn That way I could myself begin to hunt down the culprit patch to qemu much more easily. Also the qemu version in kvm seams to contain some internal patches? I noted that -drive has an "boot" option (in vl.c) in kvm which is not present in qemu-svn (atleast not in trunk). > >> >>> Also the extboot work done by H. Peter Anvin finally makes the newer >>> isolinux menus to work but the older isolinux (for example the >>> installer to ubuntu 7.10) >> >> Ubuntu doesn't use isolinux, it uses gfxboot. Older versions of gfxboot are >> known to be broken with KVM on Intel. >> > noted, I might have written wrongly. All I meant was that the older > ubuntu installers (like 7.10) no longer segfaults qemu/kvm but instead > now halts the guest, could be good to know for anyone trying to > improve the situation I thought. > > /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
