Re: [libvirt] [virt-tools-list] Provision through virt-manager not supported on para-virtualized Xen?
8:01 a.m.
On 02/02/2012 08:54 AM, Cheer Xiao wrote:
2012/2/2 Cole Robinson <crobinso(a)redhat.com>:
> On 02/02/2012 08:05 AM, Cheer Xiao wrote:
>> Hi all,
>>
>> I was setting up libvirt and virt-manager for managing Xen VMs. But
>> when I hit "New" in virt-manager to provision a new VM, virt-manager
>> gives me the error: "No install options available for this
>> connection."
>>
>> The hypervisor being used is para-virtualized Xen, running on Debian Squeeze.
>>
>> lux-002# xm info
>> host          : lux-002
>> release         : 2.6.32-5-xen-686
>> version         : #1 SMP Mon Jan 16 19:46:09 UTC 2012
>> machine         : i686
>> nr_cpus         : 4
>> nr_nodes        : 1
>> cores_per_socket    : 1
>> threads_per_core    : 2
>> cpu_mhz         : 3200
>> hw_caps         :
>> bfebfbff:20100000:00000000:00000180:0000641d:00000000:00000001:00000000
>> virt_caps        :
>> total_memory      : 8191
>> free_memory       : 1150
>> node_to_cpu       : node0:0-3
>> node_to_memory     : node0:1150
>> node_to_dma32_mem    : node0:578
>> max_node_id       : 0
>> xen_major        : 4
>> xen_minor        : 0
>> xen_extra        : .1
>> xen_caps        : xen-3.0-x86_32p
>> xen_scheduler      : credit
>> xen_pagesize      : 4096
>> platform_params     : virt_start=0xf5800000
>> xen_changeset      : unavailable
>> xen_commandline     : placeholder com1=9600,8n1 console=com1,vga
>> cc_compiler       : gcc version 4.4.5 (Debian 4.4.5-8)
>> cc_compile_by      : waldi
>> cc_compile_domain    : debian.org
>> cc_compile_date     : Mon Nov  7 09:18:26 CET 2011
>> xend_config_format   : 4
>> lux-002# libvirtd --version
>> libvirtd (libvirt) 0.8.3
>>
>
> libvirt pokes into the host machine to try and figure out it's virt
> capabilities. So something must be going wrong there. Here's the function it
> uses in libvirt code:
>
>
http://libvirt.org/git/?p=libvirt.git;a=blob;f=src/xen/xen_hypervisor.c;h...
>
> Something must be funky or unexpected with /sys/hypervisor/properties/capabilities
>
This is how it looks:
lux-002% cat /sys/hypervisor/properties/capabilities
xen-3.0-x86_32p
So, is provision through on para-virtualized Xen *supposed* to be
supported or not?
That is saying your host supports 32bit paravirt guests only.
What's the output of 'virsh --connect xen:/// capabilities' ?
- Cole
8:07 a.m.
New subject: [libvirt] [virt-tools-list] Provision through virt-manager not supported on para-virtualized Xen?
2012/2/2 Cole Robinson <crobinso(a)redhat.com>:
On 02/02/2012 08:54 AM, Cheer Xiao wrote:
> 2012/2/2 Cole Robinson <crobinso(a)redhat.com>:
>> On 02/02/2012 08:05 AM, Cheer Xiao wrote:
>>> Hi all,
>>>
>>> I was setting up libvirt and virt-manager for managing Xen VMs. But
>>> when I hit "New" in virt-manager to provision a new VM,
virt-manager
>>> gives me the error: "No install options available for this
>>> connection."
>>>
>>> The hypervisor being used is para-virtualized Xen, running on Debian
Squeeze.
>>>
>>> lux-002# xm info
>>> host          : lux-002
>>> release         : 2.6.32-5-xen-686
>>> version         : #1 SMP Mon Jan 16 19:46:09 UTC 2012
>>> machine         : i686
>>> nr_cpus         : 4
>>> nr_nodes        : 1
>>> cores_per_socket    : 1
>>> threads_per_core    : 2
>>> cpu_mhz         : 3200
>>> hw_caps         :
>>> bfebfbff:20100000:00000000:00000180:0000641d:00000000:00000001:00000000
>>> virt_caps        :
>>> total_memory      : 8191
>>> free_memory       : 1150
>>> node_to_cpu       : node0:0-3
>>> node_to_memory     : node0:1150
>>> node_to_dma32_mem    : node0:578
>>> max_node_id       : 0
>>> xen_major        : 4
>>> xen_minor        : 0
>>> xen_extra        : .1
>>> xen_caps        : xen-3.0-x86_32p
>>> xen_scheduler      : credit
>>> xen_pagesize      : 4096
>>> platform_params     : virt_start=0xf5800000
>>> xen_changeset      : unavailable
>>> xen_commandline     : placeholder com1=9600,8n1 console=com1,vga
>>> cc_compiler       : gcc version 4.4.5 (Debian 4.4.5-8)
>>> cc_compile_by      : waldi
>>> cc_compile_domain    : debian.org
>>> cc_compile_date     : Mon Nov  7 09:18:26 CET 2011
>>> xend_config_format   : 4
>>> lux-002# libvirtd --version
>>> libvirtd (libvirt) 0.8.3
>>>
>>
>> libvirt pokes into the host machine to try and figure out it's virt
>> capabilities. So something must be going wrong there. Here's the function it
>> uses in libvirt code:
>>
>>
http://libvirt.org/git/?p=libvirt.git;a=blob;f=src/xen/xen_hypervisor.c;h...
>>
>> Something must be funky or unexpected with
/sys/hypervisor/properties/capabilities
>>
>
> This is how it looks:
>
> lux-002% cat /sys/hypervisor/properties/capabilities
> xen-3.0-x86_32p
>
> So, is provision through on para-virtualized Xen *supposed* to be
> supported or not?
>
Uh... So I guess it's supposed to be supported
That is saying your host supports 32bit paravirt guests only.
What's the output of 'virsh --connect xen:/// capabilities' ?
blackie% virsh -c xen+ssh://lux-002 capabilities
<capabilities>
<host>
<cpu>
<arch>i686</arch>
<features>
<pae/>
</features>
</cpu>
<migration_features>
<live/>
<uri_transports>
<uri_transport>xenmigr</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num='1'>
<cell id='0'>
<cpus num='4'>
<cpu id='0'/>
<cpu id='1'/>
<cpu id='2'/>
<cpu id='3'/>
</cpus>
</cell>
</cells>
</topology>
</host>
<guest>
<os_type>xen</os_type>
<arch name='i686'>
<wordsize>32</wordsize>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<machine>xenpv</machine>
<domain type='xen'>
</domain>
</arch>
<features>
<pae/>
</features>
</guest>
</capabilities>
--
Regards,
Cheer Xiao aka. xiaq
8:18 a.m.
New subject: [libvirt] [virt-tools-list] Provision through virt-manager not supported on para-virtualized Xen?
On 02/02/2012 09:07 AM, Cheer Xiao wrote:
2012/2/2 Cole Robinson <crobinso(a)redhat.com>:
> On 02/02/2012 08:54 AM, Cheer Xiao wrote:
>> 2012/2/2 Cole Robinson <crobinso(a)redhat.com>:
>>> On 02/02/2012 08:05 AM, Cheer Xiao wrote:
>>>> Hi all,
>>>>
>>>> I was setting up libvirt and virt-manager for managing Xen VMs. But
>>>> when I hit "New" in virt-manager to provision a new VM,
virt-manager
>>>> gives me the error: "No install options available for this
>>>> connection."
>>>>
>>>> The hypervisor being used is para-virtualized Xen, running on Debian
Squeeze.
>>>>
>>>> lux-002# xm info
>>>> host à  à  à  à  à  à  à  à  à  : lux-002
>>>> release à  à  à  à  à  à  à  à : 2.6.32-5-xen-686
>>>> version à  à  à  à  à  à  à  à : #1 SMP Mon Jan 16
19:46:09 UTC 2012
>>>> machine à  à  à  à  à  à  à  à : i686
>>>> nr_cpus à  à  à  à  à  à  à  à : 4
>>>> nr_nodes à  à  à  à  à  à  à  : 1
>>>> cores_per_socket à  à  à  : 1
>>>> threads_per_core à  à  à  : 2
>>>> cpu_mhz à  à  à  à  à  à  à  à : 3200
>>>> hw_caps à  à  à  à  à  à  à  à :
>>>> bfebfbff:20100000:00000000:00000180:0000641d:00000000:00000001:00000000
>>>> virt_caps à  à  à  à  à  à  à :
>>>> total_memory à  à  à  à  à  : 8191
>>>> free_memory à  à  à  à  à  à : 1150
>>>> node_to_cpu à  à  à  à  à  à : node0:0-3
>>>> node_to_memory à  à  à  à  : node0:1150
>>>> node_to_dma32_mem à  à  à : node0:578
>>>> max_node_id à  à  à  à  à  à : 0
>>>> xen_major à  à  à  à  à  à  à : 4
>>>> xen_minor à  à  à  à  à  à  à : 0
>>>> xen_extra à  à  à  à  à  à  à : .1
>>>> xen_caps à  à  à  à  à  à  à  : xen-3.0-x86_32p
>>>> xen_scheduler à  à  à  à  à : credit
>>>> xen_pagesize à  à  à  à  à  : 4096
>>>> platform_params à  à  à  à : virt_start=0xf5800000
>>>> xen_changeset à  à  à  à  à : unavailable
>>>> xen_commandline à  à  à  à : placeholder com1=9600,8n1
console=com1,vga
>>>> cc_compiler à  à  à  à  à  à : gcc version 4.4.5 (Debian
4.4.5-8)
>>>> cc_compile_by à  à  à  à  à : waldi
>>>> cc_compile_domain à  à  à : debian.org
>>>> cc_compile_date à  à  à  à : Mon Nov à 7 09:18:26 CET 2011
>>>> xend_config_format à  à  : 4
>>>> lux-002# libvirtd --version
>>>> libvirtd (libvirt) 0.8.3
>>>>
>>>
>>> libvirt pokes into the host machine to try and figure out it's virt
>>> capabilities. So something must be going wrong there. Here's the function
it
>>> uses in libvirt code:
>>>
>>>
http://libvirt.org/git/?p=libvirt.git;a=blob;f=src/xen/xen_hypervisor.c;h...
>>>
>>> Something must be funky or unexpected with
/sys/hypervisor/properties/capabilities
>>>
>>
>> This is how it looks:
>>
>> lux-002% cat /sys/hypervisor/properties/capabilities
>> xen-3.0-x86_32p
>>
>> So, is provision through on para-virtualized Xen *supposed* to be
>> supported or not?
>>
Uh... So I guess it's supposed to be supported
Yes, sorry, libvirt and virt-manager/virt-install do support this config.
>
> That is saying your host supports 32bit paravirt guests only.
>
> What's the output of 'virsh --connect xen:/// capabilities' ?
blackie% virsh -c xen+ssh://lux-002 capabilities
<capabilities>
<host>
<cpu>
<arch>i686</arch>
<features>
<pae/>
</features>
</cpu>
<migration_features>
<live/>
<uri_transports>
<uri_transport>xenmigr</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num='1'>
<cell id='0'>
<cpus num='4'>
<cpu id='0'/>
<cpu id='1'/>
<cpu id='2'/>
<cpu id='3'/>
</cpus>
</cell>
</cells>
</topology>
</host>
<guest>
<os_type>xen</os_type>
<arch name='i686'>
<wordsize>32</wordsize>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<machine>xenpv</machine>
<domain type='xen'>
</domain>
</arch>
<features>
<pae/>
</features>
</guest>
</capabilities>
Okay, libvirt is detecting things correctly. So why is virt-manager confused?
Using that capabilities output works for me.
What virt-manager version are you using? Can you run virt-manager with
--debug, connect to xen, open the 'new vm' wizard that shows the error, and
post the debug output here?
Thanks,
Cole
9:53 a.m.
New subject: [libvirt] [virt-tools-list] Provision through virt-manager not supported on para-virtualized Xen?
2012/2/2 Cole Robinson <crobinso(a)redhat.com>:
... [snip] ...
Okay, libvirt is detecting things correctly. So why is virt-manager confused?
Using that capabilities output works for me.
What virt-manager version are you using? Can you run virt-manager with
--debug, connect to xen, open the 'new vm' wizard that shows the error, and
post the debug output here?
The ouput is pasted. I also made a screenshot and uploaded to [1]. And
another unrelated question: does the output says virt-manager uses HAL
for physical network interface management? I suppose HAL is
obsolete...
blackie% virt-manager --version
0.9.0
blackie% virt-manager --debug
2012-02-02 23:49:04,992 (cli:71): virt-manager startup
2012-02-02 23:49:04,992 (virt-manager:292): Launched as:
/usr/share/virt-manager/virt-manager.py --debug
2012-02-02 23:49:04,993 (virt-manager:293): GTK version: (2, 24, 9)
2012-02-02 23:49:04,993 (virt-manager:294): virtManager import:
<module 'virtManager' from
'/usr/share/virt-manager/virtManager/__init__.py'>
2012-02-02 23:49:05,116 (keyring:30): gnomekeyring bindings not
installed, no keyring support
2012-02-02 23:49:05,391 (engine:555): No inspection thread because
libguestfs is too old, not available, or libvirt is not thread safe.
2012-02-02 23:49:05,396 (engine:346): About to connect to uris
['xen+ssh://lux-003/', 'xen+ssh://major/', 'xen+ssh://lux-002/',
'qemu:///system']
2012-02-02 23:49:05,555 (engine:471): window counter incremented to 1
2012-02-02 23:49:14,633 (connection:954): Scheduling background open
thread for xen+ssh://lux-002/
2012-02-02 23:49:14,633 (connection:1140): Background 'open
connection' thread is running
2012-02-02 23:49:16,082 (connection:1168): Background open thread
complete, scheduling notify
2012-02-02 23:49:16,082 (connection:1173): Notifying open result
2012-02-02 23:49:18,120 (connection:1180): xen+ssh://lux-002/ capabilities:
<capabilities>
<host>
<cpu>
<arch>i686</arch>
<features>
<pae/>
</features>
</cpu>
<migration_features>
<live/>
<uri_transports>
<uri_transport>xenmigr</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num='1'>
<cell id='0'>
<cpus num='4'>
<cpu id='0'/>
<cpu id='1'/>
<cpu id='2'/>
<cpu id='3'/>
</cpus>
</cell>
</cells>
</topology>
</host>
<guest>
<os_type>xen</os_type>
<arch name='i686'>
<wordsize>32</wordsize>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<machine>xenpv</machine>
<domain type='xen'>
</domain>
</arch>
<features>
<pae/>
</features>
</guest>
</capabilities>
2012-02-02 23:49:20,336 (connection:514): Connection doesn't seem to
support interface APIs. Skipping all interface polling.
2012-02-02 23:49:27,777 (connection:570): Connection managed save support: False
2012-02-02 23:49:28,877 (halhelper:133): Unable to connect to HAL to
list network devices: org.freedesktop.DBus.Error.ServiceUnknown: The
name org.freedesktop.Hal was not provided by any .service files
2012-02-02 23:49:28,877 (connection:157): Libvirt version does not
support physical interface listing
2012-02-02 23:49:28,879 (connection:200): Using libvirt API for
mediadev enumeration
2012-02-02 23:49:55,510 (create:832): Guest type set to os_type=xen,
arch=i686, dom_type=xen
1. http://ftp.tuna.tsinghua.edu.cn/xiaqs/screenshot-new-vm.png
--
Regards,
Cheer Xiao aka. xiaq
8:01 a.m.
New subject: [libvirt] [virt-tools-list] Provision through virt-manager not supported on para-virtualized Xen?
On 02/02/2012 10:53 AM, Cheer Xiao wrote:
2012/2/2 Cole Robinson <crobinso(a)redhat.com>:
> ... [snip] ...
>
> Okay, libvirt is detecting things correctly. So why is virt-manager confused?
> Using that capabilities output works for me.
>
> What virt-manager version are you using? Can you run virt-manager with
> --debug, connect to xen, open the 'new vm' wizard that shows the error, and
> post the debug output here?
The ouput is pasted. I also made a screenshot and uploaded to [1]. And
another unrelated question: does the output says virt-manager uses HAL
for physical network interface management? I suppose HAL is
obsolete...
blackie% virt-manager --version
0.9.0
blackie% virt-manager --debug
2012-02-02 23:49:04,992 (cli:71): virt-manager startup
2012-02-02 23:49:04,992 (virt-manager:292): Launched as:
/usr/share/virt-manager/virt-manager.py --debug
2012-02-02 23:49:04,993 (virt-manager:293): GTK version: (2, 24, 9)
2012-02-02 23:49:04,993 (virt-manager:294): virtManager import:
<module 'virtManager' from
'/usr/share/virt-manager/virtManager/__init__.py'>
2012-02-02 23:49:05,116 (keyring:30): gnomekeyring bindings not
installed, no keyring support
2012-02-02 23:49:05,391 (engine:555): No inspection thread because
libguestfs is too old, not available, or libvirt is not thread safe.
2012-02-02 23:49:05,396 (engine:346): About to connect to uris
['xen+ssh://lux-003/', 'xen+ssh://major/', 'xen+ssh://lux-002/',
'qemu:///system']
2012-02-02 23:49:05,555 (engine:471): window counter incremented to 1
2012-02-02 23:49:14,633 (connection:954): Scheduling background open
thread for xen+ssh://lux-002/
2012-02-02 23:49:14,633 (connection:1140): Background 'open
connection' thread is running
2012-02-02 23:49:16,082 (connection:1168): Background open thread
complete, scheduling notify
2012-02-02 23:49:16,082 (connection:1173): Notifying open result
2012-02-02 23:49:18,120 (connection:1180): xen+ssh://lux-002/ capabilities:
<capabilities>
<host>
<cpu>
<arch>i686</arch>
<features>
<pae/>
</features>
</cpu>
<migration_features>
<live/>
<uri_transports>
<uri_transport>xenmigr</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num='1'>
<cell id='0'>
<cpus num='4'>
<cpu id='0'/>
<cpu id='1'/>
<cpu id='2'/>
<cpu id='3'/>
</cpus>
</cell>
</cells>
</topology>
</host>
<guest>
<os_type>xen</os_type>
<arch name='i686'>
<wordsize>32</wordsize>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<machine>xenpv</machine>
<domain type='xen'>
</domain>
</arch>
<features>
<pae/>
</features>
</guest>
</capabilities>
2012-02-02 23:49:20,336 (connection:514): Connection doesn't seem to
support interface APIs. Skipping all interface polling.
2012-02-02 23:49:27,777 (connection:570): Connection managed save support: False
2012-02-02 23:49:28,877 (halhelper:133): Unable to connect to HAL to
list network devices: org.freedesktop.DBus.Error.ServiceUnknown: The
name org.freedesktop.Hal was not provided by any .service files
2012-02-02 23:49:28,877 (connection:157): Libvirt version does not
support physical interface listing
2012-02-02 23:49:28,879 (connection:200): Using libvirt API for
mediadev enumeration
2012-02-02 23:49:55,510 (create:832): Guest type set to os_type=xen,
arch=i686, dom_type=xen
1. http://ftp.tuna.tsinghua.edu.cn/xiaqs/screenshot-new-vm.png
Okay, none of that indicates why it isn't working. I can't reproduce using
your capabilities output and virt-manager 0.9.0 either (though I hacked it in
so I could have missed a detail).
Can you try with current upstream?
git clone git://git.fedorahosted.org/virt-manager.git
git clone git://git.fedorahosted.org/python-virtinst.git
cd python-virtinst
python setup.py build
cd ../virt-manager
./autogen.sh && ./configure && make -j4
# Then after you can launch virt-manager with
PYTHONPATH=../python-virtinst python src/virt-manager.py --debug
See if you can reproduce, and if so please provide debug output and we can go
from there.
- Cole
8:52 a.m.
New subject: [libvirt] [virt-tools-list] Provision through virt-manager not supported on para-virtualized Xen?
2012/2/4 Cole Robinson <crobinso(a)redhat.com>:
... [snip] ...
Okay, none of that indicates why it isn't working. I can't reproduce using
your capabilities output and virt-manager 0.9.0 either (though I hacked it in
so I could have missed a detail).
Can you try with current upstream?
git clone git://git.fedorahosted.org/virt-manager.git
git clone git://git.fedorahosted.org/python-virtinst.git
cd python-virtinst
python setup.py build
cd ../virt-manager
./autogen.sh && ./configure && make -j4
# Then after you can launch virt-manager with
PYTHONPATH=../python-virtinst python src/virt-manager.py --debug
See if you can reproduce, and if so please provide debug output and we can go
from there.
Thanks! I'll be testing in a few days.
--
Regards,
Cheer Xiao aka. xiaq
6:58 a.m.
New subject: [libvirt] [virt-tools-list] Provision through virt-manager not supported on para-virtualized Xen?
2012/2/5 Cheer Xiao <xiaqqaix(a)gmail.com>:
2012/2/4 Cole Robinson <crobinso(a)redhat.com>:
> ... [snip] ...
> Okay, none of that indicates why it isn't working. I can't reproduce using
> your capabilities output and virt-manager 0.9.0 either (though I hacked it in
> so I could have missed a detail).
>
> Can you try with current upstream?
>
> git clone git://git.fedorahosted.org/virt-manager.git
> git clone git://git.fedorahosted.org/python-virtinst.git
> cd python-virtinst
> python setup.py build
> cd ../virt-manager
> ./autogen.sh && ./configure && make -j4
>
> # Then after you can launch virt-manager with
> PYTHONPATH=../python-virtinst python src/virt-manager.py --debug
>
> See if you can reproduce, and if so please provide debug output and we can go
> from there.
Thanks! I'll be testing in a few days.
The problem is still present, and I have collected the debug output. FYII,
* My laptop runs Archlinux and In Arch the default python is python3,
which makes it a little tricky to install python applications by hand.
Thus I tested on a VirtualBox guest, running Ubuntu 12.04. The remote
Xen host is the same.
* The PYTHONPATH trick didn't work for me, for some reason. So I did
`sudo python setup.py install` in python-virtinst and `sudo make
install` in virt-manager and ran just `virt-manager --debug`.
* python-virtinst and virt-manager are both compiled from HEAD of Git.
xiaq@vblackie ~/S/virt-manager> virt-manager --debug
** WARNING **: Trying to register gtype 'GMountMountFlags' as enum
when in fact it is of type 'GFlags'
** WARNING **: Trying to register gtype 'GDriveStartFlags' as enum
when in fact it is of type 'GFlags'
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
2012-02-06 20:52:17,589 (cli:71): virt-manager startup
2012-02-06 20:52:17,590 (virt-manager:291): Launched as:
/usr/local/share/virt-manager/virt-manager.py --debug
2012-02-06 20:52:17,590 (virt-manager:292): GTK version: (2, 24, 8)
2012-02-06 20:52:17,596 (virt-manager:293): virt-manager version: 0.9.1
2012-02-06 20:52:17,596 (virt-manager:294): virtManager import:
<module 'virtManager' from
'/usr/local/share/virt-manager/virtManager/__init__.py'>
2012-02-06 20:52:17,874 (cli:118): virtinst version: 0.600.1
2012-02-06 20:52:17,876 (cli:119): virtinst import: <module 'virtinst'
from '/usr/local/lib/python2.7/dist-packages/virtinst/__init__.pyc'>
/usr/local/share/virt-manager/virt-manager.py:305: DeprecationWarning:
Importing dbus.glib to use the GLib main loop with dbus-python is
deprecated.
Instead, use this sequence:
from dbus.mainloop.glib import DBusGMainLoop
DBusGMainLoop(set_as_default=True)
import dbus.glib
2012-02-06 20:52:18,490 (engine:555): No inspection thread because
libguestfs is too old, not available, or libvirt is not thread safe.
2012-02-06 20:52:18,501 (systray:138): Showing systray: False
2012-02-06 20:52:18,511 (engine:346): About to connect to uris
['xen+ssh://xiaq@lux-002/']
2012-02-06 20:52:18,736 (manager:171): Showing manager
2012-02-06 20:52:18,895 (engine:471): window counter incremented to 1
2012-02-06 20:52:29,286 (create:174): Showing new vm wizard
--
Regards,
Cheer Xiao aka. xiaq
7:01 a.m.
New subject: [libvirt] [virt-tools-list] Provision through virt-manager not supported on para-virtualized Xen?
2012/2/6 Cheer Xiao <xiaqqaix(a)gmail.com>:
2012/2/5 Cheer Xiao <xiaqqaix(a)gmail.com>:
> 2012/2/4 Cole Robinson <crobinso(a)redhat.com>:
>> ... [snip] ...
>> Okay, none of that indicates why it isn't working. I can't reproduce
using
>> your capabilities output and virt-manager 0.9.0 either (though I hacked it in
>> so I could have missed a detail).
>>
>> Can you try with current upstream?
>>
>> git clone git://git.fedorahosted.org/virt-manager.git
>> git clone git://git.fedorahosted.org/python-virtinst.git
>> cd python-virtinst
>> python setup.py build
>> cd ../virt-manager
>> ./autogen.sh && ./configure && make -j4
>>
>> # Then after you can launch virt-manager with
>> PYTHONPATH=../python-virtinst python src/virt-manager.py --debug
>>
>> See if you can reproduce, and if so please provide debug output and we can go
>> from there.
>
> Thanks! I'll be testing in a few days.
The problem is still present, and I have collected the debug output. FYII,
Sorry, wrong log. This is the correct version:
xiaq@vblackie ~/S/python-virtinst> virt-manager --debug
** WARNING **: Trying to register gtype 'GMountMountFlags' as enum
when in fact it is of type 'GFlags'
** WARNING **: Trying to register gtype 'GDriveStartFlags' as enum
when in fact it is of type 'GFlags'
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
2012-02-06 20:59:56,609 (cli:71): virt-manager startup
2012-02-06 20:59:56,618 (virt-manager:291): Launched as:
/usr/local/share/virt-manager/virt-manager.py --debug
2012-02-06 20:59:56,620 (virt-manager:292): GTK version: (2, 24, 8)
2012-02-06 20:59:56,621 (virt-manager:293): virt-manager version: 0.9.1
2012-02-06 20:59:56,621 (virt-manager:294): virtManager import:
<module 'virtManager' from
'/usr/local/share/virt-manager/virtManager/__init__.py'>
2012-02-06 20:59:56,873 (cli:118): virtinst version: 0.600.1
2012-02-06 20:59:56,875 (cli:119): virtinst import: <module 'virtinst'
from '/usr/local/lib/python2.7/dist-packages/virtinst/__init__.pyc'>
/usr/local/share/virt-manager/virt-manager.py:305: DeprecationWarning:
Importing dbus.glib to use the GLib main loop with dbus-python is
deprecated.
Instead, use this sequence:
from dbus.mainloop.glib import DBusGMainLoop
DBusGMainLoop(set_as_default=True)
import dbus.glib
2012-02-06 20:59:57,541 (engine:555): No inspection thread because
libguestfs is too old, not available, or libvirt is not thread safe.
2012-02-06 20:59:57,552 (systray:138): Showing systray: False
2012-02-06 20:59:57,566 (engine:346): About to connect to uris
['xen+ssh://xiaq@lux-002/']
2012-02-06 20:59:57,780 (manager:171): Showing manager
2012-02-06 20:59:57,946 (engine:471): window counter incremented to 1
2012-02-06 20:59:59,745 (connection:991): Scheduling background open
thread for xen+ssh://xiaq@lux-002/
2012-02-06 20:59:59,756 (connection:1177): Background 'open
connection' thread is running
xiaq@lux-002's password:
2012-02-06 21:00:04,097 (connection:1227): Background open thread
complete, scheduling notify
2012-02-06 21:00:04,102 (connection:1232): Notifying open result
2012-02-06 21:00:06,158 (connection:1239): xen+ssh://xiaq@lux-002/ capabilities:
<capabilities>
<host>
<cpu>
<arch>i686</arch>
<features>
<pae/>
</features>
</cpu>
<migration_features>
<live/>
<uri_transports>
<uri_transport>xenmigr</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num='1'>
<cell id='0'>
<cpus num='4'>
<cpu id='0'/>
<cpu id='1'/>
<cpu id='2'/>
<cpu id='3'/>
</cpus>
</cell>
</cells>
</topology>
</host>
<guest>
<os_type>xen</os_type>
<arch name='i686'>
<wordsize>32</wordsize>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<machine>xenpv</machine>
<domain type='xen'>
</domain>
</arch>
<features>
<pae/>
</features>
</guest>
</capabilities>
2012-02-06 21:00:08,648 (connection:551): Connection doesn't seem to
support interface APIs. Skipping all interface polling.
2012-02-06 21:00:15,772 (connection:607): Connection managed save support: False
2012-02-06 21:00:17,041 (halhelper:133): Unable to connect to HAL to
list network devices: org.freedesktop.DBus.Error.ServiceUnknown: The
name org.freedesktop.Hal was not provided by any .service files
2012-02-06 21:00:17,044 (connection:186): Libvirt version does not
support physical interface listing
2012-02-06 21:00:17,047 (connection:229): Using libvirt API for
mediadev enumeration
2012-02-06 21:00:24,328 (create:174): Showing new vm wizard
start None None None
after None None None
2012-02-06 21:00:24,439 (create:859): Guest type set to os_type=xen,
arch=i686, dom_type=xen
start xen xen None
after xen xen None
start xen xen i686
after xen xen i686
2012-02-06 21:00:35,392 (engine:426): Tick is slow, not running at
requested rate.
* My laptop runs Archlinux and In Arch the default python is
python3,
which makes it a little tricky to install python applications by hand.
Thus I tested on a VirtualBox guest, running Ubuntu 12.04. The remote
Xen host is the same.
* The PYTHONPATH trick didn't work for me, for some reason. So I did
`sudo python setup.py install` in python-virtinst and `sudo make
install` in virt-manager and ran just `virt-manager --debug`.
* python-virtinst and virt-manager are both compiled from HEAD of Git.
--
Regards,
Cheer Xiao aka. xiaq
10:03 a.m.
New subject: [libvirt] [virt-tools-list] Provision through virt-manager not supported on para-virtualized Xen?
On 02/06/2012 08:01 AM, Cheer Xiao wrote:
2012/2/6 Cheer Xiao <xiaqqaix(a)gmail.com>:
> 2012/2/5 Cheer Xiao <xiaqqaix(a)gmail.com>:
>> 2012/2/4 Cole Robinson <crobinso(a)redhat.com>:
>>> ... [snip] ...
>>> Okay, none of that indicates why it isn't working. I can't reproduce
using
>>> your capabilities output and virt-manager 0.9.0 either (though I hacked it
in
>>> so I could have missed a detail).
>>>
>>> Can you try with current upstream?
>>>
>>> git clone git://git.fedorahosted.org/virt-manager.git
>>> git clone git://git.fedorahosted.org/python-virtinst.git
>>> cd python-virtinst
>>> python setup.py build
>>> cd ../virt-manager
>>> ./autogen.sh && ./configure && make -j4
>>>
>>> # Then after you can launch virt-manager with
>>> PYTHONPATH=../python-virtinst python src/virt-manager.py --debug
>>>
>>> See if you can reproduce, and if so please provide debug output and we can
go
>>> from there.
>>
>> Thanks! I'll be testing in a few days.
>
> The problem is still present, and I have collected the debug output. FYII,
>
Sorry, wrong log. This is the correct version:
xiaq@vblackie ~/S/python-virtinst> virt-manager --debug
** WARNING **: Trying to register gtype 'GMountMountFlags' as enum
when in fact it is of type 'GFlags'
** WARNING **: Trying to register gtype 'GDriveStartFlags' as enum
when in fact it is of type 'GFlags'
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
2012-02-06 20:59:56,609 (cli:71): virt-manager startup
2012-02-06 20:59:56,618 (virt-manager:291): Launched as:
/usr/local/share/virt-manager/virt-manager.py --debug
2012-02-06 20:59:56,620 (virt-manager:292): GTK version: (2, 24, 8)
2012-02-06 20:59:56,621 (virt-manager:293): virt-manager version: 0.9.1
2012-02-06 20:59:56,621 (virt-manager:294): virtManager import:
<module 'virtManager' from
'/usr/local/share/virt-manager/virtManager/__init__.py'>
2012-02-06 20:59:56,873 (cli:118): virtinst version: 0.600.1
2012-02-06 20:59:56,875 (cli:119): virtinst import: <module 'virtinst'
from '/usr/local/lib/python2.7/dist-packages/virtinst/__init__.pyc'>
/usr/local/share/virt-manager/virt-manager.py:305: DeprecationWarning:
Importing dbus.glib to use the GLib main loop with dbus-python is
deprecated.
Instead, use this sequence:
from dbus.mainloop.glib import DBusGMainLoop
DBusGMainLoop(set_as_default=True)
import dbus.glib
2012-02-06 20:59:57,541 (engine:555): No inspection thread because
libguestfs is too old, not available, or libvirt is not thread safe.
2012-02-06 20:59:57,552 (systray:138): Showing systray: False
2012-02-06 20:59:57,566 (engine:346): About to connect to uris
['xen+ssh://xiaq@lux-002/']
2012-02-06 20:59:57,780 (manager:171): Showing manager
2012-02-06 20:59:57,946 (engine:471): window counter incremented to 1
2012-02-06 20:59:59,745 (connection:991): Scheduling background open
thread for xen+ssh://xiaq@lux-002/
2012-02-06 20:59:59,756 (connection:1177): Background 'open
connection' thread is running
xiaq@lux-002's password:
2012-02-06 21:00:04,097 (connection:1227): Background open thread
complete, scheduling notify
2012-02-06 21:00:04,102 (connection:1232): Notifying open result
2012-02-06 21:00:06,158 (connection:1239): xen+ssh://xiaq@lux-002/ capabilities:
<capabilities>
<host>
<cpu>
<arch>i686</arch>
<features>
<pae/>
</features>
</cpu>
<migration_features>
<live/>
<uri_transports>
<uri_transport>xenmigr</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num='1'>
<cell id='0'>
<cpus num='4'>
<cpu id='0'/>
<cpu id='1'/>
<cpu id='2'/>
<cpu id='3'/>
</cpus>
</cell>
</cells>
</topology>
</host>
<guest>
<os_type>xen</os_type>
<arch name='i686'>
<wordsize>32</wordsize>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<machine>xenpv</machine>
<domain type='xen'>
</domain>
</arch>
<features>
<pae/>
</features>
</guest>
</capabilities>
2012-02-06 21:00:08,648 (connection:551): Connection doesn't seem to
support interface APIs. Skipping all interface polling.
2012-02-06 21:00:15,772 (connection:607): Connection managed save support: False
2012-02-06 21:00:17,041 (halhelper:133): Unable to connect to HAL to
list network devices: org.freedesktop.DBus.Error.ServiceUnknown: The
name org.freedesktop.Hal was not provided by any .service files
2012-02-06 21:00:17,044 (connection:186): Libvirt version does not
support physical interface listing
2012-02-06 21:00:17,047 (connection:229): Using libvirt API for
mediadev enumeration
2012-02-06 21:00:24,328 (create:174): Showing new vm wizard
start None None None
after None None None
2012-02-06 21:00:24,439 (create:859): Guest type set to os_type=xen,
arch=i686, dom_type=xen
start xen xen None
after xen xen None
start xen xen i686
after xen xen i686
2012-02-06 21:00:35,392 (engine:426): Tick is slow, not running at
requested rate.
Hmm, okay, can you try applying the attached debugging patch to virt-manager
and reproduce again?
Thanks,
Cole
3:18 a.m.
New subject: [libvirt] [virt-tools-list] Provision through virt-manager not supported on para-virtualized Xen?
2012/2/7 Cole Robinson <crobinso(a)redhat.com>:
On 02/06/2012 08:01 AM, Cheer Xiao wrote:
> 2012/2/6 Cheer Xiao <xiaqqaix(a)gmail.com>:
>> 2012/2/5 Cheer Xiao <xiaqqaix(a)gmail.com>:
>>> 2012/2/4 Cole Robinson <crobinso(a)redhat.com>:
>>>> ... [snip] ...
>>>> Okay, none of that indicates why it isn't working. I can't
reproduce using
>>>> your capabilities output and virt-manager 0.9.0 either (though I hacked
it in
>>>> so I could have missed a detail).
>>>>
>>>> Can you try with current upstream?
>>>>
>>>> git clone git://git.fedorahosted.org/virt-manager.git
>>>> git clone git://git.fedorahosted.org/python-virtinst.git
>>>> cd python-virtinst
>>>> python setup.py build
>>>> cd ../virt-manager
>>>> ./autogen.sh && ./configure && make -j4
>>>>
>>>> # Then after you can launch virt-manager with
>>>> PYTHONPATH=../python-virtinst python src/virt-manager.py --debug
>>>>
>>>> See if you can reproduce, and if so please provide debug output and we
can go
>>>> from there.
>>>
>>> Thanks! I'll be testing in a few days.
>>
>> The problem is still present, and I have collected the debug output. FYII,
>>
>
> Sorry, wrong log. This is the correct version:
>
> xiaq@vblackie ~/S/python-virtinst> virt-manager --debug
>
> ** WARNING **: Trying to register gtype 'GMountMountFlags' as enum
> when in fact it is of type 'GFlags'
>
> ** WARNING **: Trying to register gtype 'GDriveStartFlags' as enum
> when in fact it is of type 'GFlags'
>
> Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
> 2012-02-06 20:59:56,609 (cli:71): virt-manager startup
> 2012-02-06 20:59:56,618 (virt-manager:291): Launched as:
> /usr/local/share/virt-manager/virt-manager.py --debug
> 2012-02-06 20:59:56,620 (virt-manager:292): GTK version: (2, 24, 8)
> 2012-02-06 20:59:56,621 (virt-manager:293): virt-manager version: 0.9.1
> 2012-02-06 20:59:56,621 (virt-manager:294): virtManager import:
> <module 'virtManager' from
> '/usr/local/share/virt-manager/virtManager/__init__.py'>
> 2012-02-06 20:59:56,873 (cli:118): virtinst version: 0.600.1
> 2012-02-06 20:59:56,875 (cli:119): virtinst import: <module 'virtinst'
> from '/usr/local/lib/python2.7/dist-packages/virtinst/__init__.pyc'>
> /usr/local/share/virt-manager/virt-manager.py:305: DeprecationWarning:
> Importing dbus.glib to use the GLib main loop with dbus-python is
> deprecated.
> Instead, use this sequence:
>
> from dbus.mainloop.glib import DBusGMainLoop
>
> DBusGMainLoop(set_as_default=True)
>
> import dbus.glib
> 2012-02-06 20:59:57,541 (engine:555): No inspection thread because
> libguestfs is too old, not available, or libvirt is not thread safe.
> 2012-02-06 20:59:57,552 (systray:138): Showing systray: False
> 2012-02-06 20:59:57,566 (engine:346): About to connect to uris
> ['xen+ssh://xiaq@lux-002/']
> 2012-02-06 20:59:57,780 (manager:171): Showing manager
> 2012-02-06 20:59:57,946 (engine:471): window counter incremented to 1
> 2012-02-06 20:59:59,745 (connection:991): Scheduling background open
> thread for xen+ssh://xiaq@lux-002/
> 2012-02-06 20:59:59,756 (connection:1177): Background 'open
> connection' thread is running
> xiaq@lux-002's password:
> 2012-02-06 21:00:04,097 (connection:1227): Background open thread
> complete, scheduling notify
> 2012-02-06 21:00:04,102 (connection:1232): Notifying open result
> 2012-02-06 21:00:06,158 (connection:1239): xen+ssh://xiaq@lux-002/ capabilities:
> <capabilities>
>
> <host>
> <cpu>
> <arch>i686</arch>
> <features>
> <pae/>
> </features>
> </cpu>
> <migration_features>
> <live/>
> <uri_transports>
> <uri_transport>xenmigr</uri_transport>
> </uri_transports>
> </migration_features>
> <topology>
> <cells num='1'>
> <cell id='0'>
> <cpus num='4'>
> <cpu id='0'/>
> <cpu id='1'/>
> <cpu id='2'/>
> <cpu id='3'/>
> </cpus>
> </cell>
> </cells>
> </topology>
> </host>
>
> <guest>
> <os_type>xen</os_type>
> <arch name='i686'>
> <wordsize>32</wordsize>
> <emulator>/usr/lib/xen/bin/qemu-dm</emulator>
> <machine>xenpv</machine>
> <domain type='xen'>
> </domain>
> </arch>
> <features>
> <pae/>
> </features>
> </guest>
>
> </capabilities>
>
> 2012-02-06 21:00:08,648 (connection:551): Connection doesn't seem to
> support interface APIs. Skipping all interface polling.
> 2012-02-06 21:00:15,772 (connection:607): Connection managed save support: False
> 2012-02-06 21:00:17,041 (halhelper:133): Unable to connect to HAL to
> list network devices: org.freedesktop.DBus.Error.ServiceUnknown: The
> name org.freedesktop.Hal was not provided by any .service files
> 2012-02-06 21:00:17,044 (connection:186): Libvirt version does not
> support physical interface listing
> 2012-02-06 21:00:17,047 (connection:229): Using libvirt API for
> mediadev enumeration
> 2012-02-06 21:00:24,328 (create:174): Showing new vm wizard
> start None None None
> after None None None
> 2012-02-06 21:00:24,439 (create:859): Guest type set to os_type=xen,
> arch=i686, dom_type=xen
> start xen xen None
> after xen xen None
> start xen xen i686
> after xen xen i686
> 2012-02-06 21:00:35,392 (engine:426): Tick is slow, not running at
> requested rate.
>
Hmm, okay, can you try applying the attached debugging patch to virt-manager
and reproduce again?
Patched against HEAD and got this debug output (for completeness I
also included the debug output after I hit the Cancel button of New VM
Wizard and then Exit button of virt-manager):
xiaq@vblackie ~> virt-manager --debug
** WARNING **: Trying to register gtype 'GMountMountFlags' as enum
when in fact it is of type 'GFlags'
** WARNING **: Trying to register gtype 'GDriveStartFlags' as enum
when in fact it is of type 'GFlags'
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
2012-02-09 17:15:00,053 (cli:71): virt-manager startup
2012-02-09 17:15:00,055 (virt-manager:291): Launched as:
/usr/local/share/virt-manager/virt-manager.py --debug
2012-02-09 17:15:00,056 (virt-manager:292): GTK version: (2, 24, 10)
2012-02-09 17:15:00,057 (virt-manager:293): virt-manager version: 0.9.1
2012-02-09 17:15:00,058 (virt-manager:294): virtManager import:
<module 'virtManager' from
'/usr/local/share/virt-manager/virtManager/__init__.py'>
2012-02-09 17:15:00,195 (cli:118): virtinst version: 0.600.1
2012-02-09 17:15:00,197 (cli:119): virtinst import: <module 'virtinst'
from '/usr/local/lib/python2.7/dist-packages/virtinst/__init__.pyc'>
/usr/local/share/virt-manager/virt-manager.py:305: DeprecationWarning:
Importing dbus.glib to use the GLib main loop with dbus-python is
deprecated.
Instead, use this sequence:
from dbus.mainloop.glib import DBusGMainLoop
DBusGMainLoop(set_as_default=True)
import dbus.glib
2012-02-09 17:15:00,777 (engine:555): No inspection thread because
libguestfs is too old, not available, or libvirt is not thread safe.
2012-02-09 17:15:00,786 (systray:138): Showing systray: False
2012-02-09 17:15:00,788 (engine:346): About to connect to uris
['xen+ssh://xiaq@lux-002/']
2012-02-09 17:15:00,974 (manager:171): Showing manager
2012-02-09 17:15:01,071 (engine:471): window counter incremented to 1
2012-02-09 17:15:08,640 (connection:991): Scheduling background open
thread for xen+ssh://xiaq@lux-002/
2012-02-09 17:15:08,651 (connection:1177): Background 'open
connection' thread is running
xiaq@lux-002's password:
2012-02-09 17:15:14,723 (connection:1227): Background open thread
complete, scheduling notify
2012-02-09 17:15:14,730 (connection:1232): Notifying open result
2012-02-09 17:15:16,775 (connection:1239): xen+ssh://xiaq@lux-002/ capabilities:
<capabilities>
<host>
<cpu>
<arch>i686</arch>
<features>
<pae/>
</features>
</cpu>
<migration_features>
<live/>
<uri_transports>
<uri_transport>xenmigr</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num='1'>
<cell id='0'>
<cpus num='4'>
<cpu id='0'/>
<cpu id='1'/>
<cpu id='2'/>
<cpu id='3'/>
</cpus>
</cell>
</cells>
</topology>
</host>
<guest>
<os_type>xen</os_type>
<arch name='i686'>
<wordsize>32</wordsize>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<machine>xenpv</machine>
<domain type='xen'>
</domain>
</arch>
<features>
<pae/>
</features>
</guest>
</capabilities>
2012-02-09 17:15:18,751 (connection:551): Connection doesn't seem to
support interface APIs. Skipping all interface polling.
2012-02-09 17:15:25,233 (connection:607): Connection managed save support: False
2012-02-09 17:15:26,279 (halhelper:133): Unable to connect to HAL to
list network devices: org.freedesktop.DBus.Error.ServiceUnknown: The
name org.freedesktop.Hal was not provided by any .service files
2012-02-09 17:15:26,283 (connection:186): Libvirt version does not
support physical interface listing
2012-02-09 17:15:26,286 (connection:229): Using libvirt API for
mediadev enumeration
2012-02-09 17:15:31,643 (create:174): Showing new vm wizard
caps <virtinst.CapabilitiesParser.Capabilities object at 0x2b66250>
conn no install options False
caps no install options False
my no install options: guest <virtinst.CapabilitiesParser.Guest object
at 0x2694890>
doms [<virtinst.CapabilitiesParser.Domain object at 0x2694950>]
False
reparsing capabilities
now my no install options: guest <virtinst.CapabilitiesParser.Guest
object at 0x26a9050>
doms [<virtinst.CapabilitiesParser.Domain object at 0x26a9210>]
False
2012-02-09 17:15:31,830 (create:878): Guest type set to os_type=xen,
arch=i686, dom_type=xen
2012-02-09 17:15:39,385 (create:181): Closing new vm wizard
2012-02-09 17:15:44,214 (manager:184): Closing manager
2012-02-09 17:15:44,220 (engine:475): window counter decremented to 0
2012-02-09 17:15:44,225 (manager:184): Closing manager
2012-02-09 17:15:44,242 (create:181): Closing new vm wizard
2012-02-09 17:15:44,260 (engine:548): Leaked <vmmConnection object at
0x2b62d20 (virtManager+connection+vmmConnection at 0x1b762a0)>
2012-02-09 17:15:44,261 (engine:548): Leaked <vmmNodeDevice object at
0x26a7460 (virtManager+nodedev+vmmNodeDevice at 0x2545560)>
2012-02-09 17:15:44,263 (engine:548): Leaked <vmmNodeDevice object at
0x26a7550 (virtManager+nodedev+vmmNodeDevice at 0x2bc4780)>
2012-02-09 17:15:44,264 (engine:548): Leaked <vmmDomain object at
0x26a7690 (virtManager+domain+vmmDomain at 0x254ac40)>
2012-02-09 17:15:44,265 (engine:548): Leaked <vmmMediaDevice object at
0x26a7b40 (virtManager+mediadev+vmmMediaDevice at 0x2554b60)>
2012-02-09 17:15:44,266 (engine:548): Leaked <vmmMediaDevice object at
0x26a7b90 (virtManager+mediadev+vmmMediaDevice at 0x2850960)>
2012-02-09 17:15:44,267 (engine:550): Exiting app normally.
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/local/share/virt-manager/virtManager/cli.py", line 82, in
exception_log
s = traceback.format_exception(typ, val, tb)
TypeError: 'NoneType' object is not callable
Original exception was:
Traceback (most recent call last):
File "/usr/local/share/virt-manager/virtManager/libvirtglib.py",
line 132, in glib_event_handle_update
state.lock.acquire()
AttributeError: 'NoneType' object has no attribute 'lock'
Unhandled exception in thread started by <bound method
Thread.__bootstrap of <Thread(Tick thread, stopped daemon
139928080676608)>>
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/local/share/virt-manager/virtManager/cli.py", line 82, in
exception_log
s = traceback.format_exception(typ, val, tb)
TypeError: 'NoneType' object is not callable
Original exception was:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 525, in __bootstrap
self.__bootstrap_inner()
File "/usr/lib/python2.7/threading.py", line 565, in __bootstrap_inner
(self.name, _format_exc()))
File "/usr/lib/python2.7/traceback.py", line 240, in format_exc
etype, value, tb = sys.exc_info()
AttributeError: 'NoneType' object has no attribute 'exc_info'
Exception AttributeError: "'NoneType' object has no attribute
'virNodeDeviceFree'" in <bound method virNodeDevice.__del__ of
<libvirt.virNodeDevice instance at 0x26a6200>> ignored
--
Regards,
Cheer Xiao aka. xiaq
9:07 a.m.
New subject: [libvirt] [virt-tools-list] Provision through virt-manager not supported on para-virtualized Xen?
On 02/09/2012 04:18 AM, Cheer Xiao wrote:
2012/2/7 Cole Robinson <crobinso(a)redhat.com>:
> On 02/06/2012 08:01 AM, Cheer Xiao wrote:
>> 2012/2/6 Cheer Xiao <xiaqqaix(a)gmail.com>:
>>> 2012/2/5 Cheer Xiao <xiaqqaix(a)gmail.com>:
>>>> 2012/2/4 Cole Robinson <crobinso(a)redhat.com>:
>>>>> ... [snip] ...
>>>>> Okay, none of that indicates why it isn't working. I can't
reproduce using
>>>>> your capabilities output and virt-manager 0.9.0 either (though I
hacked it in
>>>>> so I could have missed a detail).
>>>>>
>>>>> Can you try with current upstream?
>>>>>
>>>>> git clone git://git.fedorahosted.org/virt-manager.git
>>>>> git clone git://git.fedorahosted.org/python-virtinst.git
>>>>> cd python-virtinst
>>>>> python setup.py build
>>>>> cd ../virt-manager
>>>>> ./autogen.sh && ./configure && make -j4
>>>>>
>>>>> # Then after you can launch virt-manager with
>>>>> PYTHONPATH=../python-virtinst python src/virt-manager.py --debug
>>>>>
>>>>> See if you can reproduce, and if so please provide debug output and
we can go
>>>>> from there.
>>>>
>>>> Thanks! I'll be testing in a few days.
>>>
>>> The problem is still present, and I have collected the debug output. FYII,
>>>
>>
>> Sorry, wrong log. This is the correct version:
>>
>> xiaq@vblackie ~/S/python-virtinst> virt-manager --debug
>>
>> ** WARNING **: Trying to register gtype 'GMountMountFlags' as enum
>> when in fact it is of type 'GFlags'
>>
>> ** WARNING **: Trying to register gtype 'GDriveStartFlags' as enum
>> when in fact it is of type 'GFlags'
>>
>> Gtk-WARNING **: Unable to locate theme engine in module_path:
"pixmap",
>> 2012-02-06 20:59:56,609 (cli:71): virt-manager startup
>> 2012-02-06 20:59:56,618 (virt-manager:291): Launched as:
>> /usr/local/share/virt-manager/virt-manager.py --debug
>> 2012-02-06 20:59:56,620 (virt-manager:292): GTK version: (2, 24, 8)
>> 2012-02-06 20:59:56,621 (virt-manager:293): virt-manager version: 0.9.1
>> 2012-02-06 20:59:56,621 (virt-manager:294): virtManager import:
>> <module 'virtManager' from
>> '/usr/local/share/virt-manager/virtManager/__init__.py'>
>> 2012-02-06 20:59:56,873 (cli:118): virtinst version: 0.600.1
>> 2012-02-06 20:59:56,875 (cli:119): virtinst import: <module
'virtinst'
>> from '/usr/local/lib/python2.7/dist-packages/virtinst/__init__.pyc'>
>> /usr/local/share/virt-manager/virt-manager.py:305: DeprecationWarning:
>> Importing dbus.glib to use the GLib main loop with dbus-python is
>> deprecated.
>> Instead, use this sequence:
>>
>> Â Â from dbus.mainloop.glib import DBusGMainLoop
>>
>> Â Â DBusGMainLoop(set_as_default=True)
>>
>> Â import dbus.glib
>> 2012-02-06 20:59:57,541 (engine:555): No inspection thread because
>> libguestfs is too old, not available, or libvirt is not thread safe.
>> 2012-02-06 20:59:57,552 (systray:138): Showing systray: False
>> 2012-02-06 20:59:57,566 (engine:346): About to connect to uris
>> ['xen+ssh://xiaq@lux-002/']
>> 2012-02-06 20:59:57,780 (manager:171): Showing manager
>> 2012-02-06 20:59:57,946 (engine:471): window counter incremented to 1
>> 2012-02-06 20:59:59,745 (connection:991): Scheduling background open
>> thread for xen+ssh://xiaq@lux-002/
>> 2012-02-06 20:59:59,756 (connection:1177): Background 'open
>> connection' thread is running
>> xiaq@lux-002's password:
>> 2012-02-06 21:00:04,097 (connection:1227): Background open thread
>> complete, scheduling notify
>> 2012-02-06 21:00:04,102 (connection:1232): Notifying open result
>> 2012-02-06 21:00:06,158 (connection:1239): xen+ssh://xiaq@lux-002/ capabilities:
>> <capabilities>
>>
>> Â <host>
>> Â Â <cpu>
>> Â Â Â <arch>i686</arch>
>> Â Â Â <features>
>> Â Â Â Â <pae/>
>> Â Â Â </features>
>> Â Â </cpu>
>> Â Â <migration_features>
>> Â Â Â <live/>
>> Â Â Â <uri_transports>
>> Â Â Â Â <uri_transport>xenmigr</uri_transport>
>> Â Â Â </uri_transports>
>> Â Â </migration_features>
>> Â Â <topology>
>> Â Â Â <cells num='1'>
>> Â Â Â Â <cell id='0'>
>> Â Â Â Â Â <cpus num='4'>
>> Â Â Â Â Â Â <cpu id='0'/>
>> Â Â Â Â Â Â <cpu id='1'/>
>> Â Â Â Â Â Â <cpu id='2'/>
>> Â Â Â Â Â Â <cpu id='3'/>
>> Â Â Â Â Â </cpus>
>> Â Â Â Â </cell>
>> Â Â Â </cells>
>> Â Â </topology>
>> Â </host>
>>
>> Â <guest>
>> Â Â <os_type>xen</os_type>
>> Â Â <arch name='i686'>
>> Â Â Â <wordsize>32</wordsize>
>> Â Â Â <emulator>/usr/lib/xen/bin/qemu-dm</emulator>
>> Â Â Â <machine>xenpv</machine>
>> Â Â Â <domain type='xen'>
>> Â Â Â </domain>
>> Â Â </arch>
>> Â Â <features>
>> Â Â Â <pae/>
>> Â Â </features>
>> Â </guest>
>>
>> </capabilities>
>>
>> 2012-02-06 21:00:08,648 (connection:551): Connection doesn't seem to
>> support interface APIs. Skipping all interface polling.
>> 2012-02-06 21:00:15,772 (connection:607): Connection managed save support: False
>> 2012-02-06 21:00:17,041 (halhelper:133): Unable to connect to HAL to
>> list network devices: org.freedesktop.DBus.Error.ServiceUnknown: The
>> name org.freedesktop.Hal was not provided by any .service files
>> 2012-02-06 21:00:17,044 (connection:186): Libvirt version does not
>> support physical interface listing
>> 2012-02-06 21:00:17,047 (connection:229): Using libvirt API for
>> mediadev enumeration
>> 2012-02-06 21:00:24,328 (create:174): Showing new vm wizard
>> start None None None
>> after None None None
>> 2012-02-06 21:00:24,439 (create:859): Guest type set to os_type=xen,
>> arch=i686, dom_type=xen
>> start xen xen None
>> after xen xen None
>> start xen xen i686
>> after xen xen i686
>> 2012-02-06 21:00:35,392 (engine:426): Tick is slow, not running at
>> requested rate.
>>
>
> Hmm, okay, can you try applying the attached debugging patch to virt-manager
> and reproduce again?
Patched against HEAD and got this debug output (for completeness I
also included the debug output after I hit the Cancel button of New VM
Wizard and then Exit button of virt-manager):
Great, thanks for the info. I see the problem now, my confusion was that I was
looking at the wrong error message in the code, and that there were some
defects in the UI that were not reporting the problems very well. I've pushed
some tweaks upstream so that we are reporting more info in this case, and
actually allow import installs here.
Xen PV doesn't work with CDROM or PXE installs, so those are rightly disabled.
Since you are connecting to a remote machine, URL installs only work if you
have a new enough libvirt which it doesn't look like you do. Import installs
would work in your case, but a logic error was causing virt-manager not to
allow it.
I've changed the error reporting here to show the disabled install options
even if we think none are available, since we set tooltips on the disabled
entries that can provide more info.
But end result is that your setup as is doesn't support creating new VMs:
either update the remote libvirt version to 0.9.4 or later to get remote URL
install support, or ssh to the remote machine and install a VM using
virt-manager/virt-install.
Thanks,
Cole
4670
days inactive
4677
days old
10 comments
2 participants
participants (2)
-
Cheer Xiao -
Cole Robinson