Re-opened in the new bug tracker here: https://gitlab.com/qemu-
project/qemu/-/issues/520
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #520
https://gitlab.com/qemu-project/qemu/-/issues/520
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1807073
Title:
qemu-guest-
The QEMU project is currently considering to move its bug tracking to another
system. For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the
I have a problem with fsfreeze that looks very similar to this, though
I'm of course not 100% sure it's the same.
When I try to snapshot one server, fsfreeze-freeze hangs, and after
having timeout'ed the qemu agent has crashed:
# qm guest cmd 105 fsfreeze-status
thawed
# qm guest cmd 105 fsfreeze
But it happens in some times， this problem dose not occur 100 percent。I
can not reproduce when I want to find WHY。So it‘s dangerous in my
production environment。
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.n
btw,I run OEL7 VM on the same host and Ubuntu 18.04 VM,
both have newer qemu-guest-agent:
18.04: qemu-guest-age 1:2.11+dfsg-
OEL7: rpm -qi qemu-guest-agent
Name: qemu-guest-agent
Epoch : 10
Version : 2.12.0
Release : 2.el7
Never had this problem on both oh these.
--
You r
Just got almost the same
Ubuntu 16.04 as guest on Centos 7 host,
all will latest updates.
Execute of
virsh qemu-agent-command inetgw2 '{"execute":"guest-fsfreeze-freeze"}'
failed with agent not available ( or something like this), but fsfreeze
executed in OS
Apr 7 02:28:54 inetgw2 qemu-ga: info
