[Fedora-xen] Re: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10
Pasi Kärkkäinen
pasik at iki.fi
Sat Mar 7 18:19:22 UTC 2009
On Sat, Mar 07, 2009 at 12:33:46PM -0500, Cole Robinson wrote:
> Pasi Kärkkäinen wrote:
> > Hello!
> >
> > I'm using Fedora 10 on my Xen pv_ops testing box.
> >
> > I rebuilt Xen 3.3.1-9 packages from F11/rawhide for Fedora 10 and installed them.
> >
> > http://kojipkgs.fedoraproject.org/packages/xen/3.3.1/9.fc11/src/xen-3.3.1-9.fc11.src.rpm
> >
> > xen-3.3.1-9.fc10.i386.rpm
> > xen-debuginfo-3.3.1-9.fc10.i386.rpm
> > xen-devel-3.3.1-9.fc10.i386.rpm
> > xen-hypervisor-3.3.1-9.fc10.i386.rpm
> > xen-libs-3.3.1-9.fc10.i386.rpm
> > xen-runtime-3.3.1-9.fc10.i386.rpm
> >
> > I also built custom 2.6.29-rc7 pv_ops dom0 kernel, which seems to boot OK
> > for me.
> >
> > xend starts OK, and I can run 'xm info', 'xm list' etc.
> >
> > But now I'm having problems using virt-install and/or virt-manager to
> > install new domains.
> >
> > [root at dom0test ~]# virt-install -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'
> >
> > Has Xen support been dropped from virt-install, or is this just some bug?
> >
>
> Xen support hasn't been dropped, we are probably just failing to detect
> that xen is available.
>
> First, can you try 'virsh --connect xen:///' and see if it succeeds? If
> that works, you can manually pass the connection string to virt-install
> in the interim (virt-install --connect xen:/// ...)
>
Yeah, that seems to work:
[root at dom0test ~]# virsh --connect xen:///
Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands
'quit' to quit
virsh # vcpuinfo 0
VCPU: 0
CPU: 0
State: running
CPU time: 32.3s
CPU Affinity: yy
VCPU: 1
CPU: 1
State: idle
CPU time: 18.9s
CPU Affinity: yy
virsh # version
Compiled against library: libvir 0.5.1
Using library: libvir 0.5.1
Using API: Xen 3.0.1
Running hypervisor: Xen 3.3.0
virsh # quit
[root at dom0test ~]# xm info
host : dom0test.localdomain
release : 2.6.29-rc7-tip
version : #10 SMP Sat Mar 7 16:04:28 EET 2009
machine : i686
nr_cpus : 2
nr_nodes : 1
cores_per_socket : 1
threads_per_core : 2
cpu_mhz : 3000
hw_caps :
bfebfbff:00000000:00000000:00000180:0000441d:00000000:00000000:00000000
virt_caps :
total_memory : 2038
free_memory : 992
node_to_cpu : node0:0-1
node_to_memory : node0:992
xen_major : 3
xen_minor : 3
xen_extra : .1-9.fc10
xen_caps : xen-3.0-x86_32p
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xf5800000
xen_changeset : unavailable
cc_compiler : gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) (GCC)
cc_compile_by : root
cc_compile_domain : localdomain
cc_compile_date : Fri Mar 6 17:24:19 EET 2009
xend_config_format : 4
> Can you also check if the following 3 locations exist:
>
> /var/lib/xend
> /dev/xen/evtchn
> /proc/xen
>
Yep, all of those do exist.
[root at dom0test ~]# ls /var/lib/xend
domains relocation-socket state storage xend-socket
[root at dom0test ~]# ls -la /dev/xen/evtchn
crw-rw---- 1 root root 10, 63 2009-03-07 20:10 /dev/xen/evtchn
[root at dom0test ~]# ls /proc/xen/
capabilities privcmd xenbus xsd_kva xsd_port
> That is what we check in virtinst to guess that xen is present, and we
> should use its connection by default. If one of those is missing, any
> recommendations on how to detect xen presence would be appreciated.
>
[root at 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?
And thanks!
-- Pasi
More information about the xen
mailing list