[one-users] Add Volatile disk

Wed Aug 21 03:29:29 PDT 2013

Hi Michael,

Please try the DISK=[DEV_PREFIX="sd"] suggested in the other thread.

Best,

-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 13, 2013 at 10:22 PM, Michael Curran
<michael.curran at connectsolutions.com> wrote:
> I am going to need some help here –
>
>
>
> This is my vmdk of my newly created VM in esxi
>
>
>
> # Disk DescriptorFile
>
> version=1
>
> encoding="UTF-8"
>
> CID=f1e2794a
>
> parentCID=ffffffff
>
> isNativeSnapshot="no"
>
> createType="vmfs"
>
>
>
> # Extent description
>
> RW 104857600 VMFS "disk-flat.vmdk"
>
>
>
> # The Disk Data Base
>
> #DDB
>
>
>
> ddb.adapterType = "lsilogic"
>
> ddb.thinProvisioned = "1"
>
> ddb.geometry.sectors = "63"
>
> ddb.geometry.heads = "255"
>
> ddb.geometry.cylinders = "6527"
>
> ddb.uuid = "60 00 C2 9c 90 c8 f3 b6-e8 29 f5 b1 e9 06 1e fa"
>
> ddb.longContentID = "b9be76ceadf9b33d726bc7f9f1e2794a"
>
> ddb.deletable = "true"
>
> ddb.virtualHWVersion = "7"
>
> ddb.toolsVersion = "8300"
>
>
>
>
>
> Note that the ddb.adapterType is already set to lsilogic
>
>
>
> However when I log into vSphere, the disk is attached as IDE (0:0) and I
> have set image BUS and template devices as shown in the previous post about
> this
>
>
>
> Is there an option I am missing somewhere that is not creating the root
> drive as SCSI?
>
>
>
>
>
>
>
> Michael Curran | connectsolutions | Lead Network Architect
>
> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com
>
>
>
> From: Michael Curran
> Sent: Monday, August 12, 2013 4:08 PM
>
>
> To: Michael Curran; Nicolas Bélan; users at lists.opennebula.org
> Subject: RE: [one-users] Add Volatile disk
>
>
>
> I thought I found the issue – Tried the following
>
>
>
> In the oneimage I am using I added
>
>
>
> BUS=”SCSI”
>
>
>
> In the onetemplate I am using I added
>
>
>
> Under the DISK section of the template
>
> BUS="scsi"
>
> Under the RAW section of the tehmplate
>
> RAW=[
> DATA="<devices><controller type='scsi' index='0'
> model='lsilogic'/></devices>",
> TYPE="vmware" ]
>
> However I still do not get a SCSI boot disk or SCSI driver instantiated –
> anything I can add to this to help define why its coming up as an IDE root
> volume instead of SCSI ?? The original VM shows as SCSI.
>
>
>
>
>
>
>
> Michael Curran | connectsolutions | Lead Network Architect
>
> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com
>
>
>
> From: users-bounces at lists.opennebula.org
> [mailto:users-bounces at lists.opennebula.org] On Behalf Of Michael Curran
> Sent: Monday, August 12, 2013 3:05 PM
> To: Nicolas Bélan; users at lists.opennebula.org
> Subject: Re: [one-users] Add Volatile disk
>
>
>
> I think I found the issue – the disk is not attaching as SCSI – because
> there are no SCSI devices defined for use
>
>
>
> Going to go back and re-create the Template and make sure the disks are
> setup to use SCSI.
>
>
>
> Michael Curran | connectsolutions | Lead Network Architect
>
> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com
>
>
>
> From: Michael Curran
> Sent: Monday, August 12, 2013 1:32 PM
> To: Michael Curran; Nicolas Bélan; users at lists.opennebula.org
> Subject: RE: [one-users] Add Volatile disk
>
>
>
> More details now –
>
>
>
> So, in Sunstone GUI I see an ID 2 for my volatile disk
>
>
>
> When I add it as raw, I don’t see it use
> /var/lib/one/remotes/vmm/attach_disk – just creates a raw disk and is done
> (nothing exists in the volumes)
>
>
>
> It does not appear to use vim-cmd when it creates --
>
>
>
> When I try to detach the the disk it does this
>
>
>
> Mon Aug 12 08:24:38 2013 [VMM][I]: Successfully execute virtualization
> driver operation: attach_disk.
> Mon Aug 12 08:24:38 2013 [VMM][I]: VM Disk successfully attached.
> Mon Aug 12 08:28:59 2013 [VMM][I]: VM successfully rebooted.
> Mon Aug 12 10:20:14 2013 [VMM][I]: Command execution fail:
> /var/tmp/one/vmm/vmware/detach_disk 'one-2' '/vmfs/volumes/102/2/disk.2'
> 'hdc' '2' 2 10.7.0.55
> Mon Aug 12 10:20:14 2013 [VMM][E]: : Command " vim-cmd
> vmsvc/device.diskremove 20 0 2 /vmfs/volumes/102/2/disk.2" failed: Failed to
> find a controller with the specified bus number.
> Mon Aug 12 10:20:14 2013 [VMM][E]: Could not detach from one-2
> Mon Aug 12 10:20:14 2013 [VMM][I]: ExitCode: 255
> Mon Aug 12 10:20:14 2013 [VMM][I]: Failed to execute virtualization driver
> operation: detach_disk.
> Mon Aug 12 10:20:14 2013 [VMM][E]: Error detaching VM Disk: Could not detach
> from one-2
>
>
>
> Michael Curran | connectsolutions | Lead Network Architect
>
> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com
>
>
>
> From: users-bounces at lists.opennebula.org
> [mailto:users-bounces at lists.opennebula.org] On Behalf Of Michael Curran
> Sent: Monday, August 12, 2013 12:16 PM
> To: Nicolas Bélan; users at lists.opennebula.org
> Subject: Re: [one-users] Add Volatile disk
>
>
>
> Thanks Nicolas ---
>
>
>
> But you cannot install packages into VMware ESXi , and I did add it as a raw
> disk – it does attach it to the instance from the console, when I look in
> the instance directory I do not see an extra vmdk file
>
>
>
> Also looking at the edit settings in Vmware – I don’t see an additional SCSI
> disk
>
>
>
> Michael Curran | connectsolutions | Lead Network Architect
>
> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com
>
>
>
> From: users-bounces at lists.opennebula.org
> [mailto:users-bounces at lists.opennebula.org] On Behalf Of Nicolas Bélan
> Sent: Monday, August 12, 2013 11:24 AM
> To: users at lists.opennebula.org
> Subject: Re: [one-users] Add Volatile disk
>
>
>
> Hello,
>
> mkfs.ntfs is provided by ntfs-3g package on most linux.
> You should install it and retry I think
> Or perhaps (not tested by myselft) use a raw disk and format it inside your
> windows. I never installed windows on opennebula, I can not give you more
> advice.
>
> Best regards
> Nicolas
>
> Le 12/08/13 16:45, Michael Curran a écrit :
>
> I need to add a raw disk to be used with a windows VM – and this is the
> error message I get in the logs for the VM
>
>
>
> Mon Aug 12 07:09:53 2013 [VMM][E]: mkimage: Command "export
> PATH=/usr/sbin:/sbin:$PATH
> Mon Aug 12 07:09:53 2013 [VMM][I]:
> Mon Aug 12 07:09:53 2013 [VMM][I]: if [ ! -d /vmfs/volumes/102/2/disk.2 ];
> then
> Mon Aug 12 07:09:53 2013 [VMM][I]: mkdir -p /vmfs/volumes/102/2/disk.2
> Mon Aug 12 07:09:53 2013 [VMM][I]: fi
> Mon Aug 12 07:09:53 2013 [VMM][I]:
> Mon Aug 12 07:09:53 2013 [VMM][I]: mkfs -t NTFS /vmfs/volumes/102/2/disk.2"
> failed: sh: mkfs: not found
> Mon Aug 12 07:09:53 2013 [VMM][E]: Could not create image
> /vmfs/volumes/102/2/disk.2
> Mon Aug 12 07:09:53 2013 [VMM][I]: ExitCode: 127
> Mon Aug 12 07:09:53 2013 [VMM][I]: Failed to execute transfer manager driver
> operation: tm_attach.
> Mon Aug 12 07:09:53 2013 [VMM][E]: Error attaching new VM Disk: Could not
> create image /vmfs/volumes/102/2/disk.2
>
>
>
> This is trying to use mkfs to create a NTFS volume, when you cannot do
> anything with VMware except attach a raw disk, there are no mkfs tools that
> will build and attach it as a NTFS volume
>
>
>
> When I look up how to add a disk via ESXi command-line this is what I find
> ---- which is a completely different command than shown
>
>
>
> It says add a disk to VM 16 that is 10g in size as SCSI device 0:2 using
> datastore1
>
>
>
> vim-cmd vmsvc/device.diskadd 16 10000 scsi0 2 datastore1
>
>
>
> The unique thing is though, that I cannot run that as oneadmin, because it
> fails – which means I cannot add a disk to the VM
>
>
>
> # vim-cmd vmsvc/device.diskadd 20 15000 scsi 0 1 102
>
> Reconfigure failed
>
>
>
> And if I try to add the disk via vSphere , it cannot really add it because
> the disk currently in use is technically SCSI0:0 , but vSphere is still
> expecting SCSI0:0 as the next disk.
>
>
>
> Does this sound like a bug, if so I can create a bug report on this instead.
>
>
>
> 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
>