Bug 1876984 - VM with a SCSI hostdev fails to start due to "node-name too long for qemu"
Summary: VM with a SCSI hostdev fails to start due to "node-name too long for qemu"
Keywords:
Status: CLOSED DUPLICATE of bug 1876467
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: libvirt
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.3
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1876605
TreeView+ depends on / blocked
 
Reported: 2020-09-08 16:16 UTC by Milan Zamazal
Modified: 2020-09-08 16:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-08 16:32:02 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Milan Zamazal 2020-09-08 16:16:58 UTC
Description of problem:

When a VM contains a device like

  <hostdev managed="no" mode="subsystem" rawio="yes" type="scsi">
    <source>
      <adapter name="scsi_host16"/>
      <address bus="0" target="0" unit="4"/>
    </source>
    <alias name="ua-a03481b3-d43c-4fa1-9566-640e092f384e"/>
  </hostdev>

in its domain XML, it fails to start with the following error message from libvirt:

  error : qemuBlockNodeNameValidate:46 : internal error: node-name 'libvirt-ua-a03481b3-d43c-4fa1-9566-640e092f384e-backend' too long for qemu

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

6.6.0-4.module+el8.3.0+7883+3d717aa8

How reproducible:

100%

Steps to Reproduce:
1. Start a VM with a SCSI hostdev similar to the one above.

Actual results:

VM fails to start.

Expected results:

VM starts.

Additional info:

See Bug 1876605 for logs and more info if needed.

It looks related to libvirt commit 245ed36e9764906f6164ba20e4531fa0b1c4dd3c. libvirt documentation doesn't state any limits on user alias length. The alias is used to make a storage node name, which is later rejected because it exceeds the 32 characters limit.

Comment 1 Jiri Denemark 2020-09-08 16:32:02 UTC

*** This bug has been marked as a duplicate of bug 1876467 ***


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