Bug 695655

Summary: libvirt fails to create usable vmx/vmdk on vSphere 4.1
Product: [Community] Virtualization Tools Reporter: David Schmitt <david>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DEFERRED QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: corey, crobinso, xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-23 12:33:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
the various config files none

Description David Schmitt 2011-04-12 10:30:52 UTC 
Created attachment 491449 [details]
the various config files

Description of problem:

when creating a new virtual machine with virsh on an esx machine that is part of a vSphere 4.1 installation, the created machine fails to start.

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

tried with locally built rpm from libvirt 0.9.0

How reproducible:

every time

Steps to Reproduce:
1. dump xml for volume and virtual machine from a vpx:// hypervisor
2. remove virtual machien and disk from vmware
3. create the disk by connecting to the underlying esx:// instance
4. define and start the virtual machine via the vpx:// hypervisor
  
Actual results:

The virtual machine doesn't start and vSphere displays this error:

> Failure to configure virtual device scsi0
> Unable to allocate a PCI SCSI adapter. Too many PCI devices are already configured.

Expected results:

The virtual machine boots.

Additional info:

The attached tar ball contains the original configuration as created by vSphere, using a "typical" machine, as well as the dumpxml output and the vmx/vmdk as created by libvirt when using the dumped xml.
Comment 1 Corey Osman 2011-10-30 03:39:59 UTC 
I was getting this same error on just esxi 4.1.  I then rebuilt my xml file according to what was posted here:

http://libvirt.org/drvesx.html#xmlconfig

I also used the lsilogic controller.  Not sure what the actual cause was but  here is my xml that I created.

<domain type='vmware' >
  <name>test-host-1319949751</name>
  <memory>1048576</memory>
  <currentMemory>1048576</currentMemory>
  <vcpu>1</vcpu>
  
  <os>
    <type arch='x86_64'>hvm</type>
     <boot dev='network'/>
    <boot dev='hd'/>
  </os>
  <clock offset='utc'/>
  <devices>
    <disk type='file' device='disk'>
      <source file='[default] test-host-1319949751/test-host-1319949751.vmdk'/>
      <target dev='sda' bus='scsi'/>
      <address type='drive' controller='0' bus='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <source file='[default] apps/fakemedia.iso'/>
      <target dev='hda' bus='ide'/>
      <address type='drive' controller='0' bus='0' unit='0'/>
    </disk>
    <controller type='scsi' index='0' model='lsilogic'/>
  	<controller type='ide' index='0'/>
    <interface type='bridge'>
       <source bridge='VM Network'/>
    
    </interface>
    <graphics type='vnc' port='5901' autoport='no'>

    </graphics>
    <video>
      <model type='vmvga' vram='32768'/>
    </video>
   
  </devices>
</domain>
Comment 2 Cole Robinson 2016-03-23 12:33:04 UTC 
Sorry this never received a response. The vmware handling was under active development when this was filed, so I suspect it was eventually fixed. If anyone can still reproduce with latest libvirt, please provide the non-working that was causing the issue and reopen this bug