Bug 233229 - virt-install: taillibvir: Xen Daemon error : POST operation failed:
virt-install: taillibvir: Xen Daemon error : POST operation failed:
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: virt-manager (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Berrange
Martin Jenner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-20 22:11 EDT by eric magaoay
Modified: 2008-01-30 10:26 EST (History)
1 user (show)

See Also:
Fixed In Version: 0.5.3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-01-30 10:26:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
xend.log file (7.66 KB, text/plain)
2007-03-20 22:11 EDT, eric magaoay
no flags Details
screenshot of initial kernel bootup (18.68 KB, image/png)
2007-03-22 14:51 EDT, eric magaoay
no flags Details
setroubleshooter output preventing xen to read config.sxp (2.17 KB, text/plain)
2007-03-22 14:53 EDT, eric magaoay
no flags Details

  None (edit)
Description eric magaoay 2007-03-20 22:11:26 EDT
Description of problem:
virt-install failed after creating storage file. Below shows the traceback result.

Version-Release number of selected component (if applicable):
virt-manager 0.3.1-4.fc7.x86_64
python-virtinst 0.101.0-4.fc7.x86_64
libvirt 0.2.1-1.fc7.x86_64
kernel-xen 2.6.19-1.2898.2.3.fc7.x86_64
xen 3.0.4-9.fc7.x86_64

How reproducible:
persistent

Steps to Reproduce:
1. virt-install
 
Below is the console outputs:

[root@fiji3 images]# virt-install
What is the name of your virtual machine? v31f3  
 How much RAM should be allocated (in megabytes)? 500
 What would you like to use as the disk (path)? /var/lib/xen/images/v31f3.i
 How large would you like the disk (/var/lib/xen/images/v31f3.i) to be (in
gigabytes)? 6
 Would you like to enable graphics support? (yes or no) yes
 What is the install location? http://192.168.3.102/a/fed/x86_64/os

Starting install...
Retrieving RPM-GPG-KEY... 100% |=========================| 1.9 kB    00:00     
Retrieving vmlinuz...     100% |=========================| 2.0 MB    00:00     
Retrieving initrd.img...  100% |=========================| 5.6 MB    00:00     
Creating storage file...  100% |=========================| 6.0 GB    00:00     
taillibvir: Xen Daemon error : POST operation failed: (xend.err 'Device 0 (vif)
could not be connected. Hotplug scripts not working.')
Traceback (most recent call last):
  File "/usr/sbin/virt-install", line 484, in <module>
    main()
  File "/usr/sbin/virt-install", line 445, in main
    dom = guest.start_install(conscb,progresscb)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 476, in
start_install
    return self._do_install(consolecb, meter)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 493, in
_do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib64/python2.5/site-packages/libvirt.py", line 429, 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. Hotplug scripts not working.')
Comment 1 eric magaoay 2007-03-20 22:11:26 EDT
Created attachment 150548 [details]
xend.log file
Comment 2 Daniel Berrange 2007-03-20 22:18:53 EDT
Does xenbr2  exist as a bridge device, and if so, did you see any SELinux AVC
errors reported perhaps ? The latest Xen ought to give a sane error message if
the former occurred, so I can only suspect the latter based on the logs.
Comment 3 eric magaoay 2007-03-21 13:05:55 EDT
Yes xenbr2 does exist as bridge device. I didn't see any AVC error, but to put
selinux out of the equation I disabled it by executing "setenforce 0". Same problem.

My guess of the problem: 
virt-install is trying to configure and install from the first network (eth1,
which it found first) rather than from the preferred second network (eth2, where
the install source is located). Maybe xen couldn't properly configure all the
virtual interfaces required for multiple LAN cards. I have 3 LAN cards currently
installed. 

When I get a chance I'll try having only one LAN card and see if it works.
Comment 4 eric magaoay 2007-03-22 14:51:23 EDT
Created attachment 150689 [details]
screenshot of initial kernel bootup
Comment 5 eric magaoay 2007-03-22 14:53:36 EDT
Created attachment 150691 [details]
setroubleshooter output preventing xen to read config.sxp
Comment 6 eric magaoay 2007-03-23 16:57:28 EDT
With the latest devel build, everything works with the exception of selinux
blocking the virt-manager from proceeding. 

I will close this one and open another for selinux problem.

Comment 7 Red Hat Bugzilla 2007-07-24 22:07:52 EDT
change QA contact
Comment 8 Cole Robinson 2008-01-30 10:26:41 EST
Reported said this is working now so I'm going to close this.

Note You need to log in before you can comment on or make changes to this bug.