Re: [libvirt-users] Compatibility with Parallels Virtouzo
Well, vpsid is in there for a reason. If this was renamed we need to
figure out how to detect that and make the OpenVZ driver deal with it
at runtime. We definitely cannot just replace vpsid with ctid as this
would break compatibility with older OpenVZ versions. But I'm not
familiar with OpenVZ, so I'm not the one to decide here.
For testing you can just go ahead and replace vpsid with ctid and
recompile to see how far that gets you.
2011/7/12 Andreas Mauf <a.mauf(a)syseleven.de>:
It should be CTID instead of VPSID. I think this was changed in
openvz
version, too: http://wiki.openvz.org/Man/vzlist.8
Can we fix this in /root/libvirt-0.9.3/srcopenvz/openvz_conf.c and
reinstall?
2011/7/12 Matthias Bolte <matthias.bolte(a)googlemail.com>
>
> Well, as Virtuozzo is a variant of OpenVZ it'll probably be possible
> to teach the OpenVZ driver to detect and deal with this similar to the
> QEMU driver dealing with different variants of QEMU.
>
> 2011/7/12 Andreas Mauf <a.mauf(a)syseleven.de>:
> > Thanks! I compiled libvirt on my own and added --with-openvz. Driver is
> > now
> > available.
> > But as feared libvirt is using a api call that virtuozzo dont accept. Is
> > there a way to update those calls?
> >>
> >> [root@localhost local]# LIBVIRT_DEBUG=1 virsh -c openvz:///system
> >> [...]
> >> 00:25:12.878: 2313: debug : do_open:1053 : trying driver 1 (OPENVZ) ...
> >> 00:25:12.879: 2313: debug : virCommandRunAsync:1874 : About to run
> >> /usr/sbin/vzlist -a -ovpsid,status -H
> >> 00:25:12.901: 2313: debug : virCommandRunAsync:1890 : Command result 0,
> >> with PID 2314
> >> 00:25:12.902: 2313: debug : virCommandRun:1711 : Result status 0,
> >> stdout:
> >> '' stderr: '00:25:12.889: 2314: debug : virCommandHook:1808 :
Hook is
> >> done 0
> >> Unknown field: vpsid
> >> '
>
> Is this filed just named differently, or did Virtuozzo completely
> remove this ID?
>
> If it's just named different then this should be simple to fix, but it
> needs someone to figure this out.