xen discuss - May 2009 - CentOS DomU on Opensolaris Dom0 - virt-install fails with error in virDomainCreateLinux()

Hi,

I am trying to install CentOS on an Opensolaris Dom0. virt-install fails
 with an error in virDomainCreateLinux().

Is this a known issue? Am I missing some step?

manoj@mowgli:~$ uname -a
SunOS mowgli 5.11 snv_101b i86pc i386 i86xpv Solaris

manoj@mowgli:~$ pfexec virt-install
What is the name of your virtual machine? centos
 How much RAM should be allocated (in megabytes)? 512
 What would you like to use as the disk (file path)? /xen/centos/root.disk
 Would you like to enable graphics support? (yes or no) no
 What is the install location? /media/CentOS_5.3_Final/


Starting install...
virDomainCreateLinux() failed POST operation failed: (xend.err ''Device
0 (vif) could not be connected. Backend device not found.'')
Domain installation may not have been
 successful.  If it was, you can restart your domain
 by running ''virsh start centos''; otherwise, please
 restart your installation.
Sun, 03 May 2009 19:14:10 ERROR    virDomainCreateLinux() failed POST
operation failed: (xend.err ''Device 0 (vif) could not be connected.
Backend device not found.'')
Traceback (most recent call last):
  File "/usr/bin/virt-install", line 511, in ?
    main()
  File "/usr/bin/virt-install", line 471, in main
    dom = guest.start_install(conscb,progresscb)
  File
"/export/builds/xvm_101///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 878, in start_install
  File
"/export/builds/xvm_101///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 899, in _do_install
  File "libvirt.py", line 585, in createLinux
    if ret is None:raise libvirtError(''virDomainCreateLinux()
failed'',
conn=self)
libvirtError: virDomainCreateLinux() failed POST operation failed:
(xend.err ''Device 0 (vif) could not be connected. Backend device not
found.'')
manoj@mowgli:~$


Cheers
Manoj

-- 
Manoj Joseph,
Lustre Group,
Sun Microsystems

Manoj Joseph wrote:
> Hi,
> 
> I am trying to install CentOS on an Opensolaris Dom0. virt-install fails
>  with an error in virDomainCreateLinux().
> virDomainCreateLinux() failed POST operation failed: (xend.err
''Device
> 0 (vif) could not be connected. Backend device not found.'')
ifconfig does not show a vif device and that seems to be my problem.

I am using an ''Intel® PRO/Wireless 3945ABG'' device - wpi0. Is
this known
not to work with xen/opensolaris? I also have a LAN port but ''nwam
magic'' keeps it down.

-Manoj

* Manoj.Joseph@Sun.COM [2009-05-05 19:04:57]
> Manoj Joseph wrote:
>> Hi,
>> 
>> I am trying to install CentOS on an Opensolaris Dom0. virt-install
fails
>>  with an error in virDomainCreateLinux().
>
>> virDomainCreateLinux() failed POST operation failed: (xend.err
'Device
>> 0 (vif) could not be connected. Backend device not found.')
>
> ifconfig does not show a vif device and that seems to be my problem.
>
> I am using an 'Intel® PRO/Wireless 3945ABG' device - wpi0. Is this
known
> not to work with xen/opensolaris? I also have a LAN port but 'nwam
> magic' keeps it down.
You cannot use a wifi interface to connect guests to the network, as we
are not able to create VNICs on top.

dme.
-- 
David Edmondson, Sun Microsystems, http://dme.org
_______________________________________________
xen-discuss mailing list
xen-discuss@opensolaris.org

David Edmondson wrote:
> * Manoj.Joseph@Sun.COM [2009-05-05 19:04:57]
>> Manoj Joseph wrote:
>>> Hi,
>>>
>>> I am trying to install CentOS on an Opensolaris Dom0. virt-install
fails
>>>  with an error in virDomainCreateLinux().
>>> virDomainCreateLinux() failed POST operation failed: (xend.err
'Device
>>> 0 (vif) could not be connected. Backend device not found.')
>> ifconfig does not show a vif device and that seems to be my problem.
>>
>> I am using an 'Intel® PRO/Wireless 3945ABG' device - wpi0. Is
this known
>> not to work with xen/opensolaris? I also have a LAN port but 'nwam
>> magic' keeps it down.
> 
> You cannot use a wifi interface to connect guests to the network, as we
> are not able to create VNICs on top.
Is this an opensolaris/xen limitation? I can do this on VMWare/Linux.

Is it possible to use a host-only virtual network instead?

Manoj

_______________________________________________
xen-discuss mailing list
xen-discuss@opensolaris.org

* Manoj.Joseph@Sun.COM [2009-05-05 20:10:11]
>> You cannot use a wifi interface to connect guests to the network, as we
>> are not able to create VNICs on top.
>
> Is this an opensolaris/xen limitation? I can do this on VMWare/Linux.
I''d be curious to know how that works. All of the Wifi interfaces I
looked at refused to send packets with a MAC address other than their
own (at least when in client mode).
> Is it possible to use a host-only virtual network instead?
Yes, but setting it up is clunky.

Create an etherstub (see dladm) and use that as the bridge device for
the guest domains. Also create a VNIC over the etherstub and plumb it
under IP in dom0.

dme.
-- 
David Edmondson, Sun Microsystems, http://dme.org

David Edmondson wrote:
> * Manoj.Joseph@Sun.COM [2009-05-05 20:10:11]
>>> You cannot use a wifi interface to connect guests to the network,
as we
>>> are not able to create VNICs on top.
>> Is this an opensolaris/xen limitation? I can do this on VMWare/Linux.
> 
> I''d be curious to know how that works. All of the Wifi interfaces
I
> looked at refused to send packets with a MAC address other than their
> own (at least when in client mode).
I don''t know how it is done. But I have successfully configured a NAT
device which the vmware guest uses to connect to the Internet.

While you probably can''t look at the source of vmware, you can probably
check out virtual box. Seems vbox can do this as well.
http://ubuntuforums.org/showthread.php?t=782936
>> Is it possible to use a host-only virtual network instead?
> 
> Yes, but setting it up is clunky.
> 
> Create an etherstub (see dladm) and use that as the bridge device for
> the guest domains. Also create a VNIC over the etherstub and plumb it
> under IP in dom0.
Thanks; let me give that a try.

Cheers
Manoj

* Manoj.Joseph@Sun.COM [2009-05-05 21:42:27]
> David Edmondson wrote:
>> * Manoj.Joseph@Sun.COM [2009-05-05 20:10:11]
>>>> You cannot use a wifi interface to connect guests to the
network, as we
>>>> are not able to create VNICs on top.
>>> Is this an opensolaris/xen limitation? I can do this on
VMWare/Linux.
>> 
>> I''d be curious to know how that works. All of the Wifi
interfaces I
>> looked at refused to send packets with a MAC address other than their
>> own (at least when in client mode).
>
> I don''t know how it is done. But I have successfully configured a
NAT
> device which the vmware guest uses to connect to the Internet.
If there''s NAT in the middle then the configuration is quite different
to the default behaviour of Solaris on Xen.

We have all of the pieces to do this, but as with host only, the
configuration is clunky.

dme.
-- 
David Edmondson, Sun Microsystems, http://dme.org

David Edmondson wrote:
> * Manoj.Joseph@Sun.COM [2009-05-05 21:42:27]
>> David Edmondson wrote:
>>> * Manoj.Joseph@Sun.COM [2009-05-05 20:10:11]
>>>>> You cannot use a wifi interface to connect guests to the
network, as we
>>>>> are not able to create VNICs on top.
>>>> Is this an opensolaris/xen limitation? I can do this on
VMWare/Linux.
>>> I''d be curious to know how that works. All of the Wifi
interfaces I
>>> looked at refused to send packets with a MAC address other than
their
>>> own (at least when in client mode).
>> I don''t know how it is done. But I have successfully
configured a NAT
>> device which the vmware guest uses to connect to the Internet.
> 
> If there''s NAT in the middle then the configuration is quite
different
> to the default behaviour of Solaris on Xen.
> 
> We have all of the pieces to do this, but as with host only, the
> configuration is clunky.
Looks like project crossbow (and dladm create-etherstub) went into
snv_105. Opensolaris is still at snv_101b. So, I guess I''ll just have
to
wait.

Cheers
Manoj

On Mon, May 11, 2009 at 1:55 AM, Manoj Joseph <Manoj.Joseph@sun.com>
wrote:
> Looks like project crossbow (and dladm create-etherstub) went into
> snv_105. Opensolaris is still at snv_101b. So, I guess I''ll just
have to
> wait.
... or use /dev repository to update to snv_111a? Or do fresh install
from ISO on http://genunix.org/ ?