public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Ahern" <daahern@cisco.com>
To: Zach Carter <z.carter@f5.com>
Cc: Brian Jackson <iggy@theiggy.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: qemu-kvm 0.12.4 hanging forever
Date: Fri, 02 Jul 2010 12:51:25 -0600	[thread overview]
Message-ID: <4C2E352D.7060903@cisco.com> (raw)
In-Reply-To: <201007021028.32097.z.carter@f5.com>



On 07/02/10 11:28, Zach Carter wrote:
> On Thursday 01 July 2010 16:02:26 Brian Jackson wrote:

>>> 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.

I've used SCSI for RHEL3 and RHEL4 guests for years. Performance is
significantly better than IDE. I have yet to have a guest crash because
of it.

David


> 
> thanks,
> 
> -Zach
> --
> 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
> 

      reply	other threads:[~2010-07-02 18:49 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
2010-07-02 18:51     ` David S. Ahern [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=4C2E352D.7060903@cisco.com \
    --to=daahern@cisco.com \
    --cc=iggy@theiggy.com \
    --cc=kvm@vger.kernel.org \
    --cc=z.carter@f5.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