Hi all. I'm having issues while creating snapshots. I posted on Stack Exchange [1], but figured I might get more success here. My VM backup script fails while creating the snapshot. virsh snapshot-create-as --domain machine_1 snap --diskspec vda,file=/srv/test/test-snap.qcow2 --disk-only --atomic --no-metadata --quiesce error: Requested operation is not valid: domain is already quiesced Even after a VM reboot, the system is still quiesced and I get the same error. I thought quiesce means FS freeze, but this makes no sense since I can still write to the FS when logged in the faulty VMs. And this would not survive a reboot, right? Could it be a communication issue that makes the host think the GA says the machine is quiesced while it is not? In any case, is there a command to enquire the quiesce state (apart from attempting a snapshot and see if I get an error)? Assuming the faulty VMs went quiesced after a unreproducible error, I could fix that by exiting quiesced state, whatever that means. Is there a virsh command to unquiesce the VM? The whole backup procedure used to work and now it fails on 2 VMs but still works on 2 others and I can't think of any relevant difference between them. Software versions: - Host is Debian Jessie with qemu-kvm 2.8+dfsg-3~bop8+1 from backports. - Guests are Debian Stretch with qemu-guest-agent 2.8+dfsg-6+deb9u4. (For the record, the backup script is on GitHub [2]. Basically, what it does is 1/ create snapshot, 2/ copy, 3/ commit snapshot.) If I remove the `quiesce` option from the snapshot command line, things work smooth. But obviously, this is not ideal. Thanks for any hint. [1] https://serverfault.com/questions/917247/virsh-error-domain-is-already-quiesced [2] https://github.com/Nobatek/vmbackup/blob/master/vmbackup -- Jérôme
Michal Prívozník
2018-Jun-25 13:34 UTC
Re: [libvirt-users] virsh error: domain is already quiesced
On 06/21/2018 11:27 AM, Jérôme wrote:> Hi all. > > I'm having issues while creating snapshots. > > I posted on Stack Exchange [1], but figured I might get more success here. > > My VM backup script fails while creating the snapshot. > > virsh snapshot-create-as --domain machine_1 snap --diskspec > vda,file=/srv/test/test-snap.qcow2 --disk-only --atomic --no-metadata > --quiesce > error: Requested operation is not valid: domain is already quiescedThis is the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1160084 Should be fixed in 1.2.11 by 6085d917d5c5839b7ed351e99fadbbb56f5178fe. Upgrade and the bug should go away. Michal
Le 2018-06-25 15:34, Michal Prívozník a écrit :> Should be fixed in 1.2.11 by 6085d917d5c5839b7ed351e99fadbbb56f5178fe. > Upgrade and the bug should go away.Thanks. I did see this bug report but didn't understand the description and didn't think it applied to my use case. Besides, I noticed it was a bit old (2014) but didn't realize I was using a version _that_ old. I upgraded to a more recent version (3.0.0) and from a quick test it works correctly. Sorry for bothering you with that old issue. Have a nice day. -- Jérôme
Reasonably Related Threads
- virsh error: domain is already quiesced
- Re: virsh can't support VM offline blockcommit
- Re: Backup a VM (using live external snapshot and blockcommit)
- Backup a VM (using live external snapshot and blockcommit)
- virsh snapshot-create-as: change umask on snapshots