Problem committing Windows 10 snapshot
Posted: Mon Mar 26, 2018 8:20 pm
Hi there,
A few weeks ago I created a windows10 vm in my EVE, made changes to the image and then merged the snapshot back into the base windows10 image - all went well, I created a new windows10 node in my lab, started it up and all my changes were now in the new base image.
Problem, now I can no longer successfully merge the snapshot with the base, "qemu-img commit" give me a "Co-routine re-entered recursively Aborted" when trying to commit the snapshot to the rebased image. Here are my exact steps, maybe I've missed something?
1. Copy windows10 image to temp working directory
mkdir /root/win10-work/
cd /root/win10-work
cp /opt/unetlab/addons/qemu/win-10-nosparse/virtioa.qcow2 virtioa-work.qcow2
2. Add windows10 node to lab
3. Make changes to windows10 node and shutdown node
4. Check windows10 snapshot with qemu-info and see that base is correct image in /opt/unetlab/addons/qemu/win-10-nosparse - it is
/opt/qemu/bin/qemu-img info /opt/unetlab/tmp/0/03d0fb94-bb4e-4b0b-845d-51744497e47f/2/virtioa.qcow2
"image: virtioa.qcow2
file format: qcow2
virtual size: 20G (21474836480 bytes)
disk size: 2.7G
cluster_size: 65536
backing file: /opt/unetlab/addons/qemu/win-10-nosparse/virtioa.qcow2
Format specific information:
compat: 1.1
lazy refcounts: false
refcount bits: 16
corrupt: false
5. Rebase the snapshot:
/opt/qemu/bin/qemu-img rebase -b /root/win10-work/virtioa-work.qcow2 /opt/unetlab/tmp/0/03d0fb94-bb4e-4b0b-845d-51744497e47f/2/virtioa.qcow2
6. Verify that /root/win10-work/virtioa-work.qcow2 is the new base for snapshot - using qemu-info on snapahot image - it is
7. Merge snapshot into new base:
/opt/qemu/bin/qemu-img commit /root/win10-work/virtioa-work.qcow2 /opt/unetlab/tmp/0/03d0fb94-bb4e-4b0b-845d-51744497e47f/2/virtioa.qcow2
Get error:
"Co-routine re-entered recursively
Aborted"
This used to work about a month ago, but no t working now. Stange thing is that it works on my other images, just doesn't work on my WIndows images.
Thanks in advance.
A few weeks ago I created a windows10 vm in my EVE, made changes to the image and then merged the snapshot back into the base windows10 image - all went well, I created a new windows10 node in my lab, started it up and all my changes were now in the new base image.
Problem, now I can no longer successfully merge the snapshot with the base, "qemu-img commit" give me a "Co-routine re-entered recursively Aborted" when trying to commit the snapshot to the rebased image. Here are my exact steps, maybe I've missed something?
1. Copy windows10 image to temp working directory
mkdir /root/win10-work/
cd /root/win10-work
cp /opt/unetlab/addons/qemu/win-10-nosparse/virtioa.qcow2 virtioa-work.qcow2
2. Add windows10 node to lab
3. Make changes to windows10 node and shutdown node
4. Check windows10 snapshot with qemu-info and see that base is correct image in /opt/unetlab/addons/qemu/win-10-nosparse - it is
/opt/qemu/bin/qemu-img info /opt/unetlab/tmp/0/03d0fb94-bb4e-4b0b-845d-51744497e47f/2/virtioa.qcow2
"image: virtioa.qcow2
file format: qcow2
virtual size: 20G (21474836480 bytes)
disk size: 2.7G
cluster_size: 65536
backing file: /opt/unetlab/addons/qemu/win-10-nosparse/virtioa.qcow2
Format specific information:
compat: 1.1
lazy refcounts: false
refcount bits: 16
corrupt: false
5. Rebase the snapshot:
/opt/qemu/bin/qemu-img rebase -b /root/win10-work/virtioa-work.qcow2 /opt/unetlab/tmp/0/03d0fb94-bb4e-4b0b-845d-51744497e47f/2/virtioa.qcow2
6. Verify that /root/win10-work/virtioa-work.qcow2 is the new base for snapshot - using qemu-info on snapahot image - it is
7. Merge snapshot into new base:
/opt/qemu/bin/qemu-img commit /root/win10-work/virtioa-work.qcow2 /opt/unetlab/tmp/0/03d0fb94-bb4e-4b0b-845d-51744497e47f/2/virtioa.qcow2
Get error:
"Co-routine re-entered recursively
Aborted"
This used to work about a month ago, but no t working now. Stange thing is that it works on my other images, just doesn't work on my WIndows images.
Thanks in advance.