Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
The NBD block driver is necessary to support the new scheme for migration with non-shared storage. Also, we're supporting almost all of the code in qemu-nbd (via the monitor), so we probably should enable it as well.
FYI from a libvirt POV we will be needing the NBD driver in the future to support use of qcow2 disk images with LXC guests. Upstream LKML have indicated that they consider NBD to be the FUSE equivalent for the block layer, so qemu-nbd + NBD kmod are the only way for use to get QCow2 support for LXC, unless someone fancies extending the Loopback driver to support qcow2.
OpenStack already uses NBD kernel driver + qemu-img for support LXC + qcow2 disk. Though we don't intend to officially support LXC with OpenStack in RHEL, it would still be useful if the kmod existed, so people can use RHEL as a viable dev platform for OpenStack.
> Paolo, there's no qemu configure option to enable nbd.
There is:
--block-drv-whitelist=qcow2,raw,file,host_device,host_cdrom,qed
we need to add "nbd" here.
> However, you mentioned it's better not to enable qemu-nbd so I guess we
> shouldn't do anything about this yet.
I think we're enabling qemu-nbd in RHEL6, so we'll have to enable it in RHEL7.
Separate problem.
Comment 11Miroslav Rezanina
2013-05-24 10:20:42 UTC
Verified on qemu-kvm-rhev-1.5.3-39.el7.x86_64:
qemu-nbd -t -p 10000 RHEL-Server-7.0-64-virtio.raw
><fs> run
100% ⟦▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒⟧ 00:00
><fs> list-filesystems
/dev/sda1: xfs
/dev/rhel/root: xfs
/dev/rhel/swap: swap
><fs> mount /dev/rhel/root /
><fs> ls /
bin
boot
dev
etc
home
lib
lib64
media
mnt
opt
proc
root
run
sbin
srv
sys
tmp
usr
var
><fs> ls /
bin
boot
dev
etc
home
lib
lib64
media
mnt
opt
proc
root
run
sbin
srv
sys
tmp
usr
var
><fs> cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.0 Beta (Maipo)
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
RHEL6 is THE current release till 2020-11-30 (until EOL).
RHEL6 != RHEL7.
You should remove the possibility to close RHEL6 bugs/feature request by using RHEL7 as "current release". If unimplementable then use "no can do".
//arl (Ari Lemmke)
(In reply to Ari Lemmke from comment #35)
> RHEL6 is THE current release till 2020-11-30 (until EOL).
> RHEL6 != RHEL7.
Red Hat supports multiple RHEL versions at the same time. See https://access.redhat.com/support/policy/updates/errata/ for detailed description of of RHEL Life Cycle and list of actively supported versions.
> You should remove the possibility to close RHEL6 bugs/feature request by
> using RHEL7 as "current release". If unimplementable then use "no can do".
Note that this bug was originally filed for RHEL 7.0 (see history). Because of it was resolved in RHEL 7.0 (see comment #31), the bug was CLOSED CURRENTRELEASE. If there is any issue with this feature contact your support representative, please.