qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] kqemu in 0.7.2 no longer boots Xen
Date: Mon, 12 Sep 2005 16:37:58 -0500	[thread overview]
Message-ID: <4325F536.5010405@us.ibm.com> (raw)

Admittedly this is probably not a standard usage, but I'm using qemu for 
Xen development (Xen is an Open Source hypervisor).  It works quite well 
so far.

0.7.2 seems to have broken support for kqemu.  Linux freezes during boot 
(running in ring 1 under Xen) right before launching the INIT process.  
Passing -no-kqemu or reverting to 0.7.1 makes the problem go away.

Without knowing the differences in kqemu between versions, it's hard to 
narrow down any further.  I looked at the diffs for qemu though and did 
not see anything obvious.

Let me know if there's anything I can do to help narrow down the problem.

Thanks!

Regards,

Anthony Liguori

             reply	other threads:[~2005-09-12 22:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-12 21:37 Anthony Liguori [this message]
2005-09-12 22:14 ` [Qemu-devel] kqemu in 0.7.2 no longer boots Xen Paul Brook
2005-09-12 22:57   ` Anthony Liguori
2005-09-13 22:00 ` Jim C. Brown
2005-09-14  2:48   ` Anthony Liguori

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=4325F536.5010405@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).