> What i am not sure about is libvirt,virtinst,... behavior when working
with Xen 4.0 on F13
Libvirt 0.7.7 and all related stuff (virsh,virt-manager,virt-install) seem to work fine
at Xen 4.0 Dom0 ( pvops 2.6.31.13) on top of F13. Even HVM install now could be performed via virt-manager.
Auto detecting Xen Hypervisor and several attempts suggesting KVM answered
negative make strong impression. I thought it would ask me to install KVM
every time at virt-manager start.
[root@FedoraSRV ~]# virsh version
Compiled against library: libvir 0.7.7
Using library: libvir 0.7.7
Using API: Xen 3.0.1
Running hypervisor: Xen 4.0.0
Boris.
--- On Sun, 5/16/10, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: Move from Fedora 8 dom0s to F12/F13 dom0s with Xen
4.0.x questions
To: xen@xxxxxxxxxxxxxxxxxxxxxxx, "fcxen user" <fcxen@xxxxxxxxxxxxxxxx>
Date: Sunday, May 16, 2010, 12:35 AM
> * I use "virsh define" to create the VM configurations using virsh xml,
and I
assume that virsh/libvirtd won't work on a recent 2.6.32/33/3x
kernel and Xen
4.0.0
> * Although Pasi, Michael, Dale and others have been very generous with
their
information, testing and development, I am not completely
clear on all the
steps required to get a working F12/F13/ Xen 4.0.X
dom0 with 2.6.32/33/3x
kernel starting from a base F12/F13 system
install. If someone can point out
where to find different parts I
would be grateful and would be willing to
consolidate them into a
single blob if that doesn't already exist.
Responding both questions (for F12) :-
http://www.linuxtoday.com/high_performance/2010041500635OSSV
What i am not sure about is libvirt,virtinst,... behavior when working with Xen 4.0 on F13
Boris.
|
-----Inline Attachment Follows-----
|
--
xen mailing list
xen@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/xen
