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@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: 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@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: 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@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: 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@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 > [1]https://admin.fedoraproject.org/mailman/listinfo/xen > > -----Inline Attachment Follows----- > > -- > xen mailing list > xen@xxxxxxxxxxxxxxxxxxxxxxx > [2]https://admin.fedoraproject.org/mailman/listinfo/xen > > -----Inline Attachment Follows----- > > -- > xen mailing list > xen@xxxxxxxxxxxxxxxxxxxxxxx > [3]https://admin.fedoraproject.org/mailman/listinfo/xen > > -----Inline Attachment Follows----- > > -- > xen mailing list > [4]xen@xxxxxxxxxxxxxxxxxxxxxxx > [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@xxxxxxxxxxxxxxxxxxxxxxx > 5. https://admin.fedoraproject.org/mailman/listinfo/xen > -- > xen mailing list > xen@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/xen
