That is in release by now.
** Changed in: xen (Ubuntu)
Status: Triaged = Fix Released
--
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
+1 from me, it has features that users want, more specifacally arm
support.
--
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
Ack. Approved.
** Changed in: xen (Ubuntu)
Status: New = Triaged
--
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
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
** Patch added: Xen-README.diff
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1218817/+attachment/3795024/+files/Xen-README.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
I uploaded and build the new Xen package in my PPA (ppa:smb/xen):
https://launchpad.net/~smb/+archive/xen/+build/4880118/+files/buildlog_ubuntu-saucy-amd64.xen_4.3.0-0ubuntu3_UPLOADING.txt.gz
Several bugfixes were required in virt-install, libvirt and qemu and
already have been uploaded to Saucy and submitted upstream when
appropriate.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
