From: Brian Jackson <iggy@theiggy.com>
To: Matteo Ghezzi <tenyosama@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: KVM problems with Xeon L5530
Date: Wed, 27 Jan 2010 18:22:03 -0600 [thread overview]
Message-ID: <201001271822.04144.iggy@theiggy.com> (raw)
In-Reply-To: <3c9db2861001271537x4b45d1ccpe268e13561c035fd@mail.gmail.com>
On Wednesday 27 January 2010 05:37:14 pm Matteo Ghezzi wrote:
> Hi!
>
> I'm a long time KVM user, but I've encountered a problem that I couldn't
> solve. I've switched my good old Core2 Quad with gentoo (2.6.27 kernel)
> for a Dual Xeon L5530 with Arch (2.6.32 kernel).
> I've tried starting the old vmachines on the new hardware but if I
> enable kvm acceleration in qemu I got a black screen via vnc, and the
> logs are filled with this message:
What version of qemu-kvm?
There was a similar thread a while back, maybe you could try some of the
suggestions and/or info gathering tips from it.
http://www.mail-archive.com/kvm@vger.kernel.org/msg24304.html
>
> handle_exception: unexpected, vectoring info 0x8000000d intr info
> 0x80000b0d
>
> I've tried creating new virtual machines directly on the new hardware
> but with the same result.
> I've tried any combination of virtualization options in the bios,
> tested any bios revision for my motherboard (Asus Z8DNA-D6), checked
> the ram on another system... all in vain.
>
> If I've to provide more info please let me know.
> Thanks for your help.
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-28 0:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 23:37 KVM problems with Xeon L5530 Matteo Ghezzi
2010-01-28 0:22 ` Brian Jackson [this message]
2010-01-28 8:40 ` Matteo Ghezzi
2010-01-28 11:02 ` Matteo Ghezzi
2010-02-07 10:50 ` Avi Kivity
2010-02-09 23:11 ` Matteo Ghezzi
2010-01-28 12:32 ` Kenni Lund
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=201001271822.04144.iggy@theiggy.com \
--to=iggy@theiggy.com \
--cc=kvm@vger.kernel.org \
--cc=tenyosama@gmail.com \
/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