On 02/02/2012 09:07 AM, Cheer Xiao wrote: > 2012/2/2 Cole Robinson <crobinso@xxxxxxxxxx>: >> On 02/02/2012 08:54 AM, Cheer Xiao wrote: >>> 2012/2/2 Cole Robinson <crobinso@xxxxxxxxxx>: >>>> 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
