Thanks for the suggestions. It still does not work.
I also set SELinux to permissive mode to eliminate that potential source
of problems.
Using virt-manager to create the fully virtualized host results in the
following error (basically the same):
Unable to complete install 'libvirt.libvirtError virDomainCreateLinux()
failed POST operation failed: (xend.err 'Device 0 (vif) could not be
connected. Hotplug scripts not working.')
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/create.py", line 681, in
do_install
dom = guest.start_install(False, meter = meter)
File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 649,
in start_install
return self._do_install(consolecb, meter)
File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 666,
in _do_install
self.domain = self.conn.createLinux(install_xml, 0)
File "/usr/lib/python2.4/site-packages/libvirt.py", line 503, 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. Hotplug scripts not
working.')
'
At this point, I have to restart xend (it seems to die when the "xm
create" fails).
---Kayvan
-----Original Message-----
From: Jarod Wilson [mailto:jwilson@xxxxxxxxxx]
Sent: Tuesday, November 13, 2007 6:46 PM
To: Kayvan Sylvan
Cc: xen-ia64-devel
Subject: Re: [Xen-ia64-devel] IA64 using Redhat 5.1: xm create fails:
Hotplugscripts not working.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Zhang, Xing Z wrote:
> Do you check your "disk" parameter is right?
> "Error: Device 768 (vbd) could not be connected. Hotplug scripts
> not working." often has relation to un-correct disk image path or you
mount the image somewhere but forget unmount it.
> In the newest XEN/IA64 changeset, the error info is more readable, you
can update to a new one.
> If you want to debug it, see /var/log/xen/xend.log and search key word
"Error". Then you can get a series of python error info.
> The python code of Xend is at /usr/lib/python/xen. Good luck.
Two other suggestions...
1) the vbd not connecting *could* be selinux preventing usage of the
disk image, so you may be able to start the guest up correctly after
running 'setenforce 0' (or booting with selinux in permissive or
disabled mode).
2) try creating the guest using virt-manager. Always works for me.
>> -----Original Message-----
>> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On
>> Behalf Of Kayvan Sylvan
>> Sent: 2007?11?14? 8:43
>> To: Tristan Gingold
>> Cc: xen-ia64-devel
>> Subject: RE: [Xen-ia64-devel] IA64 using Redhat 5.1: xm create
>> fails: Hotplugscripts not working.
>>
>> I tried commenting the vif= line out and I get:
>>
>> Error: Device 768 (vbd) could not be connected. Hotplug scripts
>> not
>> working.
>>
>> I'm also not getting a console or anything else that I can
>> interact
>> with.
>>
>> I'm not sure how to proceed to try to debug this.
>>
- --
Jarod Wilson
jwilson@xxxxxxxxxx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHOmFLtO+bni+75QMRAr0zAKC7Te5Xh/dJO7fOKhRB9WBax821YwCgo7Zh
bi6v3YfTXD2LGaAK84AE4so=
=h6tC
-----END PGP SIGNATURE-----
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home