* [Qemu-devel] [Bug 1770417] Re: Qemu can not parse long fqdns during drive-mirror
[not found] <152596210054.26788.14569755785770428905.malonedeb@chaenomeles.canonical.com>
@ 2018-05-11 8:48 ` ChristianEhrhardt
2018-05-11 8:49 ` ChristianEhrhardt
` (4 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: ChristianEhrhardt @ 2018-05-11 8:48 UTC (permalink / raw)
To: qemu-devel
As Daniel asked in [1] making this abug report against Qemu (upstream).
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1568939
** Bug watch added: Red Hat Bugzilla #1568939
https://bugzilla.redhat.com/show_bug.cgi?id=1568939
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1770417
Title:
Qemu can not parse long fqdns during drive-mirror
Status in QEMU:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1770417/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Qemu-devel] [Bug 1770417] Re: Qemu can not parse long fqdns during drive-mirror
[not found] <152596210054.26788.14569755785770428905.malonedeb@chaenomeles.canonical.com>
2018-05-11 8:48 ` [Qemu-devel] [Bug 1770417] Re: Qemu can not parse long fqdns during drive-mirror ChristianEhrhardt
@ 2018-05-11 8:49 ` ChristianEhrhardt
2021-05-02 5:38 ` Thomas Huth
` (3 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: ChristianEhrhardt @ 2018-05-11 8:49 UTC (permalink / raw)
To: qemu-devel
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).
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
** Changed in: qemu (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1770417
Title:
Qemu can not parse long fqdns during drive-mirror
Status in QEMU:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1770417/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug 1770417] Re: Qemu can not parse long fqdns during drive-mirror
[not found] <152596210054.26788.14569755785770428905.malonedeb@chaenomeles.canonical.com>
2018-05-11 8:48 ` [Qemu-devel] [Bug 1770417] Re: Qemu can not parse long fqdns during drive-mirror ChristianEhrhardt
2018-05-11 8:49 ` ChristianEhrhardt
@ 2021-05-02 5:38 ` Thomas Huth
2021-07-05 6:20 ` Thomas Huth
` (2 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: Thomas Huth @ 2021-05-02 5:38 UTC (permalink / raw)
To: qemu-devel
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.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1770417
Title:
Qemu can not parse long fqdns during drive-mirror
Status in QEMU:
Incomplete
Status in qemu package in Ubuntu:
Confirmed
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1770417/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug 1770417] Re: Qemu can not parse long fqdns during drive-mirror
[not found] <152596210054.26788.14569755785770428905.malonedeb@chaenomeles.canonical.com>
` (2 preceding siblings ...)
2021-05-02 5:38 ` Thomas Huth
@ 2021-07-05 6:20 ` Thomas Huth
2021-09-04 4:17 ` Launchpad Bug Tracker
2021-09-04 4:17 ` Launchpad Bug Tracker
5 siblings, 0 replies; 6+ messages in thread
From: Thomas Huth @ 2021-07-05 6:20 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu (Ubuntu)
Status: Confirmed => Incomplete
** Bug watch removed: Red Hat Bugzilla #1568939
https://bugzilla.redhat.com/show_bug.cgi?id=1568939
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1770417
Title:
Qemu can not parse long fqdns during drive-mirror
Status in QEMU:
Incomplete
Status in qemu package in Ubuntu:
Incomplete
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1770417/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug 1770417] Re: Qemu can not parse long fqdns during drive-mirror
[not found] <152596210054.26788.14569755785770428905.malonedeb@chaenomeles.canonical.com>
` (3 preceding siblings ...)
2021-07-05 6:20 ` Thomas Huth
@ 2021-09-04 4:17 ` Launchpad Bug Tracker
2021-09-04 4:17 ` Launchpad Bug Tracker
5 siblings, 0 replies; 6+ messages in thread
From: Launchpad Bug Tracker @ 2021-09-04 4:17 UTC (permalink / raw)
To: qemu-devel
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1770417
Title:
Qemu can not parse long fqdns during drive-mirror
Status in QEMU:
Expired
Status in qemu package in Ubuntu:
Expired
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1770417/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug 1770417] Re: Qemu can not parse long fqdns during drive-mirror
[not found] <152596210054.26788.14569755785770428905.malonedeb@chaenomeles.canonical.com>
` (4 preceding siblings ...)
2021-09-04 4:17 ` Launchpad Bug Tracker
@ 2021-09-04 4:17 ` Launchpad Bug Tracker
5 siblings, 0 replies; 6+ messages in thread
From: Launchpad Bug Tracker @ 2021-09-04 4:17 UTC (permalink / raw)
To: qemu-devel
[Expired for qemu (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1770417
Title:
Qemu can not parse long fqdns during drive-mirror
Status in QEMU:
Expired
Status in qemu package in Ubuntu:
Expired
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1770417/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2021-09-04 4:27 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <152596210054.26788.14569755785770428905.malonedeb@chaenomeles.canonical.com>
2018-05-11 8:48 ` [Qemu-devel] [Bug 1770417] Re: Qemu can not parse long fqdns during drive-mirror ChristianEhrhardt
2018-05-11 8:49 ` ChristianEhrhardt
2021-05-02 5:38 ` Thomas Huth
2021-07-05 6:20 ` Thomas Huth
2021-09-04 4:17 ` Launchpad Bug Tracker
2021-09-04 4:17 ` Launchpad Bug Tracker
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.