[one-users] vmware and scsi disk setup

[Michael Curran]

Uniquely enough if I look at the VMDK driver ddb.adapterType , they both state lsilogic 

The VMX file is being created using the lsilogic definition by opennebula. So there must be something different being done by VMware -- I will try to set the following in data_vmx and see if that will work

scsi0.virtualDev = "lsisas1068"

Michael Curran | connectsolutions | Lead Network Architect
Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com

-----Original Message-----
From: Tino Vazquez [mailto:cvazquez at c12g.com] 
Sent: Thursday, August 22, 2013 5:05 AM
To: Michael Curran
Cc: users at lists.opennebula.org
Subject: Re: [one-users] vmware and scsi disk setup

Hi Michael,

At first sight, it looks like the first .vmx refers to a VM with a SCSI SAS disk, while the second uses a LSI logic driver for it. Does changing the second VM to use a lsisas driver work?

Regards,

-Tino
--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure Architect at C12G Labs www.c12g.com | @C12G | es.linkedin.com/in/tinova

--
Confidentiality Warning: The information contained in this e-mail and any accompanying documents, unless otherwise expressly indicated, is confidential and privileged, and is intended solely for the person and/or entity to whom it is addressed (i.e. those identified in the "To" and "cc" box). They are the property of C12G Labs S.L..
Unauthorized distribution, review, use, disclosure, or copying of this communication, or any part thereof, is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify us immediately by e-mail at abuse at c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation.


On Wed, Aug 21, 2013 at 7:21 PM, Michael Curran <michael.curran at connectsolutions.com> wrote:
> So -- the issue is I have a windows VM in ESXi that is currently 
> installed and runs fine with SCSI disks set -- but when I deploy it 
> with OpenNebula , windows boots in recovery mode because of a 
> suspected change in hardware
>
> This is scsi is identified in the VMX file, by VMWare
>
> scsi0.present = "true"
> scsi0.sharedBus = "none"
> scsi0.virtualDev = "lsisas1068"
> scsi0:0.present = "true"
> scsi0:0.fileName = "Vanilla-w2k8r2.vmdk"
> scsi0:0.deviceType = "scsi-hardDisk"
> sched.scsi0:0.shares = "normal"
> sched.scsi0:0.throughputCap = "off"
> scsi0:0.redo = ""
> scsi0.pciSlotNumber = "160"
> scsi0.sasWWID = "50 05 05 66 41 49 80 90"
>
>
> This is how the SCSI device is created in VMX, by OpenNebula (not sure 
> why it creates the VM with a snapshot diskname, and not just 
> disk.vmdk)
>
> scsi0.present = "true"
> scsi0.virtualDev = "lsilogic"
> scsi0:0.present = "true"
> scsi0:0.deviceType = "scsi-hardDisk"
> scsi0:0.fileName = "disk-000001.vmdk"
> scsi0.pciSlotNumber = "-1"
> scsi0:0.redo = ""
>
> There appears to be several fields missing
>
> Michael Curran | connectsolutions | Lead Network Architect Phone 
> 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com
>
> -----Original Message-----
> From: Tino Vazquez [mailto:cvazquez at c12g.com]
> Sent: Wednesday, August 21, 2013 6:28 AM
> To: Michael Curran
> Cc: users at lists.opennebula.org
> Subject: Re: [one-users] vmware and scsi disk setup
>
> Hi Michael,
>
> The SCSI configuration of a disk is better left our to OpenNebula, rather than setting it manually. Could you try setting a disk like:
>
> DISK=[IMAGE_ID="0", DEV_PREFIX="sd"]
>
> and remove the DATA_VMX field altogether (although keeping the DATA field)?
>
> Best regards,
>
> -Tino
> --
> Constantino Vázquez Blanco, PhD, MSc
> Senior Infrastructure Architect at C12G Labs www.c12g.com | @C12G | 
> es.linkedin.com/in/tinova
>
> --
> Confidentiality Warning: The information contained in this e-mail and any accompanying documents, unless otherwise expressly indicated, is confidential and privileged, and is intended solely for the person and/or entity to whom it is addressed (i.e. those identified in the "To" and "cc" box). They are the property of C12G Labs S.L..
> Unauthorized distribution, review, use, disclosure, or copying of this communication, or any part thereof, is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify us immediately by e-mail at abuse at c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation.
>
>
> On Tue, Aug 20, 2013 at 6:54 PM, Michael Curran <michael.curran at connectsolutions.com> wrote:
>> I am trying to get my windows hosts to deploy with SCSI devices 
>> instead of IDE
>>
>>
>>
>> I have modified the disk type to be SD instead of HD - and it starts 
>> up with SCSI now , however I don't think its building the VMX file 
>> correctly as I get this error
>>
>>
>>
>> Tue Aug 20 09:44:08 2013 [VMM][I]: out:
>>
>> Tue Aug 20 09:44:08 2013 [VMM][I]: error: Failed to start domain
>> one-24
>>
>> Tue Aug 20 09:44:08 2013 [VMM][I]: error: internal error Could not 
>> start
>> domain: GenericVmConfigFault -
>>
>> Tue Aug 20 09:44:08 2013 [VMM][I]: Failed to configure scsi0.
>>
>> Tue Aug 20 09:44:08 2013 [VMM][I]:
>>
>> Tue Aug 20 09:44:08 2013 [VMM][I]:
>>
>> Tue Aug 20 09:44:08 2013 [VMM][I]: ExitCode: 1
>>
>> Tue Aug 20 09:44:08 2013 [VMM][I]: Failed to execute virtualization 
>> driver
>> operation: deploy.
>>
>> Tue Aug 20 09:44:08 2013 [VMM][E]: Error deploying virtual machine
>>
>> Tue Aug 20 09:44:08 2013 [DiM][I]: New VM state is FAILED
>>
>>
>>
>>
>>
>> I have tried setting the RAW settings for SCSI env. In the VMX file, 
>> but it puts the disk name before it finds if the SCSI device is present.
>>
>>
>>
>> scsi0:0.fileName =
>> "/vmfs/volumes/51ff8fa7-5a076f91-1cb4-b499bac14752/24/disk.0/disk.vmdk"
>>
>> scsi0.present = "true"
>>
>> scsi0.sharedBus = "none"
>>
>> scsi0.virtualDev = "lsisas1068"
>>
>> scsi0:0.present = "true "
>>
>> scsi0:0.deviceType = "scsi-hardDisk"
>>
>> sched.scsi0:0.shares = "normal"
>>
>> sched.scsi0:0.throughputCap = "off"
>>
>> scsi0.pciSlotNumber = "21"
>>
>> scsi0.sasWWID = "50 05 05 60 ed 9f 4c 80"
>>
>>
>>
>> Are there any recommended best practices for this type of setup? Here 
>> is what my template looks like
>>
>>
>>
>> TEMPLATE 0 INFORMATION
>>
>> ID             : 0
>>
>> NAME           : Windows 2k8r2
>>
>> USER           : oneadmin
>>
>> GROUP          : oneadmin
>>
>> REGISTER TIME  : 08/08 12:16:50
>>
>>
>>
>> PERMISSIONS
>>
>> OWNER          : um-
>>
>> GROUP          : ---
>>
>> OTHER          : ---
>>
>>
>>
>> TEMPLATE CONTENTS
>>
>> CONTEXT=[
>>
>>   NETWORK="YES" ]
>>
>> CPU="1"
>>
>> DISK=[
>>
>>   IMAGE_ID="0" ]
>>
>> FEATURES=[
>>
>>   PCIBRIDGE="0" ]
>>
>> MEMORY="2048"
>>
>> NIC=[
>>
>>   MODEL="e1000",
>>
>>   NETWORK_ID="0" ]
>>
>> OS=[
>>
>>   GUESTOS="windows7Server64Guest" ]
>>
>> RAW=[
>>
>>   DATA="<devices><controller type='scsi' index='0'
>> model='lsilogic'/></devices>",
>>
>>   TYPE="vmware" ]
>>
>> RAW=[
>>
>>   DATA_VMX="scsi0.present = \"true\"\nscsi0.sharedBus = 
>> \"none\"\nscsi0.virtualDev = \"lsisas1068\"\nscsi0:0.present = \"true 
>> \"\nscsi0:0.deviceType = \"scsi-hardDisk\"\nsched.scsi0:0.shares = 
>> \"normal\"\nsched.scsi0:0.throughputCap = 
>> \"off\"\nscsi0.pciSlotNumber = \"160\"",
>>
>>   TYPE="vmware" ]
>>
>> REQUIREMENTS="ID=\"0\" | ID=\"1\""
>>
>>
>>
>>
>>
>>
>>
>> Michael Curran | connectsolutions | Lead Network Architect
>>
>> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org