VMware's paravirtualized SCSI controller

Similar Questions

• VMware Paravirtual SCSI adapter

  Is there a reason the "VMware Paravirtual SCSI" is not to use it?

  I would use this adapter for each VM of data partitions (not partitions to boot).

  Reason: Have the hole identitical environment.

  I have only heard one drawback: VMs with e/s low will have no gain performance on the SCSI adapter which is usually used.

  Thanks for your review!

  Simon

  Is there a reason the "VMware Paravirtual SCSI" is not to use it?

  If you do not need FT, I see no reason right now.

  See http://blog.scottlowe.org/2009/07/05/another-reason-not-to-use-pvscsi-or-vmxnet3/

  I would use this adapter for each VM of data partitions (not partitions to boot).

  I guess you know that, anyway.

  of the http://www.vmware.com/support/vsphere4/doc/vsp_esx40_u1_rel_notes.html

  Improved VMware's paravirtualized SCSI support

  Support for devices connected to an adapter (PVSCSI) paravirtualized SCSI boot drive has been added for Windows 2003 and 2008 guest operating systems...

  André

• vCenter device SCSI Controller

  Hello

  All the world looked at changing the vCenter device SCSI controller? I find it strange that the device is delivered without using the paravirtual SCSI controller, we saw good returns when upgrade to that and I would like all areas if possible (called limits taken into account).

  I appreciate the device is distributed "such what ' and change of way would probably cancel all support, but I'm still curious to know if anyone has tried.

  Looks like I'm the only one with something to add...
  .

  End a call with a VMware engineer who confirmed that the PVSCSI controller is not supported on the existing device of the vCenter. This is because it is running SUSE Linux 11 without service pack 1 is required to support.

  Obviously, the engineer could not comment on future developments, but perhaps a new version of the device will run on a later version of SUSE that supports the adapter PVSCSI.

• Add the new SCSI controller and new drive - powershell SDK

  Hi all

  I'm trying to add the new disc of paravirtual to my VMs. There are two types of virtual machines in the environment; a Paravirtual controller attached and others are without controller; so my task is to set the new drive of paravitual using powershell SDK.

  So far I am successful with my code if the controller is already present but the script fails when I try to attach the controller. with the error.

  RecommendDatastores: The method call failed because [System.Object []] contains a method named "RecommendDatastores".

  C:\NodeDeployment\Inprogress\Add_newPVScsiDisk.ps1:111 tank: 44

  + $generatedkey = $SRM. RecommendDatastores < < < < ($storageSpec)

  + CategoryInfo: InvalidOperation: (RecommendDatastores:String)], RuntimeException

  + FullyQualifiedErrorId: MethodNotFound

  
  

  I know that this script is not good enough to post here because it is an initial draft, but in the script attached please help me with the present part-

  The Script requires a csv with VMname entry; Disksize to be attached and store cluster data

  else {
              Write-Host "Paravirtualized SCSI Controller Not Found in $vmname.. Trying to add new scsi controller and additional Hard-disk..."
              $NewSCSIDevice = New-Object VMware.Vim.VirtualDeviceConfigSpec
              $NewSCSIDevice.operation = "add"
              $NewSCSIDevice.device = New-Object VMware.Vim.ParaVirtualSCSIController
              $NewSCSIDevice.device.key = -222
              $NewSCSIDevice.device.busNumber = ($allScSiController.BusNumber.Count)
              $NewSCSIDevice.device.sharedBus = "noSharing"
              $NewDiskDevice.device.controllerKey = -222
              $NewDiskDevice.device.unitNumber = 0
              $NewDiskDevice.device.capacityInKB = ($diskSize * (1024 * 1024))
              $storageSpec.configSpec.deviceChange += $NewDiskDevice
              $storageSpec.configSpec.deviceChange += $NewSCSIDevice
              $generatedkey = $SRM.RecommendDatastores($storageSpec)
              $key = $generatedkey.Recommendations[0].Key
              $SRM.ApplyStorageDrsRecommendation_Task($key)
  }
  
  

  OK I have it myself; I guess busnumber was the problem. He converted to INT working like charm...

  Now, I have to work with storage Drs IE. with the ReconfigureVM_task method. hoping that will work also...

  else {}

  [int] $busnumber = $allScSiController.Count

  Write-Host "paravirtualized SCSI Controller not found in $vmname... Try to add the new controller scsi and extra hard drives... »

  $NewSCSIDevice = new-Object VMware.Vim.VirtualDeviceConfigSpec

  $NewSCSIDevice.operation = 'Add '.

  $NewSCSIDevice.device = new-Object VMware.Vim.ParaVirtualSCSIController

  $NewSCSIDevice.device.key = - 222

  $NewSCSIDevice.device.busNumber = $busnumber

  $NewSCSIDevice.device.sharedBus = "noSharing".

  $NewDiskDevice.device.controllerKey = - 222

  $NewDiskDevice.device.unitNumber = 0

  $NewDiskDevice.device.capacityInKB = ($diskSize * (1024 * 1024))

  $storageSpec.configSpec.deviceChange += $NewDiskDevice

  $storageSpec.configSpec.deviceChange += $NewSCSIDevice

  $generatedkey = $SRM. RecommendDatastores ($storageSpec)

  $key = $generatedkey. Recommendations [0]. Key

  $SRM. ApplyStorageDrsRecommendation_Task ($key)

  }

  ---

  Concerning
  Sanshis

• Remove the SCSI controller change question of VMWare

  Hello

  I used PowerCLI for create a virtual machine and replace it with instead of buslogic SCSI LSILogic controller. I did it by using the following code:

  function updateSCSIController ($vmName, $ctrlName)

  {

  $vm = get - VM $vmName | Get-View

  1. Get the controller and devices on

  $vm. Config.Hardware.Device | where {$_.} DeviceInfo.Label - eq $ctrlName} | % {

  $oldCtrl = $_

  $ctrlKey = $_. Key

  $devs = @)

  $_. Device | % {

  $devKey = $_

  $vm. Config.Hardware.Device | where {$_.} Key - eq $devKey} | % {

  $devs += $_

  }

  }

  }

  1. Create the specification for the device changes

  $bootDelay = 10000

  $spec = new-Object VMware.Vim.VirtualMachineConfigSpec

  $spec. BootOptions = New-Object VMware.Vim.VirtualMachineBootOptions

  $spec. BootOptions.BootDelay = $bootDelay

  1. Remove the old controller

  $old = new-Object VMware.Vim.VirtualDeviceConfigSpec

  $old.device = $oldCtrl

  $old.operation = 'delete '.

  $spec. DeviceChange += $old

  1. Update the devices connected to the controller

  $devs | % {

  $dev = new-Object VMware.Vim.VirtualDeviceConfigSpec

  $dev.device = $_

  $dev.device.ControllerKey = - 100

  $dev.operation = "Edit."

  $spec. DeviceChange += $dev

  }

  1. Add the new controller

  $new = new-Object VMware.Vim.VirtualDeviceConfigSpec

  $new. Device = New-Object VMware.Vim.VirtualLsiLogicController

  $new. Device.Key = - 100

  $new. Device.ControllerKey = $oldCtrl.ControllerKey

  $new. Device.UnitNumber = $oldCtrl.UnitNumber

  $new.operation = 'Add '.

  $spec. DeviceChange += $new

  $vm. ReconfigVM ($spec)

  }

  However when I try to start the virtual machine Via code, it gives me an error saying that the virtual machine has questions to be decided.

  This is the question asked by VMWare:

  sg.disk.AdapterMismatch: the disk attached to the node SCSI0:0 has been created for the Buslogic SCSI adapter but SCSI0 Virtual Machine device is a SCSI LSI Logic card.

  VMware ESX Server can change the free disc adapter type. Attention of the user, if a guest operating system is installed on the drive, it is perhaps not able to start.

  Do you think Vmware ESX Server to change the type of adapter for SCSI0:0 disk

  This issue can be removed through PowerCLI?

  This is the part of code that fails

  updateSCSIController - vmName $name - ctrlName "SCSI controller 0.

  Start-VM - $vm VM - confirm: $false

  $vm | Get-CDDrive. Game-CDDrive-connected: $true - confirm: $false

  I don't know if you can remove the question, but you can respond with the Set-VMQuestion cmdlet.

  ____________

  Blog: LucD notes

  Twitter: lucd22

• Why do not the remove-hard drive remove a disc with a new SCSI controller?

  Hi PowerCLI gurus,

  I try to use PowerCLI to automate the solution for article configuration of disks to use VMware Paravirtual (PVSCSI) SCSI adapters (1010398).

  Remove-hard drive sometimes gives me a misleading error when I use it to remove a hard drive with a new SCSI controller.

  The FlatHardDisk specified 'Hard disk 3' no longer exists, or never existed.

  Can anyone here explain the error?

  My version of vCenter server is 5.1.0.

  My PowerCLI version is 2.0.

  Here's what I've done to reproduce the error.

  First of all, I connect to vCenter and stop the virtual machine.

  $TestVM = 'TESTVM '.

  $TestServer = ' vcenter - test.local ".

  SE connect-VIServer-Server $TestServer

  Stop-VM - $TestVM VM - confirm: $false

  I add a new hard drive and store it in a variable so I can refer to it for the next steps.

  New hard drive '.

  -VM $TestVM '

  -Persistent persistence"

  -Flat DiskType '

  CapacityKB - 1024'

  StorageFormat - thin '

  -OutVariable TempDisk

  I make a note of its name.

  $TempDisk.Name

  Because my VM already has 2 discs, the output is "hard drive 3.

  Then I add a new SCSI controller on the hard drive.

  New SCSI controller.

  Hard drive - $TempDisk '

  -Type ParaVirtual '

  NoSharing - BusSharingMode

  Now, I try to remove the hard drive from the variable to remove the disc.

  Remove-hard drive - hard drive $TempDisk - DeletePermanently-confirm: $false

  It fails with an error that says "Hard drive 3" has already been removed.

  Remove HDD: 12/02/2014-18:51:33 remove-hard drive the FlatHardDisk specified 'Hard disk 3' no longer exists, or never existed.

  On line: 1 char: 1

  + Delete-hard drive - hard drive $TempDisk - DeletePermanently-confirm: $false

  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: ObjectNotFound: (3:FlatHardDiskImpl drive) [Remove-hard drive], VimException

  + FullyQualifiedErrorId: Client20_VirtualDeviceServiceImpl_TryValidateDeviceExists_DeviceDoesNotExist, VMware.VimAutomation.ViCore.Cmdlets.Commands.RemoveHardDisk

  But I see that there are still "hard drive 3"!

  Get-disk hard - VM $TestVM - name 'hard drive 3.

  CapacityGB persistence Filename

  ----------      -----------                                    --------

  0.001 persist... B-DATA-01] TESTVM/TESTVM_9.vmdk

  Is this a bug or am I missing something?

  I don't think that the cmdlet uses actually the UID, but more likely a MoRef to the vSphere object that represents the hard disk.

  Remember that under the covers most of the PowerCLI cmdlets do calls to the vSphere API.

  Change the Uid, property value indicates that the hard drive connected to the new controller is a new and different purpose.

  And this explains why the hard drive remove does not work with the original hard disk object, it no longer exists.

• SCSI controller set do not change type

  Hello

  I have run this command, but for some strange reason the type set-change SCSI controller does not work

  $scsiController = Get - hard drive -VM 'vm001' | Select -First 1 | Get - SCSI controller

  SCSI controller set

  SCSI - controller $scsiController -Type ParaVirtual -BusSharingMode NoSharing -confirm:$false

  This gives me a

  WARNING: Changing the type of the virtual machine boot disk controller prevents the VM to start properly.

  However, the order is processed I can see re-configuration of the VM, but when I check the type of controller it is always set to its default value VirtualLsiLogicSAS

  No idea why?

  Hi new fxpro,

  See the workaround for the problem proposed here: http://communities.vmware.com/message/1703596#1703596

  Given that the operation is valid until the vSphere Client, using New-controller SCSI should help in your case.

  Irina

• Adding a virtual drive on the SCSI controller with sharing fails physical/virtual

  I have added a virtual disk to a SCSI controller with bus sharing physical or virtual, which is put down to the code below. Same code gets successfully if the bus share is 'noSharing '.

  $vmView = Vim::find_entity_view (view_type = > 'VirtualMachine', filter = > {name = > $vms [0]});
  $controllerKey = find_scsi_cntlrkey (vm = > $vmView, controller = > $cntlr);
  my hash % =)
  VM = > $vmView,
  diskMode = > 'persistent. "
  fileName = > $filename,
  controllerKey = > $controllerKey,
  unitNumber = > $target,
  size = > "5242880",.
  backingtype = > "ordinary."
  UUID = > UNDEF,
  deviceName = > UNDEF,
  );
  My $filespec = get_vdiskSpec (%hash);
  print Dumper $filespec;
  My $vdisk = add_virtualdisk (vm = > $vmView, devspec = > $filespec);

  Run the command:

  amrut@2:~/scripts/VMware/apps$ perl RDM_add.pl - vmname vm1 - Server vcenter_server name of [email protected] past Pass@123--op generation add - 2, 2 - controller filename vm_232
  Addition of new LsiLogicSAS vSCSI 2 Controller to "vm1.
  Successfully added
  $VAR1 = bless ({}
  'fileOperation' = > bless ({}
  'val' = > 'create '.
  (}, 'VirtualDeviceConfigSpecFileOperation'),
  'operation' = > bless ({}
  'val' = > 'Add '.
  (}, 'VirtualDeviceConfigSpecOperation'),
  'device' = > ({bless him
  'capacityInKB' = > '5242880',.
  "backup" = > bless ({}
  'Filename' = > ' [datastore1 (4)]/vm1/vm_232.vmdk',)]
  'diskMode' = > 'persistent '.
  (}, "VirtualDiskFlatVer2BackingInfo").
  'unitNumber' = > 2,
  'controllerKey' = > '1002',.
  'key' = >-1
  (}, "VirtualDisk")
  (}, "VirtualDeviceConfigSpec");
  Cannot configure the virtual device.

  amrut@2:~/scripts/VMware/apps$

  In vcenter GUi I get below error:

  Has no power on scsi2:2.
  Cannot add the disk scsi2:2.

  But more successful if sharing of bus is none!

  amrut@uptohell2:~/scripts/VMware/apps$ perl RDM_add.pl - vmname vm1 - Server vcenter_server name of [email protected] past Pass@123--op generation add - 1:2 - filename vm_232 controller
  $VAR1 = bless ({}
  'fileOperation' = > bless ({}
  'val' = > 'create '.
  (}, 'VirtualDeviceConfigSpecFileOperation'),
  'operation' = > bless ({}
  'val' = > 'Add '.
  (}, 'VirtualDeviceConfigSpecOperation'),
  'device' = > ({bless him
  'capacityInKB' = > '5242880',.
  "backup" = > bless ({}
  'Filename' = > ' [datastore1 (4)]/vm1/vm1_232.vmdk',)]
  'diskMode' = > 'persistent '.
  (}, "VirtualDiskFlatVer2BackingInfo").
  'unitNumber' = > 2,
  'controllerKey' = > '1001'.
  'key' = >-1
  (}, "VirtualDisk")
  (}, "VirtualDeviceConfigSpec");
  Created virtual disk.
  amrut@2:~/scripts/VMware/apps$

  Can you get it someone please let me know, we should pass us any other parameter for the addition of SCSI controller with bus sharing physical/virtual disk?

  Thank you

  Celine

  Yes, the stand is adjustable to all types at deployment time.  You need to change your disk with the correct support add operation.

• Addition of RDM but bo SCsi controller is added

  Hello

  I am trying to create a cluster between two virtual machines that are on two servers different esxi. I use SAN VNX 5100. My esxi version is 5.1.

  I am trying to add RDM hard drive but when I completed the steps, it didn't add the SCSi controller.

  Any idea?

  Kind regards

  Talha

  This statement is a useful guide that covers the process for a few common scenarios: http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-mscs-guide.pdf

• Script to list all the VMS and their scsi controller

  Hey guys,.

  New to scripting and my boss is looking for me to get a list of all the vm in our environment and the type of scsi controller they have. It seeks to go to paravirtual controller and need to know what vm, he needs to hit. I saw there is a script to change the paravirtual but he won't do it again, just the list including vm has what. Any help would be greatly appreciated.

  Thank you

  Rich

  Something like that?

  Get-VM | Select Name,@{N="Controller Type";E={Get-ScsiController -VM $_ | Select -ExpandProperty Type}}
  

• Trying to type of SCSI controller with guest operating system list

  I'm trying to shoot a list using PowerCLI of each virtual machine, each SCSI controller and the operating system, it runs. I'm able to pull data very well, but the problem that I am running attempts to export it with anything (html, csv, xml). Here is my script up to now:

  $vm = get-View - ViewType VirtualMachine-property @("nom", "Config.Hardware.Device", "Guest.GuestFullName") | Select-Object - property name, @{N = "SCSI controller"; E={($_. Config.Hardware.Device | where {$_.} DeviceInfo.Label - match "SCSI"}). DeviceInfo.Summary}}, @{N = 'Running OS'; E={$_. Guest.GuestFullName}} | Format-Table - Autosize-Wrap

  The problem that I am running is when I try to make:

  $vm | convetto-html

  It exports which seems to be a GUID ID, but not the actual data. If I echo the variable $vm, I see the data I expect to formatted as I want to, I can't go out only in a format outside of the console. I also tried another method

  $vms = get-View - ViewType VirtualMachine-property @("nom", "Config.Hardware.Device", "Guest.GuestFullName")
  $result = @)
  foreach ($vm to $vms)
  {
  $newrow = "" | Select-object Name, controller, OS
  $newrow.name = $vm.name
  $newrow.controller = $vm | Select-Object - property ($_.) Config.Hardware.Device | where {$_.} DeviceInfo.Label - match "SCSI"}). DeviceInfo.Summary
  $newrow.os = $vm | Select-Object - property $____. Guest.GuestFullName
  $result += $newrow
  }

  It lists the name of the virtual machine, but the other two columns show VMware.Vim.VirtualMachine. Probably missing me something simple here, but I can't understand it. What Miss me?

  Thank you for your help in advance.

  Try this:

  $vms = Get-View -ViewType VirtualMachine -Property @("Name", "Config.Hardware.Device", "Guest.GuestFullName")
  $result = @()
  foreach($vm in $vms)
  {
      $newrow = "" | select-object Name, Controller, OS
      $newrow.name = $vm.name
      $newrow.controller = ($vm.Config.Hardware.Device | where{$_.DeviceInfo.Label -match "SCSI"}).DeviceInfo.Summary
      $newrow.os = $vm.Guest.GuestFullName
      $result += $newrow
  }
  

• Manual addition of SCSI controller

  Hello

  I got in trouble, adding to a SCSI controller. My code looks like this:

  name = "SSCI Controller";
  description = "SSCI Controller";
  address = 0;
  type = 6;
  subType = "lsilogicsas";
  
  CimString cimString = new CimString();
  Map<QName, String> cimAttributes = cimString.getOtherAttributes();
  cimAttributes.put(new QName("http://www.vmware.com/vcloud/v1.5",
  "busSubType", "vcloud"), subType);
  cimAttributes.put(new QName("http://www.vmware.com/vcloud/v1.5",
  "busType", "vcloud"), String.valueOf(type));
  cimString.getOtherAttributes().putAll(cimAttributes);
  CimString setElementName = new CimString();
  setElementName.setValue(name);
  CimString setDescription = new CimString();
  setDescription.setValue(description);
  CimString setInstanceID = new CimString();
  setInstanceID.setValue("1000");
  ResourceType setResourceType = new ResourceType();
  setResourceType.setValue(String.valueOf(type));
  
  CimString setAddress = new CimString();
  setAddress.setValue(String.valueOf(address));
  
  RASDType diskItemType = new RASDType();
  diskItemType.setElementName(setElementName);
  diskItemType.setDescription(setDescription);
  diskItemType.setInstanceID(setInstanceID);
  diskItemType.setResourceType(setResourceType);
  diskItemType.setAddress(setAddress);
  diskItemType.getHostResource().add(cimString);
  

  The XML looks like this:

   <ns6:Item>
          <ns3:Address>0</ns3:Address>
          <ns3:Description>IDE Controller</ns3:Description>
          <ns3:ElementName>IDE Controller 0</ns3:ElementName>
              <ns3:InstanceID>1</ns3:InstanceID>
          <ns3:ResourceType>5</ns3:ResourceType>
      </ns6:Item>
      <ns6:Item>
          <ns3:Address>0</ns3:Address>
              <ns3:Description>SSCI Controller</ns3:Description>
          <ns3:ElementName>SSCI Controller</ns3:ElementName>
          <ns3:HostResource ns6:busSubType="lsilogicsas" ns6:busType="6"/>
          <ns3:InstanceID>1000</ns3:InstanceID>
          <ns3:ResourceType>6</ns3:ResourceType>
      </ns6:Item>
  
  

  Also, I get a success message:

  <Task xmlns="http://www.vmware.com/vcloud/v1.5" status="success" startTime="2011-11-08T21:14:32.401+01:00" operationName="vappUpdateVm" operation="Updated Virtual Machine Test Machine(6c99a693-fcfc-4424-afdb-cf5a9172447b)" expiryTime="2012-02-06T21:14:32.401+01:00" endTime="2011-11-08T21:14:32.635+01:00" name="task" id="urn:vcloud:task:ac59ce2a-fc3f-451e-891d-0a2e1ab54e7c" type="application/vnd.vmware.vcloud.task+xml" href="https://188.138.123.220/api/task/ac59ce2a-fc3f-451e-891d-0a2e1ab54e7c" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.vmware.com/vcloud/v1.5 http://172.30.34.220/api/v1.5/schema/master.xsd">
      <Owner type="application/vnd.vmware.vcloud.vm+xml" name="Test Machine" href="https://188.138.123.220/api/vApp/vm-6c99a693-fcfc-4424-afdb-cf5a9172447b"/>
      <User type="application/vnd.vmware.admin.user+xml" name="scriptuser" href="https://188.138.123.220/api/admin/user/8062b4a4-2aa5-4858-af62-b8bee8baa693"/>
      <Organization type="application/vnd.vmware.vcloud.org+xml" name="Demo" href="https://188.138.123.220/api/org/baca2a0b-d2be-4b6a-ad30-9268b9cdee23"/>
  </Task>
  
  

  The problem is take a look in the hardware section that I can't find the SCSI controller...

  Can someone help me?

  Hello

  Adding a type SCSI drive will add the SCSI controller for you.

  I don't think that you can add only a SCSI controller without any disk to it.

  Try to only add a SCSI (buslogic, free, lsilogicsas, VIrtualSCSI) disc that will add a SCSI controller for you.

          any name
         
          any id
          17
     

  Kind regards

  Rajesh Kamal.

• Type of SCSI controller and the driver for Win XP Pro

  Can anyone tell me please what SCSI type should I use for Windows XP Pro? Any SCSI controller I use, VSphere, ensures an error telling me that Win XP does not support the driver that uses VMware ESX to SCSI virtual devices - but it works very well.

  Any help is appreciated. TY

  This is the document that I always follow when creating XP workstations,

  http://www.VMware.com/files/PDF/XP_guide_vdi.PDF

  Note that you need the new version of the driver for new service packs.

  That said, like André request can you put a picture of your error.

  As a result, I'm moving this post to the guest OS of the forums section.

• Windows 2 k 3 lack of SCSI controller after running virtual machine converter

  Hello

  After you convert a Windows 2 k 3 server making the VM P2V is now lack a SCSI controller for the virtual machine cannot start.

  What is the best way to solve this problem? I need to copy the drivers from the physical server?

  Thanks in advance,

  PM

  If the disk controller type see you in the settings of the virtual machine is IDE, check out http://kb.vmware.com/kb/1016192.

  Another option is to choose the type of controller in the converter, when it comes to hardware.

  André

• be prompted to install the scsi controller during the creation of the new office or after recompose

  Hi, I use the lsi logic scsi Controller for my computer parallel virtual parent.  After you create the pool, choose my parent vm, etc... when I go to connect to the desktop computer I am asked to install the driver for the found new hardware wizard scsi controller.  dekstops has windows xp.  If I use the default controller it doesn't.  Thanks in advance for any ideas.  screenshot is attached.   Cheers.

  Maybe this thread will help you, http://communities.vmware.com/message/1691428 and also this KB, http://kb.vmware.com/kb/1031986.