On 2012-02-01 13:52, Erik Rull wrote: > Hi all, > > first of all I'm a bit confused: > > What is the difference between qemu with command line option --enable-kvm > and qemu-kvm? > It seems to be a difference in code so far, from the performance point of > view it seems to be the same... > > Now my issue that lead me to a git bisect on qemu-kvm: > The following commit / merge breaks my windows guest boot sequence and > causes resets infinitely:
Cannot confirm yet, but I have no ACPI-free Windows installation at hand. Where does it reset, after the BIOS? > ec757c67c40a56492001487e69272f62144fd124 Merge branch 'upstream-merge' into > next > Thu, 5 Jan 2012 11:00:07 +0000 (13:00 +0200) Avi Kivity <a...@redhat.com> > > > Interesting: qemu with --enable-kvm master and the same command line > options as qemu-kvm runs perfect. > My command line options are: > qemu-system-x86_64 -serial /dev/ttyS2 -readconfig /etc/ich9-ehci-uhci.cfg > -device usb-host,bus=ehci.0 -device usb-tablet -drive > file=/dev/sda2,cache=off -m 1024 -net nic,macaddr=$MACADDR -net > tap,script=/etc/qemu-ifup -no-acpi -monitor stdio -L /usr/X11R6/share/qemu > -boot c -localtime Is the BIOS at /usr/X11R6/share/qemu in sync with the qemu version you try? Does leaving out options change the picture? Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux
