Bug 1781490 - $dom->set_block_job_speed fails with libvirt error 'No active block job'
Summary: $dom->set_block_job_speed fails with libvirt error 'No active block job'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: perl-Sys-Virt
Version: 8.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: 8.2
Assignee: Daniel Berrangé
QA Contact: Dan Zheng
URL:
Whiteboard:
Depends On: 1780497
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-10 06:47 UTC by Dan Zheng
Modified: 2021-01-08 16:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-08 16:53:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)
libvirtd log for 300-blockjob-lifecycle.t (1.25 MB, text/plain)
2019-12-10 06:47 UTC, Dan Zheng
no flags Details
guest xml (4.64 KB, text/plain)
2019-12-10 07:04 UTC, Dan Zheng
no flags Details

Description Dan Zheng 2019-12-10 06:47:40 UTC
Created attachment 1643503 [details]
libvirtd log for 300-blockjob-lifecycle.t

Description of problem:


Version-Release number of selected component (if applicable):

libvirt-5.10.0-1.module+el8.2.0+5135+ed3b2489.x86_64
perl-Sys-Virt-5.10.0-1.module+el8.2.0+5135+ed3b2489.x86_64
qemu-kvm-4.2.0-1.module+el8.2.0+4793+b09dd2fb.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Run libvirt-tck downstream script
libvirt-tck --testdir scripts/qemu/300-blockjob-lifecycle.t -v --force
...
ok 10 - defined persistent domain config
# Starting inactive domain config
ok 11 - running domain has an ID > 0
ok 12 - start to block pull and block job bandwidth is 1MB/S
ok 13 - abort block job
ok 14 - continue to block pull and block job bandwidth is 1MB/S
ok 15 - abort block job
ok 16 - start to block pull with flag BLOCK_PULL_BANDWIDTH_BYTES and blcok job bandwidth is 2097152B/S
libvirt error code: 55, message: Requested operation is not valid: No active block job 'drive-virtio-disk1'

2. libvirtd.log
2019-12-10 05:21:51.762+0000: 29230: debug : qemuMonitorBlockJobSetSpeed:3301 : jobname=drive-virtio-disk1, bandwidth=2097152B
2019-12-10 05:21:51.762+0000: 29230: debug : qemuMonitorBlockJobSetSpeed:3303 : mon:0x7f9b1402e9a0 vm:0x7f9b00008550 fd:38
2019-12-10 05:21:51.762+0000: 29230: info : qemuMonitorSend:996 : QEMU_MONITOR_SEND_MSG: mon=0x7f9b1402e9a0 msg={"execute":"block-job-set-speed","arguments":{"device":"drive-virtio-disk1","speed":2097152},"id":"libvirt-373"}^M
 fd=-1
2019-12-10 05:21:51.762+0000: 29227: info : qemuMonitorIOWrite:453 : QEMU_MONITOR_IO_WRITE: mon=0x7f9b1402e9a0 buf={"execute":"block-job-set-speed","arguments":{"device":"drive-virtio-disk1","speed":2097152},"id":"libvirt-373"}^M
 len=114 ret=114 errno=0
2019-12-10 05:21:51.762+0000: 29227: debug : qemuMonitorJSONIOProcessLine:220 : Line [{"id": "libvirt-373", "error": {"class": "DeviceNotActive", "desc": "Block job 'drive-virtio-disk1' not found"}}]
2019-12-10 05:21:51.762+0000: 29227: info : qemuMonitorJSONIOProcessLine:240 : QEMU_MONITOR_RECV_REPLY: mon=0x7f9b1402e9a0 reply={"id": "libvirt-373", "error": {"class": "DeviceNotActive", "desc": "Block job 'drive-virtio-disk1' not found"}}
2019-12-10 05:21:51.762+0000: 29230: debug : qemuMonitorJSONBlockJobError:4934 : Requested operation is not valid: No active block job 'drive-virtio-disk1'


3.




Actual results:
See above

Expected results:
Script run PASS

Additional info:
See attachment for libvirtd.log

Comment 1 Dan Zheng 2019-12-10 07:04:31 UTC
Created attachment 1643506 [details]
guest xml

Comment 3 yisun 2019-12-10 07:56:35 UTC
this could be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1780497

Comment 4 Daniel Berrangé 2019-12-10 13:12:57 UTC
Yes, it looks like the same root cause.

Comment 5 Dan Zheng 2020-02-12 06:33:55 UTC
# rpm -q libvirt qemu-kvm kernel
libvirt-6.0.0-2.module+el8.2.0+5513+34927b6c.x86_64
qemu-kvm-4.2.0-7.module+el8.2.0+5520+4e5817f3.x86_64
kernel-4.18.0-80.el8.x86_64
kernel-4.18.0-151.el8.x86_64

Tested PASS.

Comment 8 Jeff Nelson 2021-01-08 16:53:08 UTC
Changing this TestOnly BZ as CLOSED CURRENTRELEASE. Please reopen if the issue is not resolved.


Note You need to log in before you can comment on or make changes to this bug.