problem using kvm-guest-drivers

problem using kvm-guest-drivers

[Nikola Ciprich]

Hello,
I'm trying to get virtio_blk working, but I can't figure what am I doing 
wrong...
First thing I do not really understand is what kernels are supported, as 
in README file it is written:

Where /path/to/kernel is the path to a recent kernel tree containing 
virtio drivers.  At the moment, this must be Rusty Russell's virtio patch 
queue[1] applied on top of Linus' git tree[2].

and few lines later:

Supported Kernels
-----------------
2.6.24, 2.6.23, 2.6.22, 2.6.21, 2.6.20, 2.6.19, 2.6.18

anyways, I'm not able to get it working either on 2.6.24, or latest GIT 
with rusty's patches.

If I run kvm with
... -drive file=/some/file,if=virtio and then load virtio_blk inside it, I 
simply don't see any new block device appear.

What am I doing wrong?

Oh and I'm using kvm-64 with 2.6.24 for host.

Thanks a lot in advance for any hints.

BR
nik


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

Re: problem using kvm-guest-drivers

[Anthony Liguori]

Nikola Ciprich wrote:
> Hello,
> I'm trying to get virtio_blk working, but I can't figure what am I doing 
> wrong...
> First thing I do not really understand is what kernels are supported, as 
> in README file it is written:
>
> Where /path/to/kernel is the path to a recent kernel tree containing 
> virtio drivers.  At the moment, this must be Rusty Russell's virtio patch 
> queue[1] applied on top of Linus' git tree[2].
>   

This is meant for when you're building the guest drivers from source.  
If you just download a tarball, this step is unnecessary.

> and few lines later:
>
> Supported Kernels
> -----------------
> 2.6.24, 2.6.23, 2.6.22, 2.6.21, 2.6.20, 2.6.19, 2.6.18
>
> anyways, I'm not able to get it working either on 2.6.24, or latest GIT 
> with rusty's patches.
>
> If I run kvm with
> ... -drive file=/some/file,if=virtio and then load virtio_blk inside it, I 
> simply don't see any new block device appear.
>
> What am I doing wrong?
>
> Oh and I'm using kvm-64 with 2.6.24 for host.
>   

Make sure you have virtio_pci loaded in the guest.

Regards,

Anthony Liguori

> Thanks a lot in advance for any hints.
>
> BR
> nik
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Register now and save $200. Hurry, offer ends at 11:59 p.m., 
> Monday, April 7! Use priority code J8TLD2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>   


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

Re: problem using kvm-guest-drivers

[Nikola Ciprich]

Hello Anthony,
thanks a lot for Your help! Loading virtio_pci did indeed 
solved my problem.
BR
nik



On Sat, 5 Apr 2008, Anthony Liguori wrote:

> Nikola Ciprich wrote:
>> Hello,
>> I'm trying to get virtio_blk working, but I can't figure what am I doing 
>> wrong...
>> First thing I do not really understand is what kernels are supported, as in 
>> README file it is written:
>> 
>> Where /path/to/kernel is the path to a recent kernel tree containing virtio 
>> drivers.  At the moment, this must be Rusty Russell's virtio patch queue[1] 
>> applied on top of Linus' git tree[2].
>> 
>
> This is meant for when you're building the guest drivers from source.  If you 
> just download a tarball, this step is unnecessary.
>
>> and few lines later:
>> 
>> Supported Kernels
>> -----------------
>> 2.6.24, 2.6.23, 2.6.22, 2.6.21, 2.6.20, 2.6.19, 2.6.18
>> 
>> anyways, I'm not able to get it working either on 2.6.24, or latest GIT 
>> with rusty's patches.
>> 
>> If I run kvm with
>> ... -drive file=/some/file,if=virtio and then load virtio_blk inside it, I 
>> simply don't see any new block device appear.
>> 
>> What am I doing wrong?
>> 
>> Oh and I'm using kvm-64 with 2.6.24 for host.
>> 
>
> Make sure you have virtio_pci loaded in the guest.
>
> Regards,
>
> Anthony Liguori
>
>> Thanks a lot in advance for any hints.
>> 
>> BR
>> nik
>> 
>> 
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register 
>> now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use 
>> priority code J8TLD2. 
>> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>> _______________________________________________
>> kvm-devel mailing list
>> kvm-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>> 
>
>

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

Re: problem using kvm-guest-drivers

[Dennis Jacobfeuerborn]

Nikola Ciprich wrote:
> Hello,
> I'm trying to get virtio_blk working, but I can't figure what am I doing
> wrong...

You'll probably have to build a new initrd image in the guest adding the 
following options to the mkinitrd call:
"--with=virtio_pci --with=virtio_blk"

This makes sure that the guest will find the virtual devices when booting.

If you use LVM volume groups in the guest then you also need to make sure 
that you use a *very* recent version of the lvm2 package (not older than a 
month) because older versions don't scan the virtual block devices for 
volume groups due to a name change.

Regards,
   Dennis

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

Re: problem using kvm-guest-drivers

[Nikola Ciprich]

Hi Dennis,
thanks a lot for Your reply, the problem really was that I didn't know 
that virtio_pci module is also needed.
I'm not using LVM in guests, but it's good to know recent version would be 
needed for such case.
BR
nik.


On Sun, 6 Apr 2008, Dennis Jacobfeuerborn wrote:

> Nikola Ciprich wrote:
>> Hello,
>> I'm trying to get virtio_blk working, but I can't figure what am I doing
>> wrong...
>
> You'll probably have to build a new initrd image in the guest adding the
> following options to the mkinitrd call:
> "--with=virtio_pci --with=virtio_blk"
>
> This makes sure that the guest will find the virtual devices when booting.
>
> If you use LVM volume groups in the guest then you also need to make sure
> that you use a *very* recent version of the lvm2 package (not older than a
> month) because older versions don't scan the virtual block devices for
> volume groups due to a name change.
>
> Regards,
>   Dennis
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Register now and save $200. Hurry, offer ends at 11:59 p.m.,
> Monday, April 7! Use priority code J8TLD2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
>

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone