Pasi Kärkkäinen wrote: > On Sat, Mar 07, 2009 at 08:50:36PM +0200, Pasi Kärkkäinen wrote: >> On Sat, Mar 07, 2009 at 01:45:11PM -0500, Cole Robinson wrote: >>> Pasi Kärkkäinen wrote: >>>> [root@dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l >>>> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"; >>>> >>>> ERROR Unsupported virtualization type 'xen' >>>> >>>> Hmm.. so that didn't help unfortunately.. Other ideas? >>>> >>> Ah okay. Libvirt capabilities must be getting confused. Can you attach >>> the output of >>> >>> virsh --connect xen:/// capabilities >>> cat /sys/hypervisor/properties/capabilities >>> >> [root@dom0test ~]# virsh --connect xen:/// 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='2'> >> <cpu id='0'/> >> <cpu id='1'/> >> </cpus> >> </cell> >> </cells> >> </topology> >> </host> >> >> </capabilities> >> >> [root@dom0test ~]# cat /sys/hypervisor/properties/capabilities >> cat: /sys/hypervisor/properties/capabilities: No such file or directory >> > > [root@dom0test ~]# ls -la /sys/hypervisor > ls: cannot access /sys/hypervisor: No such file or directory > > Hmm, well that will do it. Libvirt capabilities are what tell user apps what types of domains can be installed, and generating xen capabilities is largely dependent on the above paths. Not too sure what to do from here. - Cole -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
