Good question. Over time I've got some feedback that the whole config
file mechanism is really just a second class citizen anyway. I'm happy
for now (running 2.7) and don't really care too much.
Nevertheless: I'd be absolutely excited if I could reliably configure
(and have nice documentation that
This has been merged in upstream Qemu a while ago.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1587065
Title:
btrfs qemu-ga - multiple mounts block fsfreeze
Status in QEMU:
New
Bug descriptio
f we try to freeze an
>> already frozen filesystem. This can happen if a filesystem
>> is mounted more than once (e.g. with a bind mount).
>>
>> Suggested-by: Christian Theune
>> Cc: qemu-sta...@nongnu.org
>> Signed-off-by: Peter Lieven
>
> What happens when y
r idea would
>
> be to track all devices which have been successfully frozen and skip
> consecutive
>
> tries to freeze them.
Which will be subject to race conditions as other processes may call
freeze/thaw on any device. Those are completely out of our control.
Christian
--
C
I'm the responder from the Qemu list. I reviewed that C code a while ago
when I stumbled over it. If someone helps me through the Qemu patch
acceptance process then I'm willing to provide a patch.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribe
duplicate
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1358287
Title:
-readconfig file doesn't interpret memory size correctly
Status in QEMU:
New
Bug description:
I'm running Qemu 2.1 and h
*** This bug is a duplicate of bug 1358287 ***
https://bugs.launchpad.net/bugs/1358287
Public bug reported:
I'm running Qemu 2.1 and have issues with the config file format.
Specifically Qemu wrote the following snippet with '-writeconfig':
[memory]
size = "1024"
However, upon starting a
Public bug reported:
I'm running Qemu 2.1 and have issues with the config file format.
Specifically Qemu wrote the following snippet with '-writeconfig':
[memory]
size = "1024"
However, upon starting a VM with this setting it only receives 128MiB
(the default size).
I'm reverting back to usi
Hi,
we're currently still on 0.13, looking forward to a large update soon. :)
We haven't been using live migration up until now, but are
investigating it to multiple downtimes (restarting updated hosts and
restarting updated guests) when doing system updates. So, we're trying
to find out whet
