blob: cf62a7efe91b97fc4ffc424f6cd185297ddf7a3e (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
device: 0.965
network: 0.907
performance: 0.891
files: 0.866
KVM: 0.861
other: 0.859
vnc: 0.858
PID: 0.852
socket: 0.816
permissions: 0.771
semantic: 0.757
graphic: 0.748
debug: 0.605
boot: 0.577
qga return "frozen" when vm just been created from snapfile
Steps to reproduce:
1. virsh create lisa.xml
Domain lisa created from lisa.xml
2. virsh domblklist lisa
vda /mnt/a/b/srv.qcow2
3. virsh snapshot-create-as lisa --disk-only --diskspec vda,file=/tmp/f1,snapfile=/tmp/sp1 --no-metadata --quiesce
Domain snapshot 20220919165217 created
4. virsh shutdown lisa
Domain lisa is being shutdown
5. modify lisa.xml: replace /mnt/a/b/srv/qcow2 with /tmp/sp1
6. virsh create lisa.xml
Domain lisa created from lisa.xml
7. virsh domblklist lisa
vda /tmp/sp1
8. virsh qemu-agent-command lisa '{"execute":"guest-fsfreeze-status"}'
{"return":"frozen"}
9. virsh snapshot-create-as lisa --disk-only --diskspec vda,file=/tmp/f2,snapfile=/tmp/sp2 --no-metadata --quiesce
error: internal error: unable to execute QEMU agent command 'guest-fsfreeze-freeze': The command guest-fsfreeze-freeze has been disabled for this instance
Additional information:
Is "frozen" a normal value in step8? If not, what's the best way to avoid this?
|