Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1363800 - [RFE] [ESX] libvirt doesn't indicate if a VM is a template or a VM
Summary: [RFE] [ESX] libvirt doesn't indicate if a VM is a template or a VM
Status: NEW
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
Depends On:
Blocks: 1363692 1363693 1363796
TreeView+ depends on / blocked
Reported: 2016-08-03 15:13 UTC by Richard W.M. Jones
Modified: 2018-07-18 14:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1363796
Last Closed:

Attachments (Terms of Use)

Description Richard W.M. Jones 2016-08-03 15:13:40 UTC
Description of problem:

To implement bug #1363796 libvirt needs to tell virt-v2v if an
ESX VM is a template or a VM.

Additional info:

an example from virsh dumpxml of vCenter template:
[root@intel-vfio vdsm]# virsh -c 'vpx://administrator@*****/Folder1/Folder2/Compute/Folder3/Cluster/*****?no_verify=1' dumpxml "RHEL7_2_template"
Enter administrator's password for *****: 
<domain type='vmware' xmlns:vmware=''>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <vcpu placement='static'>2</vcpu>
  <type arch='x86_64'>hvm</type>
  <clock offset='utc'/>
  <disk type='file' device='disk'>
  <source file='[NFS_ISO] RHEL7_2/RHEL7_2.vmdk'/>
  <target dev='sda' bus='scsi'/>
  <address type='drive' controller='0' bus='0' target='0' unit='0'/>
  <controller type='scsi' index='0' model='vmpvscsi'/>
  <interface type='bridge'>
  <mac address='00:1a:4a:16:01:55'/>
  <source bridge='VM Network'/>
  <model type='vmxnet3'/>
  <model type='vmvga' vram='8192'/>

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