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

Re: [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 redhat com>:
>> On 02/02/2012 08:54 AM, Cheer Xiao wrote:
>>> 2012/2/2 Cole Robinson <crobinso 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=b5b2328c22ccffb17f7710b3ed6064907d744215;hb=HEAD#l2563
>>>>
>>>> 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


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