public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Zach Carter <z.carter@f5.com>
To: Brian Jackson <iggy@theiggy.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: qemu-kvm 0.12.4 hanging forever
Date: Fri, 2 Jul 2010 10:28:31 -0700	[thread overview]
Message-ID: <201007021028.32097.z.carter@f5.com> (raw)
In-Reply-To: <201007011802.27102.iggy@theiggy.com>

On Thursday 01 July 2010 16:02:26 Brian Jackson wrote:
> > Here are some more interesting details.  The 64 bit host, kernel, and kvm
> > kernel module are all vanilla CentOS 5.4.  If I use the kmod-
> > kvm-83-105.el5_4.9 version of the kernel module, it works fine.  Yum
> > update to anything past that and the hang occurs 100% of the
> > time.  Update all the way to the very latest CentOS 5.5 packages, and I
> > still get the hang. Downgrade just the kvm kernel modules and it starts
> > working again.
> 
> That's pretty well known. Use a newer kernel with a newer qemu-kvm, or use
> the  packages that come with CentOS.

I looked though mail lists and searched with google for quite a while and 
didn't anything that sounded the same.  Is there a bug reference or some other 
search term I could use to find others discussing this issue?

> > I'm sure I could use the qemu-kvm that ships from CentOS with the
> > corresponding kernel module, however that lacks certain essential
> > features, including support for scsi disk drive emulation.
> 
> There's a reason Redhat disables scsi support in their kvm... it's not
> really  suggested to use it.

What specific reason is that?  The kvm.spec %changelog references RedHat 
bugzilla 512837, however I am not authorized to access it.

scsi is a hard requirement for us, even if we have to stay on the old kernel 
module.  

Any additional insight would be much appreciated.

thanks,

-Zach

  reply	other threads:[~2010-07-02 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 22:37 qemu-kvm 0.12.4 hanging forever Zach Carter
2010-07-01 23:02 ` Brian Jackson
2010-07-02 17:28   ` Zach Carter [this message]
2010-07-02 18:51     ` David S. Ahern

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=201007021028.32097.z.carter@f5.com \
    --to=z.carter@f5.com \
    --cc=iggy@theiggy.com \
    --cc=kvm@vger.kernel.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