From: Marcelo Tosatti <mtosatti@redhat.com>
To: Kenni Lund <kelu@kelu.dk>
Cc: kvm@vger.kernel.org
Subject: Re: Unable to boot guest on kernel 2.6.29.1 with kvm-84 or kvm-85
Date: Fri, 24 Apr 2009 22:04:11 -0300 [thread overview]
Message-ID: <20090425010411.GC15144@amt.cnet> (raw)
In-Reply-To: <57110.1240507294@kelu.dk>
Kenni,
On Thu, Apr 23, 2009 at 07:21:34PM +0200, Kenni Lund wrote:
> Hi
>
> When updating to kernel 2.6.29.1, I'm unable to boot my Windows XP Pro 32bit guest. The problem is consistent (actually on both of my laptops, with two different WinXP guests) and it is fixed immediately when downgrading to kernel 2.6.28.8 or an older kernel version.
>
>
> Scenario:
> I'm booting the guest with the command
> qemu-kvm -smp 2 -m 1024 -net nic -net user -daemonize -vnc :1 -hda /data/virtualization/winxp.img -boot c
>
> I connect with VNC and see the QEMU BIOS, followed by the Windows menu which lets me select if I want to boot Windows in safe mode or not. It counts down from 30, but when it get to 0 or once I hit the "Start Windows Normally" it freezes and nothing more happens.
>
> The following is written to dmesg when qemu-kvm is launched:
> kvm: 4609: cpu1 unhandled wrmsr: 0xc0010117 data 0
> kvm: 4609: cpu0 unhandled wrmsr: 0xc0010117 data 0
This message are supposedly harmless (and you should also see them with
2.6.28.8).
Can you try the kvm-85 modules? Can't spot anything obvious between
2.6.28->2.6.29 which would cause such breakage.
> Further information:
> KVM version: 84+85 (userspace only, kernel modules from stock kernel)
>
> I've tested -no-kvm-irqchip and -no-kvm-pit as the bugs-page describes, but it doesn't make a difference.
>
> Adding -no-kvm actually FIXES the issue and make Windows boot...so it doesn't seem to be QEMU related.
>
> # uname -a
> Linux T61 2.6.29-ARCH #1 SMP PREEMPT Fri Apr 17 12:46:01 UTC 2009 i686 Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz GenuineIntel GNU/Linux
>
> # lsmod|grep kvm
> kvm_intel 39208 0
> kvm 144944 1 kvm_intel
>
>
> Is this a known problem with this kernel version? If not, what can I do to help debugging it further?
next prev parent reply other threads:[~2009-04-25 1:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 17:21 Unable to boot guest on kernel 2.6.29.1 with kvm-84 or kvm-85 Kenni Lund
2009-04-23 20:57 ` Bernhard Held
2009-04-25 1:04 ` Marcelo Tosatti [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-24 14:29 Kenni Lund
2009-04-26 10:43 ` Avi Kivity
2009-04-26 22:11 Eino Malinen
2009-04-27 8:57 ` Avi Kivity
2009-04-27 17:42 ` Eino Malinen
2009-05-01 22:52 Kenni Lund
2009-05-02 7:51 ` Avi Kivity
2009-05-03 10:14 ` Avi Kivity
2009-05-03 11:49 Kenni Lund
2009-05-03 12:07 ` Avi Kivity
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=20090425010411.GC15144@amt.cnet \
--to=mtosatti@redhat.com \
--cc=kelu@kelu.dk \
--cc=kvm@vger.kernel.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