From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Jorge Boncompte [DTI2]" <jorge-hjL/uWR+mxo@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: unhandled vm exit: 0x80000021
Date: Mon, 19 Feb 2007 20:01:42 +0200 [thread overview]
Message-ID: <45D9E606.3030407@qumranet.com> (raw)
In-Reply-To: <02b901c7544f$9fd1e0f0$061010ac-2xSMGd46i5a8XZm8kdyKSF6hYfS7NtTn@public.gmane.org>
Jorge Boncompte [DTI2] wrote:
> Hi,
>
> My kvm/qemu setup exits realiably with the error from the subject every
> time that I do a reboot at the guest. Aside from this annoyance kvm/qemu
> works pretty well on my workload.
>
> HOST: Debian (etch) + kernel.org 2.6.20 (32bits) + kvm-14
> GUEST: Custom embedded distribution + kernel.org 2.4.32
> CPU: Intel Pentium D 3.2Ghz
> CMDLINE: /usr/local/bin/qemu -hda /images/loop1.img -k es -serial
> stdio -net nic,model=rtl8139,macaddr="52:54:00:$(date +%T)" -net
> tap -std-vga -no-acpi -nographic
>
The issue is known. It is already fixed (at least partially) on AMD
hosts, and I plan a fix for Intel, though it will take some time for me
to reach it.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-02-19 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 17:58 unhandled vm exit: 0x80000021 Jorge Boncompte [DTI2]
[not found] ` <02b901c7544f$9fd1e0f0$061010ac-2xSMGd46i5a8XZm8kdyKSF6hYfS7NtTn@public.gmane.org>
2007-02-19 18:01 ` Avi Kivity [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=45D9E606.3030407@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=jorge-hjL/uWR+mxo@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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