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
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
socket: 0.974
graphic: 0.973
instruction: 0.973
assembly: 0.969
semantic: 0.968
vnc: 0.962
network: 0.960
boot: 0.947
device: 0.945
KVM: 0.936
other: 0.926
mistranslation: 0.923
qemu-1.5.0 savevm error -95 while writing vm with ceph-rbd as storage-backend
With a running VM I encounter this strange behaviour, former qemu-versions don't show up such an error.
Perhaps this comes from the rbd-backend in qemu-1.5.0 in combination with ceph-0.56.6?
( -95 might be a general "Operation not supported" error? )
Up to 1.4.2 everything is OK with savevm, though.
Any help welcome,
Oliver.
Sorry for not providing enough informations, here we go:
typical longish start for qemu is:
/usr/local/bin/qemu-system-x86_64 -usbdevice tablet -enable-kvm -daemonize -pidfile /var/run/qemu-server/760.pid -monitor unix:/var/run/qemu-server/760.mon,server,nowait -vnc unix:/var/run/qemu-server/760.vnc,password -qmp unix:/var/run/qemu-server/760.qmp,server,nowait -nodefaults -serial none -parallel none -device rtl8139,mac=00:F1:70:00:2F:80,netdev=vlan0d0 -netdev type=tap,id=vlan0d0,ifname=tap760i0d0,script=/etc/fcms/add_if.sh,downscript=/etc/fcms/downscript.sh -name 1155823384-4 -m 512 -vga cirrus -k de -smp sockets=1,cores=1 -device virtio-blk-pci,drive=virtio0 -drive format=raw,file=rbd:1155823384/vm-760-disk-1.rbd:rbd_cache=false,cache=writeback,if=none,id=virtio0,media=disk,index=0 -drive format=raw,file=rbd:1155823384/vm-760-swap-1.rbd:rbd_cache=false,cache=writeback,if=virtio,media=disk,index=1 -drive if=ide,media=cdrom,id=ide1-cd0,readonly=on -drive if=ide,media=cdrom,id=ide1-cd1,readonly=on -boot order=dc
after fired up I go to the monitor socket and try a:
QEMU 1.5.0 monitor - type 'help' for more information
(qemu) savevm test123
Error -95 while writing VM
(qemu)
If I only let the error -95 happen and ignore, everything seems to be OK, though. Might be easy to fix, but not for me...
qemu up to 1.4.2 is not affected.
Please let me know, if you need more informations.
Oliver.
Triaging old bug tickets ... can you still reproduce this problem with the latest version of QEMU (currently v2.9.0)?
Hi Thomas,
thnx for coming back on this. Currently on vacation, but just gave it a shot on fresh compiled qemu-2.9.0:
—
savevm
Error while writing VM state: Operation not supported
—
I think there once existed a patch from the Proxmox guys dealing with the VM state informations. But
apparently did not make it into main-stream.
Kind regards,
Oliver.
> Am 20.07.2017 um 13:52 schrieb Thomas Huth <email address hidden>:
>
> Triaging old bug tickets ... can you still reproduce this problem with
> the latest version of QEMU (currently v2.9.0)?
>
> ** Changed in: qemu
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1185395
>
> Title:
> qemu-1.5.0 savevm error -95 while writing vm with ceph-rbd as storage-
> backend
>
> Status in QEMU:
> Incomplete
>
> Bug description:
> With a running VM I encounter this strange behaviour, former qemu-versions don't show up such an error.
> Perhaps this comes from the rbd-backend in qemu-1.5.0 in combination with ceph-0.56.6?
>
> ( -95 might be a general "Operation not supported" error? )
>
> Up to 1.4.2 everything is OK with savevm, though.
>
> Any help welcome,
>
> Oliver.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1185395/+subscriptions
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/96
|