public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Caleb Tennis <caleb@aei-tech.com>
Cc: kvm@vger.kernel.org
Subject: Re: virtio block drivers not working
Date: Mon, 23 Mar 2009 08:48:04 +0100	[thread overview]
Message-ID: <87y6uwvfwr.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <7EE71E85-ED07-4C3D-8747-092F8F478A8E@aei-tech.com> (Caleb Tennis's message of "Sun\, 22 Mar 2009 18\:06\:17 -0400")

Caleb Tennis <caleb@aei-tech.com> writes:

> On Mar 22, 2009, at 5:30 PM, Christoph Hellwig wrote:
>
>> I do you virtio block in a very similar setup to yours (fully static
>> kernel, -kernel option to kvm/qemu) sucesfully for quite a a while.
>>
>> Can you post your kernel .config and the contents of /proc/devices
>> and /proc/partitions to debug this further?
>>
>
> I've found the problem.  In my testing, I was changing my second drive
> from ide to virtio, so it looked like this:
>
> -drive index=0,media=disk,if=ide,file=/root
> -drive index=1,media=disk,if=virtio,file=/data
>
> This doesn't work though, even as vdb, as since the interface is the
> first virtio, the index needs to be set back to 0.  This gives me a /
> dev/vda like I was expecting.
>
> Thanks,
> Caleb

Yes, the common loop to create virtio block devices (all three copies of
it) stops at the first unused unit number / index.  A rude trap for the
unwary.  The device configuration patch I'm working on upstream doesn't
do that.

      reply	other threads:[~2009-03-23  7:48 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
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 [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=87y6uwvfwr.fsf@pike.pond.sub.org \
    --to=armbru@redhat.com \
    --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