[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/916085
I'm testing this in quantal, and not quite seeing what you mean. When I
switch the 'current' memory (using virt-manager) from 512m to 1024m,
/proc/meminfo in the guest shows the updated values; likewise when I
lower it back to 512m, after a few seconds the guest shows the new
values. Of course,
** Changed in: libvirt (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/916085
Title:
kvm-qemu, libvirt-bin: kernel panic if using memory balloon
To manage no
Thanks. I see now. The 'second test' pinpoints ballooning as the
source of the bug. Got it.
I'll try to reproduce this when I get a chance. In the meantime, if
it's at all possible for you to try and reproduce this with the current
upstream git tree, that be helpful.
Since this only affects t
Yes.
This way most memory used by guests can be swapped (inefficient, but works) out
if necessary because others need RAM to run.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/916085
Title:
kvm-qem
Thanks for taking the time to report this bug.
By 'make sure there is enough swap defined', do you mean that host
memory + host swap is greater than than the sum of memory used by all
guests?
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/916085
Title:
kvm-qemu, libvirt-bin: kernel panic if using memory balloon
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt