Daniel P. Berrange wrote:
On Tue, Jan 06, 2009 at 11:57:34AM -0000, Gerhardus.Geldenhuis@xxxxxxxxxxxxxx wrote:
No it does not use xend.
# ps auxwww | grep xen
root 21 0.0 0.0 0 0 ? S< 2008 0:00 [xenwatch]
root 22 0.0 0.0 0 0 ? S< 2008 0:00 [xenbus]
root 5240 0.0 0.1 2076 908 ? S 2008 0:00
/usr/sbin/xenstored
root 5243 0.0 0.0 12232 532 ? Sl 2008 0:00
/usr/sbin/xenconsoled
root 5254 0.0 0.0 2608 444 ? S 2008 0:00
/opt/xensource/libexec/cdrommon /dev/xapi/cd/hda
root 5269 0.0 0.4 19156 3800 ? S< 2008 0:00
/opt/xensource/bin/xapi -daemon -writereadyfile
/var/run/xapi_startup.cookie -writeinitcomplete
/var/run/xapi_init_complete.cookie -onsystemboot
root 5271 0.0 1.3 178612 10056 ? S<l 2008 1:00
/opt/xensource/bin/xapi -daemon -writereadyfile
/var/run/xapi_startup.cookie -writeinitcomplete
/var/run/xapi_init_complete.cookie -onsystemboot
root 5561 0.0 0.4 21580 3720 ? Sl 2008 0:00 python
/opt/xensource/sm/snapwatchd/snapwatchd -d /var/log/SMlog
root 6181 0.0 0.7 12380 5592 ? Ss 2008 1:19 python
/opt/xensource/bin/perfmon --daemon
root 6405 0.0 0.1 4756 1524 ? Ss 2008 0:00
/usr/lib/xen/bin/vncterm -v 127.0.0.1 -r -x /local/domain/0/serial/0 -c
/usr/lib/xen/bin/dom0term.sh
root 10301 0.0 0.1 2424 1024 pts/0 Ss+ Jan05 0:00
/bin/bash /usr/lib/xen/bin/dom0term.sh
That's pretty much game over then. Someone will have to write a new
libvirt driver specifically for XenEnterprise to get it to work.
damn - that really scuppers me trying to forge ahead with the cobbler
route as XenEnterprise will be around here for a while much to my annoyance.
Is that really it ?
--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list