public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Caleb Tennis <caleb@aei-tech.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: virtio block drivers not working
Date: Sun, 22 Mar 2009 19:34:39 +0100	[thread overview]
Message-ID: <49C684BF.8070808@wpkg.org> (raw)
In-Reply-To: <CDD36301-1ED8-4804-BC44-C6FF8D08993E@aei-tech.com>

Caleb Tennis schrieb:
> I've been very unsuccessful in using the virtio block drivers inside of 
> a guest.  I can't seem to make them active.  I'm positive my kernel has 
> support for them turned on (not as a module, but as a direct built in), 
> but when I change one of my ide drives over to virtio and boot, it isn't 
> found, and nothing under /sys or /dev indicates the presence of a 
> device.  dmesg doesn't indicate anything about them either.  I DO have 
> virtio networking enabled and working, so I know as a whole that some of 
> the virtio subsystem is functional.
> 
> The only thing I think I'm doing possibly differently than normal is 
> using the "-kernel" option to boot up from a kernel image vs. having an 
> installed boot image via lilo or grub.  Would this make any difference?
> 
> Is there any way for me to debug some more as to why the block drivers 
> don't seem to be showing up?

Did you try other guests?

For example, try downloading a SystemRescueCd beta - it includes virtio 
drivers:

http://www.sysresccd.org/Beta-x86

Boot the guest from this CD, with a drive attached as virtio.

Load virtio drivers - do you see /dev/vda?


-- 
Tomasz Chmielewski
http://wpkg.org

  reply	other threads:[~2009-03-22 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-22 17:58 virtio block drivers not working Caleb Tennis
2009-03-22 18:34 ` Tomasz Chmielewski [this message]
2009-03-22 19:32   ` Caleb Tennis
2009-03-22 21:30 ` Christoph Hellwig
2009-03-22 22:06   ` Caleb Tennis
2009-03-23  7:48     ` Markus Armbruster

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=49C684BF.8070808@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=caleb@aei-tech.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