public inbox for kvm@vger.kernel.org
 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: Thu, 02 Feb 2012 15:17:42 +0100	[thread overview]
Message-ID: <4F2A9B06.7050007@siemens.com> (raw)
In-Reply-To: <954799929.293270.1328191651933.JavaMail.open-xchange@email.1und1.de>

On 2012-02-02 15:07, Erik Rull wrote:
> 
> On February 2, 2012 at 2:21 PM Jan Kiszka <jan.kiszka@siemens.com> wrote:
> 
>> On 2012-02-02 14:18, Erik Rull wrote:
>>>
>>> On February 1, 2012 at 11:05 PM Erik Rull <erik.rull@rdsoftware.de>
> wrote:
>>>
>>>> Jan Kiszka wrote:
>>>>> 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<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
>>>>>
>>>>> Is the BIOS at /usr/X11R6/share/qemu in sync with the qemu version
> you
>>>>> try? Does leaving out options change the picture?
>>>>>
>>>>> Jan
>>>>>
>>>>
>>>> It happens directly after the windows boot progress bar is completed
> (I
>>>> boot without logo)
>>>>
>>>> With the -no-kvm-irqchip it seems to be fine...
>>>>
>>>> Best regards,
>>>>
>>>> Erik
>>>
>>>
>>> Hi Jan,
>>>
>>> I tested with an ACPI-enabled windows.
>>> Results:
>>> -no-acpi: Continuous reboots like the no-acpi-windows-version
>>> without -no-acpi: boots!
>>>
>>> So I tested the no-acpi-windows-version without -no-acpi option - still
>>> rebooting
>>> And without -no-acpi and -no-kvm-irqchip => works again
>>
>> Interesting. Need to install such a version, I guess.
>>
>> What about no-acpi-windows and upstream qemu with kvm and -machine
>> kernel_irqchip=on?
>>
>> Jan
> 
> Boots with and without -no-acpi

Ok... Either I fixed something magically, or the feature gap makes the
difference. In any case, need to reproduce.

> 
> Best regards,
> 
> Erik
> 
> P.S. Too many options for me :-)

Not just for you. :)

Jan

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

      reply	other threads:[~2012-02-02 14:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 12:52 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       ` [Qemu-devel] " 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     ` [Qemu-devel] " Erik Rull
2012-02-02 13:21       ` Jan Kiszka
2012-02-02 14:07         ` [Qemu-devel] " Erik Rull
2012-02-02 14:17           ` Jan Kiszka [this message]

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=4F2A9B06.7050007@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