summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/peripherals/1770417
blob: 3d9ec1d31b4b9182e9a1ea46c6f16923bf0fcde6 (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
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
peripherals: 0.950
graphic: 0.928
register: 0.919
device: 0.912
virtual: 0.895
permissions: 0.887
socket: 0.881
x86: 0.880
boot: 0.872
hypervisor: 0.858
network: 0.854
performance: 0.852
mistranslation: 0.848
architecture: 0.847
kernel: 0.846
semantic: 0.845
debug: 0.843
user-level: 0.842
PID: 0.819
assembly: 0.816
arm: 0.800
risc-v: 0.779
vnc: 0.769
files: 0.753
VMM: 0.710
ppc: 0.671
TCG: 0.653
KVM: 0.628
i386: 0.474

Qemu can not parse long fqdns during drive-mirror

During migration of an openstack booted instance, I got the following error:

Apr 12 10:55:22 cmp1 libvirtd[4133]: 2018-04-12 10:55:22.133+0000: 4139: error : qemuMonitorJSONCheckError:392 : internal error: unable to execute QEMU command 'drive-mirror': error parsing address 'cmp0.sandriichenko-deploy-heat-virtual-mcp-pike-ovs-76.bud-mk.local:49153'

A bit more info in libvirt bug https://bugzilla.redhat.com/show_bug.cgi?id=1568939

To reproduce it with qemu only, I followed the guide at https://github.com/qemu/qemu/blob/master/docs/interop/live-block-operations.rst#id21. On dest and source compute nodes, I launched an instance:

qemu-system-x86_64 -display none -nodefconfig -M q35 -nodefaults -m 512 -blockdev node-name=node-TargetDisk,driver=qcow2,file.driver=file,file.node-name=file,file.filename=./test-instance-mirror.qcow2 -device virtio-blk,drive=node-TargetDisk,id=virtio0 -S -monitor stdio -qmp unix:./qmp-sock,server,nowait -incoming tcp:localhost:6666

Then on dest node I launched nbd server:

(qemu) nbd_server_start cmp0:49153
(qemu) nbd_server_add -w node-TargetDisk

On the source node:

(qemu) drive_mirror -n  node-TargetDisk nbd:cmp0.vdrok-deploy-heat-virtual-mcp-pike-ovs-foobarbuzz.bud-mk.local:49153:exportname=node-TargetDisk
error parsing address 'cmp0.vdrok-deploy-heat-virtual-mcp-pike-ovs-foobarbuzz.bud-mk.local:49153'

When using short host name instead of FQDN address seems to be parsed fine:

(qemu) drive_mirror -n  node-TargetDisk nbd:cmp0:49153:exportname=node-TargetDisk qcow2
Image is not in qcow2 format

(not sure why it is not a qcow2 format, as I have qcow2 image with raw backing file, but this is unrelated)

QEMU version is 2.11.1 from bionic

As Daniel asked in [1] making this abug report against Qemu (upstream).

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1568939 

Ubuntu task is not actionable until we settled on how to change the parsing code for long strings upstream, so I set it to confirmed but wishlist (until we know what size a patch - or actions a recommendation on handling differently has).

The QEMU project is currently considering to move its bug tracking to
another system. For this we need to know which bugs are still valid
and which could be closed already. Thus we are setting older bugs to
"Incomplete" now.

If you still think this bug report here is valid, then please switch
the state back to "New" within the next 60 days, otherwise this report
will be marked as "Expired". Or please mark it as "Fix Released" if
the problem has been solved with a newer version of QEMU already.

Thank you and sorry for the inconvenience.


[Expired for QEMU because there has been no activity for 60 days.]

[Expired for qemu (Ubuntu) because there has been no activity for 60 days.]