[OmniOS-discuss] OmniOS KVM guest with virtio net support

[Frédéric Alix]

Hum, very strange,
Some KVM host providers use this param to add disk img

-drive file=img.qcow2,if=virtio,id=drive-virtiodisk0,cache=none

If i use it for OmniOS, the boot process block at the load of vioblk module

With NexentaOS, it load without problem.

To start OmniOS correctly, i must use this:

-drive file=img.qcow2,if=none,id=drive-virtio-disk0,format=qcow2
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1

Since few hours, i am trying to understand why it's ok with nexenta
and not with OmniOS.

I used the illumos-nexenta source to build virtio, vioblk and blkdev
and nothing change.

Did you already had this situation ?


fred.


2014-11-04 3:35 GMT+01:00 NovHost <contact at novhost.eu>:

> I try to run OmniOS under Runabove cloud.
> To this, i build this OmniOS image for KVM.
> It's a qcow2 img. I run it with virtio blk and virtio net support on
> Fedora and Ubuntu with virt-manager, without problem.
>
> Actually, i have a problem to run it on Runabove, but it should run in
> another KVM VPS providers.
>
> You can download it at:
>
> https://drive.google.com/file/d/0B3424f6EdZMmbFY2VkN0dnZ6TzQ/view?usp=sharing
>
> I'll send my notes soon how i put virtio net driver.
>
> fred.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omniosce.org/ml-archive/attachments/20141104/a737482b/attachment.html>