[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [et-mgmt-tools] Virt-manager won't connect to Xen hypervisor

Hugh Brock wrote:
> Steve Brueckner wrote:
>> I've installed Fedora 7, Xen 3.1 (from source), and virt-manager 0.4
>> (from rpms).  The machine is VMX/VT-x capable.  I have managed to
>> build and run a paravirtualized Linux guest just fine.  Now I want to
>> build an HVM Linux guest, but virt-manager tells me "unable to open a
>> connection to the Xen hypervisor/daemon."  I've confirmed that both
>> xend and libvirtd are running. 
> We're going to need some more information: /var/log/xend/xend.log,
> /root/.virt-manager/virt-manager.log, and the libvirt version you are
> using. Are you using our xen 3.1 package (from Fedora 7) or
> XenSource's?   
I've attached the logs you requested, plus 4 xen config files in case 
the problem lies there.

I get no messages in /var/log/xend/xend.log when trying to use virt-
manager (not on app startup, not when error occurs, not on app 
shutdown).  But there are a whole lot of warnings about failed API calls 
during initial xend startup.

Since my first message, I have yum-updated my machine and now get a 
warning when starting virt-manager on the command line.  This warning 
seems unrelated to the connection problem, however:
***MEMORY-WARNING***: virt-manager.py[4554]: GSlice: g_thread_init() 
must be called before all other GLib functions; memory corruption due to 
late invocation of g_thread_init() has been detected; this program is 
likely to crash, leak or unexpectedly abort soon...

Here is my configuration:
Fedora 7   (fully updated)
Xen 3.1    (installed from XenSource tarball using vanilla kernel)
python-virtinst-0.103.0-3.fc7 (installed from Fedora 7 rpm)
libvirt-0.2.3-1.fc8           (installed from Fedora 7 rpm)
libvirt-python-0.2.3-1.fc8    (installed from Fedora 7 rpm)
virt-manager-0.4.0-2.fc7      (installed from Fedora 7 rpm)

I had to install Xen from source because the Fedora 7 rpms didn't work 
on my hardware: dom0 wouldn't boot.  This isn't the usual misconfigured 
grub or missing initrd or anything...this is an early hardware detection 
error.  I've been dealing with such errors for a while: Linux doesn't 
always play nicely with the new Intel 965 boards and also gets confused 
by sata optical drives.

It occurs to me that xend used to have 2 different connection options.  
Does it still?  Do I need to change a setting in one of the xend, xm, or 
xenapi config files?


Steve Brueckner, ATC-NY

Attachment: xm-config-xenapi.xml
Description: Binary data

Attachment: xm-config.xml
Description: Binary data

Attachment: xend-config-xenapi.sxp
Description: Binary data

Attachment: xend-config.sxp
Description: Binary data

Attachment: virt-manager.log
Description: Binary data

Attachment: xend.log
Description: Binary data

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]