All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Rull <1366836@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1366836] [NEW] Core2Duo and KVM may not boot Win8 properly on 3.x kernels
Date: Mon, 08 Sep 2014 14:47:05 -0000	[thread overview]
Message-ID: <20140908144705.25513.64209.malonedeb@soybean.canonical.com> (raw)
In-Reply-To: 20140908144705.25513.64209.malonedeb@soybean.canonical.com

Public bug reported:

When I start up QEMU w/ KVM 1.7.0 on a Core2Duo machine running a vanilla kernel
3.4.67 or 3.10.12 to run a Windows 8.0 guest, the guest freezes at Windows 8 boot without any error.
When I dump the CPU registers via "info registers", nothing changes, that means
the system really stalled. Same happens with QEMU 2.0.0 and QEMU 2.1.0.

But - when I run the very same guest using Kernel 2.6.32.12 and QEMU 1.7.0 or 2.0.0 on
the host side it works on the Core2Duo. Also the system above but just with an
i3 or i5 CPU it works fine.

I already disabled networking and USB for the guest and changed the graphics
card - no effect. I assume that some mean bits and bytes have to be set up
properly to get the thing running.

Seems to be related to a kvm/processor incompatibility.

** Affects: qemu
     Importance: Undecided
         Status: New


** Tags: core2duo kvm

** Description changed:

  When I start up QEMU w/ KVM 1.7.0 on a Core2Duo machine running a vanilla kernel
  3.4.67 or 3.10.12 to run a Windows 8.0 guest, the guest freezes at Windows 8 boot without any error.
  When I dump the CPU registers via "info registers", nothing changes, that means
  the system really stalled. Same happens with QEMU 2.0.0 and QEMU 2.1.0.
  
  But - when I run the very same guest using Kernel 2.6.32.12 and QEMU 1.7.0 or 2.0.0 on
  the host side it works on the Core2Duo. Also the system above but just with an
  i3 or i5 CPU it works fine.
  
  I already disabled networking and USB for the guest and changed the graphics
  card - no effect. I assume that some mean bits and bytes have to be set up
  properly to get the thing running.
  
- Seems to be related to a kvm/progressor incompatibility.
+ Seems to be related to a kvm/procressor incompatibility.

** Description changed:

  When I start up QEMU w/ KVM 1.7.0 on a Core2Duo machine running a vanilla kernel
  3.4.67 or 3.10.12 to run a Windows 8.0 guest, the guest freezes at Windows 8 boot without any error.
  When I dump the CPU registers via "info registers", nothing changes, that means
  the system really stalled. Same happens with QEMU 2.0.0 and QEMU 2.1.0.
  
  But - when I run the very same guest using Kernel 2.6.32.12 and QEMU 1.7.0 or 2.0.0 on
  the host side it works on the Core2Duo. Also the system above but just with an
  i3 or i5 CPU it works fine.
  
  I already disabled networking and USB for the guest and changed the graphics
  card - no effect. I assume that some mean bits and bytes have to be set up
  properly to get the thing running.
  
- Seems to be related to a kvm/procressor incompatibility.
+ Seems to be related to a kvm/processor incompatibility.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1366836

Title:
  Core2Duo and KVM may not boot Win8 properly on 3.x kernels

Status in QEMU:
  New

Bug description:
  When I start up QEMU w/ KVM 1.7.0 on a Core2Duo machine running a vanilla kernel
  3.4.67 or 3.10.12 to run a Windows 8.0 guest, the guest freezes at Windows 8 boot without any error.
  When I dump the CPU registers via "info registers", nothing changes, that means
  the system really stalled. Same happens with QEMU 2.0.0 and QEMU 2.1.0.

  But - when I run the very same guest using Kernel 2.6.32.12 and QEMU 1.7.0 or 2.0.0 on
  the host side it works on the Core2Duo. Also the system above but just with an
  i3 or i5 CPU it works fine.

  I already disabled networking and USB for the guest and changed the graphics
  card - no effect. I assume that some mean bits and bytes have to be set up
  properly to get the thing running.

  Seems to be related to a kvm/processor incompatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1366836/+subscriptions

       reply	other threads:[~2014-09-08 14:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 14:47 Erik Rull [this message]
2014-09-08 14:57 ` [Qemu-devel] [Bug 1366836] Re: Core2Duo and KVM may not boot Win8 properly on 3.x kernels Erik Rull
2014-09-08 15:05 ` Erik Rull
2014-09-09  6:55 ` Erik Rull
2014-09-11 10:13 ` Erik Rull
2014-09-11 13:24 ` Erik Rull
2014-09-11 14:12 ` Erik Rull
2014-09-12 12:28 ` Erik Rull
2017-10-26 13:20 ` Thomas Huth
2017-10-27 20:16 ` Erik Rull
2017-10-27 21:54 ` Thomas Huth

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=20140908144705.25513.64209.malonedeb@soybean.canonical.com \
    --to=1366836@bugs.launchpad.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.