From: Erik Rull <erik.rull@rdsoftware.de>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] git bisect results: ec757c67c40a56492001487e69272f62144fd124 breaks windows boot in qemu-kvm
Date: Wed, 1 Feb 2012 13:52:15 +0100 (CET) [thread overview]
Message-ID: <923364617.199626.1328100735285.JavaMail.open-xchange@email.1und1.de> (raw)
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:
ec757c67c40a56492001487e69272f62144fd124 Merge branch 'upstream-merge' into
next
Thu, 5 Jan 2012 11:00:07 +0000 (13:00 +0200) Avi Kivity <avi@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
Best regards,
Erik
next reply other threads:[~2012-02-01 12:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 12:52 Erik Rull [this message]
2012-02-01 13:40 ` [Qemu-devel] git bisect results: ec757c67c40a56492001487e69272f62144fd124 breaks windows boot in qemu-kvm Avi Kivity
2012-02-01 14:02 ` Erik Rull
2012-02-01 14:42 ` Jan Kiszka
2012-02-01 15:43 ` Erik Rull
2012-02-01 16:01 ` Jan Kiszka
2012-02-01 16:10 ` Erik Rull
2012-02-01 19:02 ` Jan Kiszka
2012-02-01 22:05 ` Erik Rull
2012-02-02 13:18 ` Erik Rull
2012-02-02 13:21 ` Jan Kiszka
2012-02-02 14:07 ` Erik Rull
2012-02-02 14:17 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=923364617.199626.1328100735285.JavaMail.open-xchange@email.1und1.de \
--to=erik.rull@rdsoftware.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).