On Mon, Mar 09, 2009 at 02:24:04PM +0200, Pasi Kärkkäinen wrote:
On Mon, Mar 09, 2009 at 10:39:29AM +0000, Daniel P. Berrange wrote:
> On Sun, Mar 08, 2009 at 09:23:10PM +0200, Pasi K?rkk?inen wrote:
> > On Sat, Mar 07, 2009 at 09:37:25PM +0200, Pasi Kärkkäinen wrote:
> > > On Sat, Mar 07, 2009 at 02:28:52PM -0500, Cole Robinson wrote:
> > > > >> [root@dom0test ~]# cat
/sys/hypervisor/properties/capabilities
> > > > >> cat: /sys/hypervisor/properties/capabilities: No such file
or directory
> > > > >>
> > > > >
> > > > > [root@dom0test ~]# ls -la /sys/hypervisor
> > > > > ls: cannot access /sys/hypervisor: No such file or directory
> > > > >
> > > > >
> > > >
> > > > Hmm, well that will do it. Libvirt capabilities are what tell user
apps
> > > > what types of domains can be installed, and generating xen
capabilities
> > > > is largely dependent on the above paths. Not too sure what to do from
here.
> > > >
> > >
> > > Ok.
> > >
> > > I'll try asking what's the thing with that.. if it's still
missing, or is it
> > > deprecated or something..
> > >
> >
> > Ok, it seems that /sys/hypervisor feature is not yet implemented in pv_ops
> > dom0 kernel.
> >
> > There's a patch somewhere in Redhat's old dom0 repository.. Jeremy is
trying
> > to find that.
>
>
> If this patch gets rejected for whatever reason, let me know, becasue we
> can possibly switch libvirt over to making a direct hypercall to fetch
> this information.
>
Yep. I will.
The patch seems to be here:
http://git.et.redhat.com/?p=linux-2.6-dom0-pvops.git;a=commit;h=7aa79a560...
And now this feature is committed to pv_ops kernel git tree:
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=834bf...
ATM this fix is needed to compile the kernel with /sys/hypervisor support patch:
http://lists.xensource.com/archives/html/xen-devel/2009-03/msg00699.html
I compiled a custom kernel with the patch included, and now:
[root@dom0test ~]# cat /sys/hypervisor/properties/capabilities
xen-3.0-x86_32p
But Fedora 10 domU installation still fails:
[root@dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l
"ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
Starting install...
Retrieving file .treeinfo... | 1.1 kB
00:00
Retrieving file vmlinuz-PAE... | 2.5 MB
00:01
Retrieving file initrd-PAE.img... | 16 MB
00:10
XML description for failed to build sexpr is not well formed or invalid
Domain installation may not have been
successful. If it was, you can restart your domain
by running 'virsh start vm01'; otherwise, please
restart your installation.
ERROR XML description for failed to build sexpr is not well formed or invalid
Traceback (most recent call last):
File "/usr/sbin/virt-install", line 692, in <module>
main()
File "/usr/sbin/virt-install", line 632, in main
dom = guest.start_install(conscb, progresscb, wait=(not wait))
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 732, in
start_install
return self._do_install(consolecb, meter, removeOld, wait)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 767, in
_do_install
self.domain = self.conn.createLinux(install_xml, 0)
File "/usr/lib/python2.5/site-packages/libvirt.py", line 915, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: XML description for failed to build sexpr is not well formed or invalid
-- Pasi