htpcguru Posted April 10, 2018 Share Posted April 10, 2018 (edited) I am able to create a snapshot of a running VM. root@OttSwServer1:/mnt/user/domains/Ubuntu-OttSwVM01# virsh snapshot-create-as --domain "Ubuntu-OttSwVM01" --quiesce --name backup --atomic --disk-only Domain snapshot backup created root@OttSwServer1:/mnt/user/domains/Ubuntu-OttSwVM01# ls vdisk1.backup vdisk1.qcow2 root@OttSwServer1:/mnt/user/domains/Ubuntu-OttSwVM01# virsh snapshot-list Ubuntu-OttSwVM01 Name Creation Time State ------------------------------------------------------------ backup 2018-04-10 08:18:15 -0700 disk-snapshot However, when I tried to do blockcommit of the snapshot, it complains about the vdisk location. root@OttSwServer1:/mnt/user/domains/Ubuntu-OttSwVM01# virsh blockcommit Ubuntu-OttSwVM01 /mnt/user/domains/Ubuntu-OttSwVM01/vdisk1.backup --active --verbose --pivot error: internal error: qemu block name '/mnt/disk1/domains/Ubuntu-OttSwVM01/vdisk1.qcow2' doesn't match expected '/mnt/user/domains/Ubuntu-OttSwVM01/vdisk1.qcow2' Looks like blockcommit command looks for the vdisk from actual disk location rather than user share mount. (vdisk1.qcow2 file physical location is on /mnt/disk1) The snapshot xml does have the correct base image path on the user share "/mnt/user" root@OttSwServer1:/mnt/user/domains/Ubuntu-OttSwVM01# virsh snapshot-dumpxml Ubuntu-OttSwVM01 backup | grep disk1 <source file='/mnt/user/domains/Ubuntu-OttSwVM01/vdisk1.backup'/> <source file='/mnt/user/domains/Ubuntu-OttSwVM01/vdisk1.qcow2'/> vdisk files references also look good: root@OttSwServer1:/mnt/user/domains/Ubuntu-OttSwVM01# virsh domblklist Ubuntu-OttSwVM01 Target Source ------------------------------------------------ hdc /mnt/user/domains/Ubuntu-OttSwVM01/vdisk1.backup hda /mnt/user/isos/ubuntu-16.04.3-desktop-amd64.iso Thoughts? Edited April 10, 2018 by htpcguru Quote Link to comment
htpcguru Posted April 10, 2018 Author Share Posted April 10, 2018 If I specify the vdisk.qcow2 location on KVM/Qemu in /mnt/disk1/... rather than /mnt/user/..., the operations work as expected root@OttSwServer1:~# virsh domblklist Ubuntu-OttSwVM01 Target Source ------------------------------------------------ hdc /mnt/disk1/domains/Ubuntu-OttSwVM01/vdisk1.qcow2 hda /mnt/user/isos/ubuntu-16.04.3-desktop-amd64.iso root@OttSwServer1:~# virsh snapshot-list Ubuntu-OttSwVM01 Name Creation Time State ------------------------------------------------------------ root@OttSwServer1:~# virsh snapshot-create-as --domain "Ubuntu-OttSwVM01" --quiesce --name backup --atomic --disk-onlyDomain snapshot backup created root@OttSwServer1:~# virsh domblklist Ubuntu-OttSwVM01 Target Source ------------------------------------------------ hdc /mnt/disk1/domains/Ubuntu-OttSwVM01/vdisk1.backup hda /mnt/user/isos/ubuntu-16.04.3-desktop-amd64.iso root@OttSwServer1:~# virsh snapshot-list Ubuntu-OttSwVM01 Name Creation Time State ------------------------------------------------------------ backup 2018-04-10 08:46:49 -0700 disk-snapshot root@OttSwServer1:~# virsh blockcommit Ubuntu-OttSwVM01 /mnt/disk1/domains/Ubuntu-OttSwVM01/vdisk1.backup --active --verbose --pivot Block commit: [100 %] Successfully pivoted root@OttSwServer1:~# virsh domblklist Ubuntu-OttSwVM01Target Source ------------------------------------------------ hdc /mnt/disk1/domains/Ubuntu-OttSwVM01/vdisk1.qcow2 hda /mnt/user/isos/ubuntu-16.04.3-desktop-amd64.iso root@OttSwServer1:~# virsh snapshot-list Ubuntu-OttSwVM01 Name Creation Time State ------------------------------------------------------------ backup 2018-04-10 08:46:49 -0700 disk-snapshot root@OttSwServer1:~# Looks like a bug in blockcommit? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.