5:45 p.m.
I would like to try to move some dom0s from Fedora 8 to Fedora 12/13/Xen 4.0,
but I had a few questions. Some of these are probably repeats so I apologize
in advance.
* 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
Is there a way to extract the xm style configuration values from the running
VMs? Or a file somewhere so I can pull out/copy the VM configs for use on the
new machine or is there another way to do that? It has been since about Fedora
Core 5 that I used the xm style configs so I don't have that in my head like
many on this list do.
* I am using plain disk files for the storage for each VM, I understand that
Xen 4.0 has the ability to use these now with the correct kernel. Is that the
case? Would I be able to use my current (F10-F12) VMs as is?
* 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. I looked at
some of the wiki some on the xen wiki but I get a bit of choice overload from
those pages - you can use this kernel or that kernel or...
* If this were to work, would I see a performance increase or (hopefully not)
decrease for vanilla F10-F12 domUs (apache, etc) on the same hardware going
from Xen 3.1.4 on F8 to Xen 4.0.x on F12/F13 on Intel 5400/5500 based servers?
Thanks for any help.
One of the other reasons I want to upgrade is because I can no longer add VMs
with virt-install command line. I constantly get:
libvir: Xen Daemon error : GET operation failed: xend_get: error from xen daemon:
virDomainLookupByID() failed GET operation failed: xend_get: error from xen
daemon:
Even after upgrading to libvirtd 0.4.6-1.fc8 and even immediately after
rebooting the dom0 - which seemed to be a workaround for others that I read
about having this problem. I realize this is not the libvirtd list but a
couple of the replies to this problem that I have seen are along the lines of
"it is not a libvirt problem". And If it is not too painful to get the F12/F13
dom0s working with my old VMs, I hope to just forget all about this :)
11:35 p.m.
* 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.
12:44 p.m.
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(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x
questions
To: xen(a)lists.fedoraproject.org, "fcxen user" <fcxen(a)itsbeen.sent.com>
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(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
10:49 p.m.
I had to disable Xen bridging and setup bridge manually to be able to work with PV
guests . In other words all xen bridged networking has to be commented out on F13
and at the same time PV guest cannot obtain IP via virbr0
It doesn't happen on F12.
--- On Mon, 5/17/10, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x
questions
To: xen(a)lists.fedoraproject.org, "fcxen user" <fcxen(a)itsbeen.sent.com>
Date: Monday, May 17, 2010, 1:44 PM
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(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen
4.0.x questions
To: xen(a)lists.fedoraproject.org, "fcxen user" <fcxen(a)itsbeen.sent.com>
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(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
-----Inline Attachment Follows-----
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
1:11 a.m.
So, installed Xen 4.0 via MY's src.rpm on top F13 i had
to set up manually "br0" for PV Guests, HVM seems to be OK with NAT ( or br0 no
matter)
# chkconfig NetworkManager off
# chkconfig network on
Reboot
VNC console doesn't get launched for virt-installs of PV guests , referencing
"br0".
Virt-install should run in "nographics" mode with VNC setup at DomU for
Fedoras,CentOS guests.
I might did something wrong, but at the moment "Xen 4.0 /
Virt-manager&Virt-install" regression vs F12 is taken place.
Boris.
--- On Mon, 5/17/10, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x
questions
To: xen(a)lists.fedoraproject.org, "fcxen user" <fcxen(a)itsbeen.sent.com>
Date: Monday, May 17, 2010, 11:49 PM
I had to disable Xen bridging and setup bridge manually to be able to work with PV
guests . In other words all xen bridged networking has to be commented out on F13
and at the same time PV guest cannot obtain IP via virbr0
It doesn't happen on F12.
--- On Mon, 5/17/10, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x
questions
To: xen(a)lists.fedoraproject.org, "fcxen user" <fcxen(a)itsbeen.sent.com>
Date: Monday, May 17, 2010, 1:44 PM
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(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen
4.0.x questions
To: xen(a)lists.fedoraproject.org, "fcxen user" <fcxen(a)itsbeen.sent.com>
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(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
-----Inline Attachment Follows-----
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
-----Inline Attachment Follows-----
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
8 a.m.
With 2.6.32.13 RH's PV guests (F13,RHL6 Beta tested) do detect NAT interface
and can smoothly installed via virt-manager ( virt-install).
However, Ubuntu Lucid Official xenified installer is still failing with NAT and requires
old style network bridging, OSOL 134 behaves same way.
Boris.
--- On Tue, 5/18/10, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x
questions
To: xen(a)lists.fedoraproject.org, "fcxen user" <fcxen(a)itsbeen.sent.com>
Date: Tuesday, May 18, 2010, 2:11 AM
So, installed Xen 4.0 via MY's src.rpm on top F13 i had
to set up manually "br0" for PV Guests, HVM seems to be OK with NAT ( or br0 no
matter)
# chkconfig NetworkManager off
# chkconfig network on
Reboot
VNC console doesn't get launched for virt-installs of PV guests , referencing
"br0".
Virt-install should run in "nographics" mode with VNC setup at DomU for
Fedoras,CentOS guests.
I might did something wrong, but at the moment "Xen 4.0 /
Virt-manager&Virt-install" regression vs F12 is taken place.
Boris.
--- On Mon, 5/17/10, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13
dom0s with Xen 4.0.x questions
To: xen(a)lists.fedoraproject.org, "fcxen user" <fcxen(a)itsbeen.sent.com>
Date: Monday, May 17, 2010, 11:49 PM
I had to disable Xen bridging and setup bridge manually to be able to work with PV
guests . In other words all xen bridged networking has to be commented out on F13
and at the same time PV guest cannot obtain IP via virbr0
It doesn't happen on F12.
--- On Mon, 5/17/10, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote:
From: Boris Derzhavets
<bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x
questions
To: xen(a)lists.fedoraproject.org, "fcxen user" <fcxen(a)itsbeen.sent.com>
Date: Monday, May 17, 2010, 1:44 PM
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(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen
4.0.x questions
To: xen(a)lists.fedoraproject.org, "fcxen user" <fcxen(a)itsbeen.sent.com>
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(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
-----Inline Attachment Follows-----
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
-----Inline Attachment Follows-----
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
-----Inline Attachment Follows-----
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
11:04 a.m.
New subject: Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions
On Wed, May 19, 2010 at 06:00:10AM -0700, Boris Derzhavets wrote:
With 2.6.32.13 RH's PV guests (F13,RHL6 Beta tested) do detect
NAT
interface
and can smoothly installed via virt-manager ( virt-install).
However, Ubuntu Lucid Official xenified installer is still failing with
NAT and requires
old style network bridging, OSOL 134 behaves same way.
Ubuntu 10.04 PV guest works just fine for me with NAT.
-- Pasi
Boris.
--- On Tue, 5/18/10, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with
Xen 4.0.x questions
To: xen(a)lists.fedoraproject.org, "fcxen user"
<fcxen(a)itsbeen.sent.com>
Date: Tuesday, May 18, 2010, 2:11 AM
So, installed Xen 4.0 via MY's src.rpm on top F13 i had
to set up manually "br0" for PV Guests, HVM seems to be OK with NAT ( or
br0 no matter)
# chkconfig NetworkManager off
# chkconfig network on
Reboot
VNC console doesn't get launched for virt-installs of PV guests ,
referencing "br0".
Virt-install should run in "nographics" mode with VNC setup at DomU for
Fedoras,CentOS guests.
I might did something wrong, but at the moment "Xen 4.0 /
Virt-manager&Virt-install" regression vs F12 is taken place.
Boris.
--- On Mon, 5/17/10, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s
with Xen 4.0.x questions
To: xen(a)lists.fedoraproject.org, "fcxen user"
<fcxen(a)itsbeen.sent.com>
Date: Monday, May 17, 2010, 11:49 PM
I had to disable Xen bridging and setup bridge manually to be able to
work with PV
guests . In other words all xen bridged networking has to be commented
out on F13
and at the same time PV guest cannot obtain IP via virbr0
It doesn't happen on F12.
--- On Mon, 5/17/10, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s
with Xen 4.0.x questions
To: xen(a)lists.fedoraproject.org, "fcxen user"
<fcxen(a)itsbeen.sent.com>
Date: Monday, May 17, 2010, 1:44 PM
> 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(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13
dom0s with Xen 4.0.x questions
To: xen(a)lists.fedoraproject.org, "fcxen user"
<fcxen(a)itsbeen.sent.com>
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(a)lists.fedoraproject.org
[1]https://admin.fedoraproject.org/mailman/listinfo/xen
-----Inline Attachment Follows-----
--
xen mailing list
xen(a)lists.fedoraproject.org
[2]https://admin.fedoraproject.org/mailman/listinfo/xen
-----Inline Attachment Follows-----
--
xen mailing list
xen(a)lists.fedoraproject.org
[3]https://admin.fedoraproject.org/mailman/listinfo/xen
-----Inline Attachment Follows-----
--
xen mailing list
[4]xen(a)lists.fedoraproject.org
[5]https://admin.fedoraproject.org/mailman/listinfo/xen
References
Visible links
1. https://admin.fedoraproject.org/mailman/listinfo/xen
2. https://admin.fedoraproject.org/mailman/listinfo/xen
3. https://admin.fedoraproject.org/mailman/listinfo/xen
4. file:///mc/compose?to=xen@lists.fedoraproject.org
5. https://admin.fedoraproject.org/mailman/listinfo/xen
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
5085
days inactive
5092
days old
6 comments
3 participants
participants (3)
-
Boris Derzhavets -
fcxen user -
Pasi Kärkkäinen