RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1091163 - 'filename' and 'file' should not be none when use nbd storage backend for virtual block device
Summary: 'filename' and 'file' should not be none when use nbd storage backend for vir...
Keywords:
Status: CLOSED DUPLICATE of bug 1135385
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Hanna Czenczek
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-25 05:16 UTC by Sibiao Luo
Modified: 2014-11-04 08:14 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-04 08:14:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Sibiao Luo 2014-04-25 05:16:58 UTC 
Description of problem:
launch a KVM guest with a nbd storage backend for virtual block device, but check the QMP or HMP monitor that 'filename' and 'file' is none.

Version-Release number of selected component (if applicable):
host info:
# uname -r && rpm -q qemu-kvm-rhev
3.10.0-121.el7.x86_64
qemu-kvm-rhev-1.5.3-60.el7ev.x86_64
# rpm -q nbd
nbd-2.9.20-3.el7.x86_64
guest info:
# uname -r
3.10.0-121.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.start nbd-server to export a qcow2 image with absolute path on the NBD server host.
# nbd-server 12345 /home/my-data-disk.qcow2
2.launch a KVM guest with this exported image as a data disk.
# qemu-img info nbd:10.66.83.171:12345
image: 
file format: qcow2
virtual size: 10G (10737418240 bytes)
disk size: unavailable
cluster_size: 65536
Format specific information:
    compat: 1.1
    lazy refcounts: false
e.g:...-drive file=nbd:10.66.83.171:12345,if=none,id=drive-data-disk,format=qcow2,cache=none,aio=native -device virtio-scsi-pci,id=scsi1,addr=0x7,bus=pci.0 -device scsi-hd,bus=scsi1.0,drive=drive-data-disk,id=data-disk,bootindex=2
3.check the block device info via QMP/HMP.
(qemu) info block
QMP:   {"execute":"query-block"}

Actual results:
after step 3,
(qemu) info block
drive-system-disk: removable=0 io-status=ok file=/home/RHEL-7.0-20140409.0_Server_x86_64.qcow2bk ro=0 drv=qcow2 encrypted=0 bps=0 bps_rd=0 bps_wr=0 iops=0 iops_rd=0 iops_wr=0
drive-data-disk: removable=0 io-status=ok file= ro=0 drv=qcow2 encrypted=0 bps=0 bps_rd=0 bps_wr=0 iops=0 iops_rd=0 iops_wr=0
...
{"execute":"query-block"}
{"return": [...{"io-status": "ok", "device": "drive-data-disk", "locked": false, "removable": false, "inserted": {"iops_rd": 0, "image": {"virtual-size": 10737418240, "filename": "", "cluster-size": 65536, "format": "qcow2", "format-specific": {"type": "qcow2", "data": {"compat": "1.1", "lazy-refcounts": false}}, "dirty-flag": false}, "iops_wr": 0, "ro": false, "backing_file_depth": 0, "drv": "qcow2", "iops": 0, "bps_wr": 0, "encrypted": false, "bps": 0, "bps_rd": 0, "file": "", "encryption_key_missing": false}, "type": "unknown"}...]}

Expected results:
file and filename should be nbd:10.66.83.171:12345.
"filename": "nbd:10.66.83.171:12345"
"name": "nbd:10.66.83.171:12345"

Additional info:
Comment 1 Hanna Czenczek 2014-11-03 09:33:06 UTC 
Hi,

As can be seen from the status, I posted a backport which however lacked some patches. Another backport with all the required patches would be rather complicated to fix this issue, also we are past devel freeze.

Would it be okay with you to move this to RHEV? If not, I will move it to RHEL 7.2.

Max
Comment 2 Sibiao Luo 2014-11-04 02:28:35 UTC 
(In reply to Max Reitz from comment #1)
> Hi,
> 
> As can be seen from the status, I posted a backport which however lacked
> some patches. Another backport with all the required patches would be rather
> complicated to fix this issue, also we are past devel freeze.
> 
> Would it be okay with you to move this to RHEV? If not, I will move it to
> RHEL 7.2.
> 
Ok, no problem for me to move to rhev, thanks.
Comment 3 Hanna Czenczek 2014-11-04 08:14:17 UTC 

*** This bug has been marked as a duplicate of bug 1135385 ***
Note You need to log in before you can comment on or make changes to this bug.