Bug 2068992

Summary: [RFE]Detect nvme disks/controller from VMware by virsh
Product: Red Hat Enterprise Linux 9 Reporter: mxie <mxie>
Component: libvirtAssignee: Virtualization Maintenance <virt-maint>
libvirt sub component: Storage QA Contact: mxie <mxie>
Status: CLOSED MIGRATED Docs Contact:
Severity: medium    
Priority: medium CC: chhu, hongzliu, jsuchane, juzhou, lersek, lmen, mzhan, rjones, tyan, tzheng, virt-maint, vwu, xiaodwan, xuzhang
Version: 9.1Keywords: FutureFeature, MigratedToJIRA, Triaged
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 16:39:04 UTC Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vmware-guest-nvme-disks.png none

Description mxie@redhat.com 2022-03-28 03:31:03 UTC
Created attachment 1868645 [details]
vmware-guest-nvme-disks.png

Description of problem:
[RFE]Detect nvme disks/controller from VMware by virsh

Version-Release number of selected component (if applicable):
libvirt-libs-8.1.0-1.el9.x86_64
qemu-img-6.2.0-12.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Prepare a windows which nvme disk and nvme controller on VMware, please refer to screenshot
2.Use virsh to dump the guest xml from VMware
# virsh -c  vpx://root.198.169/data/10.73.199.217/?no_verify=1 dumpxml esx7.0-win2022-x86_64-uefi
Enter root's password for 10.73.198.169: 
.....
  <devices>
    <disk type='file' device='disk'>
      <source file='[esx7.0-matrix] esx7.0-win2022-x86_64/esx7.0-win2022-x86_64-000001.vmdk'/>
      <target dev='sda' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <source file='[tools] tools/os-installation-iso/en-us_windows_server_2022_x64_dvd_620d7eac.iso'/>
      <target dev='sda' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='scsi' index='0' model='lsisas1068'/>
    <controller type='sata' index='0'/>
    <interface type='bridge'>
      <mac address='00:50:56:83:e9:6e' type='generated'/>
      <source bridge='VM Network'/>
      <model type='e1000e'/>
    </interface>
    <video>
      <model type='vmvga' vram='8192' primary='yes'/>
    </video>
  </devices>
  <vmware:datacenterpath>data</vmware:datacenterpath>
  <vmware:moref>vm-6329</vmware:moref>
</domain>



Actual results:
Can't detect nvme disks/controller from VMware by virsh 

Expected results:
As above description

Additional info:

Comment 1 Vera 2022-06-23 04:13:13 UTC
checked with the versions:
libvirt-8.4.0-2.el9.x86_64
qemu-img-7.0.0-6.el9.x86_64

# virsh -c vpx://root.73.141/data/10.73.75.219/?no_verify=1 dumpxml esx6.7-rhel8.6-nvme-disk
Enter root's password for 10.73.73.141: 
<domain type='vmware' xmlns:vmware='http://libvirt.org/schemas/domain/vmware/1.0'>
  <name>esx6.7-rhel8.6-nvme-disk</name>
  <uuid>422c176d-0b31-4e16-8297-f0b4990b8609</uuid>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <vcpu placement='static'>1</vcpu>
  <cputune>
    <shares>1000</shares>
  </cputune>
  <os>
    <type arch='x86_64'>hvm</type>
  </os>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <interface type='bridge'>
      <mac address='00:50:56:ac:cf:51' type='generated'/>
      <source bridge='VM Network'/>
      <model type='vmxnet3'/>
    </interface>
    <video>
      <model type='vmvga' vram='8192' primary='yes'/>
    </video>
  </devices>
  <vmware:datacenterpath>data</vmware:datacenterpath>
  <vmware:moref>vm-3097</vmware:moref>
</domain>


There is no any disk info including basic location.

Comment 3 RHEL Program Management 2023-09-22 16:36:21 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-22 16:39:04 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.