From: "Gregory Haskins" <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
To: "Avi Kivity" <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Forward progress
Date: Mon, 12 Mar 2007 13:26:26 -0400 [thread overview]
Message-ID: <45F5550C.BA47.005A.0@novell.com> (raw)
In-Reply-To: <45F3CBC7.2020406-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
>>> On Sun, Mar 11, 2007 at 5:28 AM, in message <45F3CBC7.2020406-atKUWr5tajBWk0Htik3J/w@public.gmane.org>,
Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>
> Does the problem also occur with stock qemu- 0.9.0?
I confirmed that the KVM variant of qemu has the problem both with and without the KVM driver. However, the stock 0.9.0 QEMU codebase works fine. I saw there was a checkin recently where some files were found to have not merged correctly? I will pull down the latest and see if that makes a difference.
-Greg
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-03-12 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 5:19 Forward progress Gregory Haskins
[not found] ` <45F0A836.BA47.005A.0-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
2007-03-11 9:28 ` Avi Kivity
[not found] ` <45F3CBC7.2020406-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-12 11:49 ` Gregory Haskins
2007-03-12 17:26 ` Gregory Haskins [this message]
[not found] ` <45F5550C.BA47.005A.0-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
2007-03-12 17:34 ` 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=45F5550C.BA47.005A.0@novell.com \
--to=ghaskins-et1tbqhtxzrqt0dzr+alfa@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@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