qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Erik Rull <erik.rull@rdsoftware.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] git bisect results: ec757c67c40a56492001487e69272f62144fd124 breaks windows boot in qemu-kvm
Date: Wed, 01 Feb 2012 17:01:20 +0100	[thread overview]
Message-ID: <4F2961D0.7070509@siemens.com> (raw)
In-Reply-To: <908703316.215593.1328111009018.JavaMail.open-xchange@email.1und1.de>

On 2012-02-01 16:43, Erik Rull wrote:
>  On February 1, 2012 at 3:42 PM Jan Kiszka <jan.kiszka@siemens.com> wrote:
> 
>> On 2012-02-01 15:02, Erik Rull wrote:
>>>
>>> On February 1, 2012 at 2:40 PM Avi Kivity <avi@redhat.com> wrote:
>>>
>>>> On 02/01/2012 02:52 PM, 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...
>>>>
>>>> The differences are being reduced rapidly, thanks to Jan's efforts.
>>>> Right now what remains is PIT performance and accuracy, device
>>>> assignment, and Windows XP performance.  Most guests should see the
> same
>>>> performance.
>>
>> MSI performance is expected to be worse with upstream as well, thus
> virtio.
>>
>>>>
>>>>> 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

So commit aad3b517a1b83561f2755dc4451596a421399c19, i.e. the last merge
before that one is still fine?

>>>>> 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
>>>>>
>>>>>
>>>>
>>>> What version of Windows are you using?  What's the contents of
>>>> /etc/ich9-ehci-uhci.cfg?
>>>>
>>>
>>> Hi Avi,
>>>
>>> the contents from the .cfg are located in docs/ich9-ehci-uhci.cfg
>>>
>>> I tried two versions of Windows XP: One is the default Windows XP SP3
> that
>>> you get from MSDN, one is Windows Embedded Standard (embedded
> customized
>>> XP).
>>>
>>> Both show the same behavior: boots with qemu -enable-kvm and
> continuously
>>> reboots with qemu-kvm.
>>
>> What does qemu-kvm with -no-kvm-irqchip do?
>>
>> Jan
>>
> 
> Wow - that works!
> Does this influence the guest performance?
> 

Yes, how much depends on your workload.

Still strange, though. We should try to understand this issue. It stays
like this up to and including current qemu-kvm.git master?

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2012-02-01 16:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 12:52 [Qemu-devel] git bisect results: ec757c67c40a56492001487e69272f62144fd124 breaks windows boot in qemu-kvm Erik Rull
2012-02-01 13:40 ` 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 [this message]
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=4F2961D0.7070509@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=erik.rull@rdsoftware.de \
    --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).