Since I have not heard anything back from Citrix, I did an attempt of checking myself and found that even without any update to Xen the xen- api/xcp state is ... highly improvable. The command-line examples in the README.Debian of xcp-xapi more or less work (with the caveat that you have to leave network config to xcp and that fails to send the hostname with dhcp which then makes networking in a pain in the bum, but that is probably another story). A more grave problem is that the xen command (which is a wrapper that is supposed to automatically use the right xm/xl toolstack) in not handling xapi as a toolstack and seems to cause the xapi daemon to loose its mind (until restarting). And unfortunately the xendomains startup script uses "xen list". Again that is broken right now without any updates. Openxenmanager is supposed to be a graphical frontend to control a host running the xapi stack but right now shows more python exceptions than anything else. Also without any changes to current Xen.
That said with replacing xen to 4.3 and using the updated xen-api from my PPA I managed to get a PVM guest up. That still seems to use blktap devices, so not having support compiled into libxenlight does not seem to matter. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1218817 Title: [FFE] Update to Xen-4.3 in Saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1218817/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
