xen discuss - Feb 2008 - Xen Daemon error: POST operation failed: (xend.err)

Hello

I am running 64-bit snv_80
I''m trying to install a guest domain running windows vista, but getting
errors.

I ran this command to create an ISO of the vista CD:
# dd if=/dev/dsk/c0t0d0s2 of=vistaimg.iso
5952576+0 records in
5952576+0 records out

Next I ran virt-install, and this is what happened:

# virt-install
Would you like a fully virtualized guest (yes or no)?  This will allow you to
run unmodified operating systems. yes
 What is the name of your virtual machine? vista
 How much RAM should be allocated (in megabytes)? 2048
 What would you like to use as the disk (path)? /virtdsk/vistadisk.img
 How large would you like the disk (/virtdsk/vistadisk.img) to be (in
gigabytes)? 50
 Would you like to enable graphics support? (yes or no) yes
 What would you like to use for the virtual CD image? /virtdsk/vistaimg.iso
 

Starting install...
Creating storage file...  100% |=========================|  50 GB    00:00     
libvir: Xen Daemon error : POST operation failed: (xend.err )
Traceback (most recent call last):
  File "/usr/bin/virt-install", line 657, in ?
    main()
  File "/usr/bin/virt-install", line 606, in main
    dom = guest.start_install(conscb,progresscb)
  File
"/export/builds/xvm_80/proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 638, in start_install
  File
"/export/builds/xvm_80/proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 655, in _do_install
  File "/usr/lib/python2.4/vendor-packages/libvirt.py", line 503, in
createLinux
    if ret is None:raise libvirtError(''virDomainCreateLinux()
failed'', conn=self)
libvirt.libvirtError: virDomainCreateLinux() failed POST operation failed:
(xend.err )

What am I doing wrong?
 
 
This message posted from opensolaris.org

Could this be why it wont work?
My wired NIC is listed as legacy.

# dladm show-link
wpi0            type: non-vlan  mtu: 1500       device: wpi0
bcme0           type: legacy    mtu: 1500       device: bcme0
 
 
This message posted from opensolaris.org

Kerry Randolph wrote:
> Could this be why it wont work?
> My wired NIC is listed as legacy.
>
> # dladm show-link
> wpi0            type: non-vlan  mtu: 1500       device: wpi0
> bcme0           type: legacy    mtu: 1500       device: bcme0
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> xen-discuss mailing list
> xen-discuss@opensolaris.org
>   
Broadcom is really the most unsupported adapter you can use on any FOSS 
system, including OpenSolaris.  Intel, Atheros, AMD, Realtek, and nForce 
are the best supported adapters, and work with xVM.  Broadcom is missing 
support for certain features in GLDv3 I think, which is maybe why it''s 
legacy.  It''s missing what''s needed to bridge it correctly, if
I am correct.

James

Hi All,

I get the same xend.err and from searching understand I need a GLD3 NIC driver.
The onboard NIC is a Broadcom 4401. Running on nv83.

I have installed the bfe driver bfe-2.3.1t0.tar.gz from
http://www.opensolaris.org/os/community/device_drivers/files

The NIC is working correctly. However when I run the dladm show-link command to
verify its not showing up in legacy status, I get:

$ dladm show-link
LINK CLASS MTU STATE OVER
wpi0 phys 1500 down --
bfe0 phys 1500 unknown --

The ''type'' field is missing altogether. Any ideas why this
output is different?

What can I do to verify I have the correct GLD3 driver installed and eliminate
this as the problem of the xend.err above?

Cheers, JP
 
 
This message posted from opensolaris.org

On 20 Mar 2008, at 05:22, Jean-Paul Rivet wrote:
> The NIC is working correctly. However when I run the dladm show-link  
> command to verify its not showing up in legacy status, I get:
>
> $ dladm show-link
> LINK CLASS MTU STATE OVER
> wpi0 phys 1500 down --
> bfe0 phys 1500 unknown --
>
> The ''type'' field is missing altogether. Any ideas why
this output is
> different?
dladm output changed with the integration of the Clearview UV project.
> What can I do to verify I have the correct GLD3 driver installed and  
> eliminate this as the problem of the xend.err above?
Try to create a VNIC ''by hand'':

# /usr/lib/vna bfe0 aa:1:2:3:4:5

If this succeeds then bfe0 is usable by the Xen tools. It should  
output ''vnic0'' (perhaps not ''0'') when
successful. You can remove the
VNIC it creates with ''/usr/lib/vna vnic0''.

Thanks David.

In the interim I''ve done a fresh install to snv_85, re-installed the
bfe driver as above and the tried the command you suggested.

Running the command gives:

# /usr/lib/vna bfe0 aa:1:2:3:4:5
dladm_vnic_create: operation not supported
# 

which I guess is not the answer we were looking for?

Cheers, JP
 
 
This message posted from opensolaris.org

Actually, error looks slightly different I guess with the move from 83->85
saying ''Device 0 (vif) could not be connected. Backend device not
found.''

 virt-install 
Would you like a fully virtualized guest (yes or no)?  This will allow you to
run unmodified operating systems. yes
 What is the name of your virtual machine? winxp
 How much RAM should be allocated (in megabytes)? 512
 What would you like to use as the disk (path)? /export/xvm/winxp.img
 How large would you like the disk (/export/xvm/winxp.img) to be (in gigabytes)?
8
 Would you like to enable graphics support? (yes or no) yes
 What would you like to use for the virtual CD image?
/export/home/jp/Download/WXPCORP_EN.iso
 

Starting install...
libvir: Xen Daemon error : GET operation failed: 
libvir: Xen Daemon error : GET operation failed: 
Creating storage file...  100% |=========================| 8.0 GB    00:00     
libvir: Xen Daemon error : 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 657, in ?
    main()
  File "/usr/bin/virt-install", line 606, in main
    dom = guest.start_install(conscb,progresscb)
  File
"/export/builds/xvm_85/proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 638, in start_install
  File
"/export/builds/xvm_85/proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 655, in _do_install
  File "/usr/lib/python2.4/vendor-packages/libvirt.py", line 585, in
createLinux
    if ret is None:raise libvirtError(''virDomainCreateLinux()
failed'', conn=self)
libvirt.libvirtError: virDomainCreateLinux() failed POST operation failed:
(xend.err ''Device 0 (vif) could not be connected. Backend device not
found.'')
 
 
This message posted from opensolaris.org

On 20 Mar 2008, at 10:14, Jean-Paul Rivet wrote:
> # /usr/lib/vna bfe0 aa:1:2:3:4:5
> dladm_vnic_create: operation not supported
> #
>
> which I guess is not the answer we were looking for?
It tells us that you cannot create VNICs over bfe0. Given that your  
only other network interface appeared to be wifi (which also doesn''t  
support VNICs), it looks as though you are out of luck. Sorry.

dme.

Thanks David.

I also located a 2.6.0a revision of the bfe driver from here
http://homepage2.nifty.com/mrym3/taiyodo/eng/

I compiled the GLDv3 version but no luck :(

Thanks for your support.

Cheers, JP
 
 
This message posted from opensolaris.org