WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems wit

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Wed, 19 Aug 2009 06:05:11 -0700 (PDT)
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 19 Aug 2009 06:05:46 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1250687111; bh=iJ6wuZDk5wFIK3gMZ7plIyF9PTzKtvvox9o0XQy6DIs=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=etbuEijg4WGXxF05X7B2nYHmtLluePx0EshSHsZqZ/tPWMdioEJAeaWocfV2h3VCOHCHc1ryQvn+uTzYMjZW4OCGfZRtUQ3ruzeHnzuw6VuSttn3+BKBEghBbcwi7Kk7rEsTUrgrG6OlU3KRmj8gpiTS6sS4MP1WZgfbl72O+6I=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=R533amO1MAqzYkAcqqp7LLojt7H0RQsVaTSerAJpU/cbR/9C+Qsiuja6fT7MKhABM2E0MTgNlYscyBMWNKLfziM92cMsPiaV7wlZSfp5EJ+Zfacd4h9egAVST7UlpoV0SUeCRDJHFH+RQodH4eDTIegPExlcqqepa1EXEPXYws4=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090819123732.GS19938@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> What do you have in "xm log" ? Is the last line about running pygrub?

Here we go

[2009-08-19 16:28:06 2124] DEBUG (SrvDomain:76) Starting domain VMF11 False
[2009-08-19 16:28:06 2124] DEBUG (XendDomainInfo:2296) XendDomainInfo.constructDomain
[2009-08-19 16:28:06 2124] DEBUG (balloon:166) Balloon: 132448 KiB free; need 4096; done.
[2009-08-19 16:28:06 2124] DEBUG (XendDomain:452) Adding Domain: 1
[2009-08-19 16:28:06 2124] DEBUG (XendDomainInfo:2497) XendDomainInfo.initDomain: 1 256
[2009-08-19 16:28:06 3281] DEBUG (XendBootloader:113) Launching bootloader as [\047/usr/bin/pygrub\047, \047--output=/var/run/xend/boot/xenbl.4360\047, \047/dev/sda12\047].
[2009-08-19 16:28:47 2124] INFO (XendDomain:1180) Domain VMF11 (1) unpaused.
[2009-08-19 16:29:24 2124] DEBUG (XendDomainInfo:2724) XendDomainInfo.destroy: domid=1
[2009-08-19 16:29:24 2124] DEBUG (XendDomainInfo:2204) No device model
[2009-08-19 16:29:24 2124] DEBUG (XendDomainInfo:2206) Releasing devices
[2009-08-19 16:29:24 2124] ERROR (XendBootloader:207) Domain was died while the bootloader was running.
[2009-08-19 16:29:24 2124] ERROR (XendDomainInfo:476) VM start failed
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 456, in start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, in log_progress
    retval = func(*args, **kwds)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2499, in _initDomain
    self._configureBootloader()
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2919, in _configureBootloader
    bootloader_args, kernel, ramdisk, args)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendBootloader.py", line 208, in bootloader
    raise VmError, msg
VmError: Domain was died while the bootloader was running.
[2009-08-19 16:29:24 2124] ERROR (SrvBase:88) Request start failed.
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/xen/web/SrvBase.py", line 85, in perform
    return op_method(op, req)
  File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDomain.py", line 77, in op_start
    return self.xd.domain_start(self.dom.getName(), paused)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 1039, in domain_start
    dominfo.start(is_managed = True)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 456, in start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, in log_progress
    retval = func(*args, **kwds)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2499, in _initDomain
    self._configureBootloader()
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2919, in _configureBootloader
    bootloader_args, kernel, ramdisk, args)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendBootloader.py", line 208, in bootloader
    raise VmError, msg
VmError: Domain was died while the bootloader was running.

Boris.

--- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@xxxxxx> wrote:

From: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Wednesday, August 19, 2009, 8:37 AM

On Wed, Aug 19, 2009 at 05:21:55AM -0700, Boris Derzhavets wrote:
> Pasi,
>
> Thanks  a lot a lot for your support.
>
>   I was able  to reproduce you instructions on F11 (64-bit) instance (C2D E8400,8 GB RAM).
>   I remind pretty clear,  that now i am experiencing the same issue as with xen-3.4.0-2.fc12.src.rpm.
> F11 PVM been created via virt-manager, cannot be , actually, managed either via virt-manager or from command line.
>
> # xm start VMF11
>
> moves it to paused state and resuming shows :-
>
> [root@ServerXen341F boris]# xm list
> Name                                          ID   Mem VCPUs      State   Time(s)
> Domain-0                                    0    6034     2     r-----    574.9
> VMF11                                         3    2048     0     ------      0.0
>

What do you have in "xm log" ? Is the last line about running pygrub?

I'm seeing an issue with F11 domU where the domU grub.conf contains
timeout=0 and that causes pygrub to get stuck and thus prevents the domU
from starting.. changing to timeout=5 fixes the problem.

I'm going to debug pygrub later today.. I believe it's a bug in pygrub.

> Attempt to create HVM crashes immediately.
>

I can't test HVM guests on my testbox, it doesn't have VT support in the CPU.

-- Pasi

> Boris.
>
> P.S. I was unable to find glibc-devel.i386 for 64-bit F11 (vs F10)
> and installed glibc-devel.i586 for rpmbuild.
>
> --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
>
> From: Pasi Kärkkäinen <pasik@xxxxxx>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
> Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
> Date: Wednesday, August 19, 2009, 6:27 AM
>
> On Wed, Aug 19, 2009 at 02:54:36AM -0700, Boris Derzhavets wrote:
> > Pasi,
> >
> > I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
> > Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.
> >
> > Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
> > and installed (pretty recent - 08/10/2009) :-
> >
> > yum install libvirt-0.7.0-3.fc11.x86_64.rpm \      
> > libvirt-client-0.7.0-3.fc11.x86_64.rpm \
> > libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
> > libvirt-python-0.7.0-3.fc11.x86_64.rpm \
> > python-virtinst-0.500.0-1.fc11.noarch.rpm \
> > virt-manager-0.8.0-1.fc11.noarch.rpm \
> > virt-viewer-0.2.0-1.fc11.x86_64.rpm
> >
> > [root@ServerXen341F Download]# rpm -qa|grep virt
> > libvirt-0.7.0-3.fc11.x86_64
> > libvirt-devel-0.7.0-3.fc11.x86_64
> > python-virtinst-0.500.0-1.fc11.noarch
> > virt-manager-0.8.0-1.fc11.noarch
> > virt-viewer-0.2.0-1.fc11.x86_64
> > libvirt-python-0.7.0-3.fc11.x86_64
> > libvirt-client-0.7.0-3.fc11.x86_64
> >
> > Then i was able to connect to xend via virt-manager and attempted to start building
> > OSOL HVM. Got an error at startup:-
> >
> > Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> > Traceback (most recent call last):
> >   File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
> >     dom = guest.start_install(False, meter = meter)
> >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
> >     return self._do_install(consolecb, meter, removeOld, wait)
> >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in _do_install
> >     self.domain = self.conn.createLinux(install_xml, 0)
> >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
> >     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> > libvirtError: Domain not found: xenUnifiedDomainLookupByName
> >
> > Please advise , how to escalate it to Fedora's people ?
> >
>
> I think you should post to fedora-xen@xxxxxxxxxx and possibly
> CC fedora-virt@xxxxxxxxxx.
>
> > Boris.
> > P.S. Usually i installed libvirt stuff :-
> >
> > # yum install libvirt libvirt-python python-virtinst \
> >
> > virt-manager virt-viewer
> >
> > To apply patch manually i need a kind of libvirt.src.rpm.
> > I don't track Fedora so close to be aware of this.
> > '
>
>
> I was using the default libvirt from F11, but I manually added the bugfix patch:
>
> - Download libvirt src.rpm:
>   ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/11/SRPMS/libvirt-0.6.2-14.fc11.src.rpm
>
> - install it: "rpm -i libvirt-0.6.2-14.fc11.src.rpm"
>
> - Copy & paste the patch to a file /root/rpmbuild/SOURCES/libvirt-bugfix-custom.patch from
>   http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=55ffd3f9a5004e681c8ffb2279d27965eb42e956;hp=b211bb6293355bf68e33f56f947021bd7bb8e675;hb=14435163a086c0bcdff04308077fa46a5fa08bb0;hpb=fd90b67afe59265327dde7e447ea847687bd4e8d
>
> - Edit /root/rpmbuild/SPECS/libvirt.spec and add the patch like other
>   patches are added. You need to add one line to two different places.
>
> - Run "rpmbuild -bb libvirt.spec"
>
> - Install the bugfixed rpms from /root/rpmbuild/RPMS/i586/
>
> -- Pasi
>
>
> >
> > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> >
> > From: Pasi Kärkkäinen <pasik@xxxxxx>
> > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
> > Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
> > Date: Wednesday, August 19, 2009, 3:09 AM
> >
> > On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> > > >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when
> > > > using Xen 3.4, but after I got that patched it was all fine
> > >
> > > If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> > > I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> > >
> >
> > I grabbed Xen 3.4.1-1 src.rpm from:
> > http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/
> >
> > and rebuilt that for F11.
> >
> > The next problem was that libvirt package in Fedora 11 has a bug, which causes it
> > to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.
> >
> > Patch for the libvirt bug is here:
> > http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0
> >
> > Upcoming libvirt update for F11 will fix this. After manually applying that
> > patch and rebuilding libvirt I'm now able to successfully install new guests
> > using virt-install and connect to their console by virt-viewer.
> >
> > -- Pasi
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> >
> >
> >
> >       
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>
>
>       

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>