This bug was fixed in the package libvirt - 0.9.8-2ubuntu16
---
libvirt (0.9.8-2ubuntu16) precise; urgency=low
[ Serge Hallyn ]
* Apply patches from Josh Durgin to make
attaching rbd volumes and taking snapshots of them work.
- ubuntu/9022-qemu-unescape-HMP-commands-befor
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973529
Title:
libvirt: xen: Use of vfb in HVM definitions causes xenbus errors
To manage notifications about this bug go to:
https
Ok, it seems I just was too confusing when I tried to explain the
problem.
"So the argument is that ATM libvirt uses a vfb config line with HVM
guests and that is wrong. I agree with you there, the vfb config line is
for PV guests only and should be removed from any HVM guests
configurations."
I
Hm hold back, just saw a reply to my question and it sounds like from
the Xen side the preferred way may be to change the kernel in a way that
avoids the delays.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
To be more clear: yes...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973529
Title:
libvirt: xen: Use of vfb in HVM definitions causes xenbus errors
To manage notifications about this bug go to:
h
On on hand some upstream feedback would be nice, even for the Ubuntu package.
On the other side this only affects creation and modification of HVM instances
via libvirt. Which I was able to verify and it is working. So missing feedback
should not prevent us from using / applying it. The main wor
Hi Stefan,
to be clear, would you like this to be rolled into our package while you
try to get it upstream? Or should that also await feedback?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973529
T
The following changes will prevent the vkbd device from being created
(or it will be removed when updating the instance configuration). Right
now, waiting on some upstream feedback. Depending on that outcome, I
would proceed and try to submit this upstream.
** Patch added: "no-vfb-for-hvm.debdiff"
