On Wed, Aug 19, 2009 at 02:54:36AM -0700, Boris Derzhavets wrote:
> I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
> Rebooted into Xen Host with 126.96.36.199 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 \
> [root@ServerXen341F Download]# rpm -qa|grep virt
> Then i was able to connect to xend via virt-manager and attempted to start
> OSOL HVM. Got an error at startup:-
> Unable to complete install '<class 'libvirt.libvirtError'> Domain not found:
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/create.py", line 1489, in
> dom = guest.start_install(False, meter = meter)
> File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in
> return self._do_install(consolecb, meter, removeOld, wait)
> File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in
> self.domain = self.conn.createLinux(install_xml, 0)
> File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in
> if ret is None:raise libvirtError('virDomainCreateLinux() failed',
> 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
> 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:
- install it: "rpm -i libvirt-0.6.2-14.fc11.src.rpm"
- Copy & paste the patch to a file
- 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/
> --- 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:
> 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:
> 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 mailing list