@Brian,
given that there is a workaround, I'm hesitant to do it. There have
been reported bugs with ballooning in heavy overcommit situations, so
even if ballooning is working fine for some users I'd rather not cause
other users to switch from not using it to using it.
--
You received this bug
Any word on a decision to backport this fix to Lucid? I agree it is not
a terrible bug and more of a lack of a feature, but Lucid will be in use
for some time to come.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Potentially better than copying the /usr/bin/kvm binary to
/usr/bin/kvm.real is to use dpkg-dirvert, then the shell script it's
replaced with (as per Michael R. Hines' suggestion) won't be over-
written on upgrade of the qemu-kvm package:
$ sudo dpkg-divert --add --rename --divert /usr/bin/kvm.rea
This does not seem fixed in 10.04.1. The fix would apparently belong in
Libvirt but the changelogs for the Libvirt package in 10.04.1 don't
indicate anything and no KVM guest processes on my hosts running 10.04.1
show the "-balloon virtio" flag. I had to use a wrapper script around
qemu-system-x86_
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Fix Released
--
kvm memory ballooning is unusable in Lucid
https://bugs.launchpad.net/bugs/579723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Nevermind seems to working. Sorry for jumping the gun.
--
kvm memory ballooning is unusable in Lucid
https://bugs.launchpad.net/bugs/579723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
I see that there is a fix release out there, but it's not clear how has
it been fixed. Is it on libvirt? kvm? Is it available currently on
Lucid? Maverick?
--
kvm memory ballooning is unusable in Lucid
https://bugs.launchpad.net/bugs/579723
You received this bug notification because you are a mem
** Changed in: libvirt (Ubuntu)
Status: Fix Released => Confirmed
--
kvm memory ballooning is unusable in Lucid
https://bugs.launchpad.net/bugs/579723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Ooops, that should be: exec /usr/bin/kvm.real -balloon virtio "$@"
--
kvm memory ballooning is unusable in Lucid
https://bugs.launchpad.net/bugs/579723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
This is a far less intrusive workaround:
bash$ cd /usr/bin
bash$ mv kvm kvm.real
bash$ cat kvm
#!/bin/bash
exec /usr/bin/kvm.bak -balloon virtio "$@"
... doesn't require modifying libvirt or anybody else.
--
kvm memory ballooning is unusable in Lucid
https://bugs.launchpad.net/bugs/579723
Y
libvirt in maverick should have this fix (and does on my install). Are you
able to confirm?
** Changed in: libvirt (Ubuntu)
Status: New => Fix Released
--
kvm memory ballooning is unusable in Lucid
https://bugs.launchpad.net/bugs/579723
You received this bug notification because you are
I also hit this bug after upgrading to lucid, and found an explanation
of the root of the problem here: http://www.mail-archive.com/libvirt-
us...@redhat.com/msg00328.html.
The upstream fix is
http://libvirt.org/git/?p=libvirt.git;a=commit;h=7a90f21655aedc35cf711264498ebb4a1b783c8a.
It applies cle
I'm afraid I'm still having some issues. I'm most likely just missing
some subtle thing entirely...
I edited the apparmor profile, and the vm starts just fine. I update the
memory with both setmaxmem and setmem, however, a virsh dominfo qa-matt
still yields:
r...@qa:~# virsh dominfo qa-matt
Id:
This sounds like you need to adjust the libvirtd apparmor profile.
Edit
/etc/apparmor.d/abstractions/libvirt-qemu
and add the following line:
/usr/bin/kvm-balloon rmix,
--
kvm memory ballooning is unusable in Lucid
https://bugs.launchpad.net/bugs/579723
You received this bug notification
I have, sorry I didn't post that. Yes, I can execute it from my
path(Can't give the exact output since I'm away from that machine at the
moment though).
--
kvm memory ballooning is unusable in Lucid
https://bugs.launchpad.net/bugs/579723
You received this bug notification because you are a member
Have you checked the file's execution bit?
chmod 0755 kvm-balloon
** Description changed:
kvm/qemu doesn't enable ballooning by default anymore (the man page still
claims that ballooning is enabled by default) .
There is no easy way to enable it with libvirt.
libvirt should add "-balloo
I also find this is a problem, but your fix doesn't work.
# cat /usr/bin/kvm-balloon
#!/bin/bash
/usr/bin/kvm -balloon virtio "$@"
# virsh start qa-matt
error: Failed to start domain qa-matt
error: monitor socket did not show up.: No such file or directory
The VM's XML(or, part of it anyway)
try adding quotes around $@ in kvm-balloon script:
#!/bin/sh
/usr/bin/kvm -balloon virtio "$@"
--
kvm memory ballooning is unusable in Lucid
https://bugs.launchpad.net/bugs/579723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
Thanks,
I still have an error message if I change the kvm to kvm-balloon in
/etc/libvirt/qemu/Duffman.xml :
r...@homer:~# virsh start Duffman
error: Failed to start domain Duffman
error: internal error cannot parse QEMU version number in ''"
However both are executables, and both displays the ve
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Low
--
kvm memory ballooning is unusable in Lucid
https://bugs.launchpad.net/bugs/579723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
20 matches
Mail list logo
