Update QEMU from 2.6.1 to 2.6.2 #248
Conversation
News: > September 29th, 2016 > > • QEMU version 2.6.2 is out! See the Download page for more > information. Announcement [1]: > This is a fairly small update to 2.6.1 that addresses: > > - a security issue when using virtfs/virtio-9p which can lead to a guest > gaining unintended access to the host filesystem, > - a regression introduced into 2.6.1 which can result in live migration > failing when virtio devices have pending entries in their virtqueues, > - and various issues related to VNC and emulated network/storage > devices, among other things. > > Users of QEMU 2.6.1 should upgrade accordingly. [1] https://lists.gnu.org/archive/html/qemu-devel/2016-09/msg07971.html
|
Paul, wo du den qemu gerade aktualisierst, koenntest du ihn gleich mit jemalloc bauen? Oder hat der configure das jemalloc von alleine gefunden? |
|
Es sieht so aus, dass QEMU ohne jemalloc-Unterstützung gebaut wurde. Ich kann den Schalter übergeben, testen kann ich das aber nicht. |
Pass `--enable-jemalloc` as requested by Thomas.
pmenzel
force-pushed
the
update-qemu-from-2.6.1-to-2.6.2
branch
from
6c66147
to
00b5fe3
Compare
|
Mit |
|
The problem is, we can't easily test the important things (the VMs on macheteinfach, including github) without their interruption. But neither do I like the idea of just upgrading qemu and hoping, that everything will be okay, when a VM restarts the next time. If we detect a problem days or weeks later, the image might be corrupted and new data is not included in the last good copy. Don't know, how to handle this. |
|
encapsulate qemu into /project/vm . If you want stability, thre is no other way. |
|
Encapsulation has the same "how to test" problem, unless we freeze the project forever. |
|
updated on distmaster |
Tested on keineahnung.