Simulator Discussions

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

Thanks Bob - although I haven't completed the cluster setup yet, I'd say you were spot on. I'd failed to pay sufficient notice to the network type which was desktop rather than server variant, having logged in to the systemshell it became obvious there were no adapters other than localhost, and under the hood of just logging in as admin there were various rpc failures which should have pointed me in this direction. As should the "allow system to boot without network adapters on AMD64" messages.

The desktop style adapters work with the 8.1.1 vsim image, but as far as I can tell no later ones.

Thanks for your help - much apreciated

Cheers

Julian

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

This instructions worked as stated. Nice job !


@bobshouseofcards wrote:

There have been a small number of posts both here and in the support community about the change between the 7.3 family of OnTap simulators and those for 8.1.1.  The delivery model changed from being one where you install the simulator on a Linux system (easily setup on any virtualization platform you have) to the model in 8.1.1 Simulator where you download a full virtual machine image designed for use in a VMWare environment only.

 

Many people will have access to one of the paid options (VMWare Workstation/Fusions/ESX) or can use the free VMWare Player on Windows.  But, for those that need alternatives such as on a Linux or Solaris host platform or something free on a Mac, here are instructions to setup 8.1.1 Simulator on VirtualBox.

 

Disclaimer:  to date I have only tested this on a single Windows platform.  Specifically, I tested this on a 32 bit Windows 7 host (but on 64 bit capable hardware).  Basic setup and general operations seem normally functional, though I have not delved into all the possibilities that OnTap offers.  The 7-mode simulator is the one on which I did most checkouts since this is what I need to make available to other team members where I work.  I have done minimal setup only on cluster mode.  None of this is technically supported by NetApp, and your mileage may vary.

 

Test environment:  Dell laptop, 3GB RAM running Windows 7 SP1 32 bit; VirtualBox 4.2.4r81684; Simulate OnTap 8.1.1.  As per the VirtualBox documentation,  you will need a 64 bit processor with virtualization enhancements enabled even if the host OS is 32 bit.

 

Setup (assumes basic familiarity with VirtualBox)

 

1.  Download and install VirtualBox.  I just used defaults for setup.

 

2.  Download the 8.1.1 simulator.  Extract the files somewhere that you want them to be.

 

3.  Create a new Virtual Machine with OS type BSD, version FreeBSD (64 bit).  Memory required is 1600MB.  Don't select a virtual hard drive now, we need to select a bunch later.  Save the new machine.

 

4.  Open the Settings for the new VM.  On the System page, Processor tab, set CPU to 2

 

5.  On the Storage path, delete the CDROM from the IDE controller.  Then, add 4 virtual hard disks to the controller.  For each disk, you will choose an existing disk.  The disks you will add, in order, are "DataONTAP.vmdk", "DataONTAP-var.vmdk", "DataONTAP-nvram.vmdk", and "DataONTAP-sim.vmdk".  Finally, add a Floppy controller with a single, empty floppy drive.  When complete, the storage setup for your new virtual machine should look like:

 

6.  On the audio page, uncheck "Enable Audio".

 

7.  On the network page, you can add up to 4 network adapters in any style that you choose - host only, bridged, internal, NAT.  This provides a bit more choice than available through VMWare Player.  Having some NICs of each type certainly can setup some interesting possibilities for multiple simulators.  For each NIC you add, expand the "Advanced" section for the NIC and select "Intel PRO/1000 MT Server (82545EM)" as the adapter type.  The Simulator virtual machine only has drivers for this emulated NIC type.  A sample NIC setup would look like:

 

8.  The default setup of the VMWare virtual machine attaches a local Windows pipe as a conduit to each of two serial ports - one for the "console" and one for debugging.  You can enable serial ports and redirect, but it is not required.

 

9.  On the USB page, uncheck "Enable USB Controller".

 

10.  On the Shared Folders page, no shared folders need be created.

 

11.  Save the virtual machine.

 

12.  Be sure you have 1600MB real free memory to start the guest or it will fail during startup at some point.

 

13.  Start the virtual machine.

 

14.  During the 10 second countdown, click in the VM and press any key that is NOT Enter to stop the boot.

 

15.  Update the environment to not start the VMWare tools with command "setenv bootarg.vm.run_vmtools false"

 

16.  If you are installing a 2nd simulator this is a great time to update the serial number as per the documentation as well.

 

17.  Enter command "boot" to continue with the startup of Data OnTAP.

 

18.  When the "Press Cntrl-C for menu" appears, press Cntrl-C and wait for the boot menu.  This first boot can take a little bit to happen depending on your hosting platform.

 

19.  On the boot menu, select option 4 and confirm clearing all disks and deleting all data.

 

20.  The Simulator will restart - let it proceed normally.  After restoring a fresh Data OnTAP from the simulated media you will eventually get the prompts for standard setup of a new Filer.

 

Enjoy!


 

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

Just used these instructions to set up an ONTAP 8.2 simulator on VirtualBox 9 and it worked perfectly.  Thanks for the great proecedural notes!

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

Step 15. You are not clear as to where to enter this option. You did not explain that option at all.

I believe you mean to say open the env file located vsim_netapp-cm\cfcard\env. Below is an example where I installed

my files: 

 

C:\Users\pbruce\Documents\Vendors\NetApp\Software\Simulator\vsim_netapp-cm\cfcard\env directory and 

 

I also am running into the boot no boot issue. What wrong is supposed to be able to put a ? to see list of command available

and it does not seem to work.

 

For those of you having issues finding the files. This is where I put mine and you can see all the files are there.

 

Directory of C:\Users\pbruce\Documents\Vendors\NetApp\Software\Simulator\vsim_netapp-cm

11/17/2014 05:51 AM 2,037,383,168 DataONTAP-flat.vmdk
11/17/2014 05:51 AM 5,101,322,240 DataONTAP-nvram-flat.vmdk
02/12/2015 10:05 PM 745 DataONTAP-nvram.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s001.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s002.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s003.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s004.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s005.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s006.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s007.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s008.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s009.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s010.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s011.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s012.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s013.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s014.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s015.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s016.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s017.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s018.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s019.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s020.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s021.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s022.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s023.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s024.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s025.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s026.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s027.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s028.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s029.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s030.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s031.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s032.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s033.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s034.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s035.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s036.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s037.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s038.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s039.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s040.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s041.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s042.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s043.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s044.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s045.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s046.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s047.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s048.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s049.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s050.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s051.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s052.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s053.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s054.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s055.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s056.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s057.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s058.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s059.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s060.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s061.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s062.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s063.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s064.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s065.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s066.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s067.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s068.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s069.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s070.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s071.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s072.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s073.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s074.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s075.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s076.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s077.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s078.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s079.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s080.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s081.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s082.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s083.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s084.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s085.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s086.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s087.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s088.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s089.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s090.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s091.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s092.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s093.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s094.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s095.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s096.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s097.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s098.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s099.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s100.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s101.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s102.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s103.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s104.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s105.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s106.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s107.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s108.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s109.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s110.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s111.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s112.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s113.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s114.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s115.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s116.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s117.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s118.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s119.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s120.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s121.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s122.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s123.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s124.vmdk
02/15/2015 10:08 AM 327,680 DataONTAP-s125.vmdk
02/15/2015 10:08 AM 65,536 DataONTAP-s126.vmdk
02/12/2015 10:05 PM 5,656 DataONTAP-sim.vmdk
11/17/2014 05:51 AM 1,616,904,192 DataONTAP-var-flat.vmdk
02/12/2015 10:05 PM 743 DataONTAP-var.vmdk
02/12/2015 10:05 PM 739 DataONTAP.vmdk
133 File(s) 8,796,643,019 bytes
0 Dir(s) 356,529,795,072 bytes free

 

The person who wrote the guys should had paid a littel attention to detail. While good for the most part we seem to be missing something else.

I like to get past the boot issue.

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

Found that adding the floopy with empty data solved the issue so far.

 

Still not setting up.

Re: Simulate ONTAP 8.1.1 withVirtualBox

Hi,

 

I did the whole thing more then ones with 8.3 and 8.2.

The problem I encounter is that at the end it can't find setup due by a missing mboot disk.

 

Regards

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

Yes, it's always the same thing......RTFM.

I used the wrong NIC , the standard one mt 1000 desktop instead of server.

 

boot disk is found now, setup is running.

 

Regards

Chiel

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

Has anyone been able to get 8.3.2RC1 to run in VirtualBox?

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

Sure.  Took a slightly different approach.  I fixed the ovf so it would import correctly and added the floppy device to the ovf xml.  Then I just imported the appliance, connected the nics to the appropriate networks and started it up.

 

I did have some trouble getting past a memory related panic at start up.  There is no apparent way to control the placement of the PCI hole, so it took some experimentation to find ram sizing that would work.  5gb did not work, 6gb did work.  4gb did not, 3gb did.  I settled on 3560MB, and updated my ovf to make that the default on future imports.

 

 

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

I've been experimenting with writing OVF descriptors for the various vsims, and the results are encouraging.  With an appropriate OVF descriptor added to the TGZ archives they import cleanly into virtualbox, fusion, and workstation.  Virtualbox on windows seems to be the exception.  It can't deal with compressed vmdks at all, and even when it imports the vmdks it leaves them disconnected from the IDE controller.  In windows it will import, but you have to go back and re-attach the hard drives.

 

Here is a sample ovf envelope.  It plays a little lose with the dmtf spec, and I had to make some educated guesses on the ovf:format values, but it seems to work accross the various 8.2.x archives.  Just extract the vsim tgz file, drop this in along side all the .vmdk files, and import it into virtual box.  

 

vsim-82x.ovf

 

<?xml version="1.0" encoding="UTF-8"?>
<!--Hand crafted ovf descriptor for the vsim tgz archives for use in virtualbox-->
<Envelope vmw:buildId="build-166674" xmlns="http://schemas.dmtf.org/ovf/envelope/1" xmlns:cim="http://schemas.dmtf.org/wbem/wscim/1/common" xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1" xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData" xmlns:vmw="http://www.vmware.com/schema/ovf" xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <References>
    <File ovf:href="DataONTAP.vmdk" ovf:id="file1"/>
    <File ovf:href="DataONTAP-var.vmdk" ovf:id="file2"/>
    <File ovf:href="DataONTAP-nvram.vmdk" ovf:id="file3"/>
    <File ovf:href="DataONTAP-sim.vmdk" ovf:id="file4"/>
  </References>
  <DiskSection>
    <Info>Virtual disk information</Info>
    <Disk ovf:capacity="1943" ovf:capacityAllocationUnits="byte * 2^20" ovf:diskId="vmdisk1" ovf:fileRef="file1" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#thick"/>
    <Disk ovf:capacity="1542" ovf:capacityAllocationUnits="byte * 2^20" ovf:diskId="vmdisk2" ovf:fileRef="file2" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#thick"/>
    <Disk ovf:capacity="5122" ovf:capacityAllocationUnits="byte * 2^20" ovf:diskId="vmdisk3" ovf:fileRef="file3" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#thick"/>
    <Disk ovf:capacity="250"  ovf:capacityAllocationUnits="byte * 2^30" ovf:diskId="vmdisk4" ovf:fileRef="file4" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#twoGbMaxExtentSparse"/>
  </DiskSection>
  <NetworkSection>
    <Info>The list of logical networks</Info>
    <Network ovf:name="hostonly">
      <Description>The hostonly network</Description>
    </Network>
    <Network ovf:name="nat">
      <Description>The nat network</Description>
    </Network>
  </NetworkSection>
  <VirtualSystem ovf:id="vsim_netapp-DOT8.2.x">
    <Info>A virtual machine</Info>
    <Name>vsim_netapp-DOT8.2.x</Name>
    <OperatingSystemSection ovf:id="78" vmw:osType="freebsd64Guest">
      <Info>The kind of installed guest operating system</Info>
    </OperatingSystemSection>
    <VirtualHardwareSection>
      <Info>Virtual hardware requirements</Info>
      <System>
        <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>
        <vssd:InstanceID>0</vssd:InstanceID>
        <vssd:VirtualSystemIdentifier>vsim_netapp-DOT8.2.x</vssd:VirtualSystemIdentifier>
        <vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType>
      </System>
      <Item>
        <rasd:AllocationUnits>hertz * 10^6</rasd:AllocationUnits>
        <rasd:Description>Number of Virtual CPUs</rasd:Description>
        <rasd:ElementName>2 virtual CPU(s)</rasd:ElementName>
        <rasd:InstanceID>1</rasd:InstanceID>
        <rasd:ResourceType>3</rasd:ResourceType>
        <rasd:VirtualQuantity>2</rasd:VirtualQuantity>
      </Item>
      <Item>
        <rasd:AllocationUnits>byte * 2^20</rasd:AllocationUnits>
        <rasd:Description>Memory Size</rasd:Description>
        <rasd:ElementName>1600MB of memory</rasd:ElementName>
        <rasd:InstanceID>2</rasd:InstanceID>
        <rasd:ResourceType>4</rasd:ResourceType>
        <rasd:VirtualQuantity>1600</rasd:VirtualQuantity>
      </Item>
      <Item>
        <rasd:Address>0</rasd:Address>
        <rasd:Description>IDE Controller</rasd:Description>
        <rasd:ElementName>ideController0</rasd:ElementName>
        <rasd:InstanceID>3</rasd:InstanceID>
        <rasd:ResourceType>5</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:Address>1</rasd:Address>
        <rasd:Description>IDE Controller</rasd:Description>
        <rasd:ElementName>ideController1</rasd:ElementName>
        <rasd:InstanceID>4</rasd:InstanceID>
        <rasd:ResourceType>5</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>0</rasd:AddressOnParent>
        <rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>
        <rasd:Caption>floppy0</rasd:Caption>
        <rasd:Description>Floppy Drive</rasd:Description>
        <rasd:ElementName>floppy0</rasd:ElementName>
        <rasd:InstanceID>5</rasd:InstanceID>
        <rasd:ResourceType>14</rasd:ResourceType>
      </Item>
        <Item>
        <rasd:AddressOnParent>0</rasd:AddressOnParent>
        <rasd:ElementName>disk1</rasd:ElementName>
        <rasd:HostResource>/disk/vmdisk1</rasd:HostResource>
        <rasd:InstanceID>6</rasd:InstanceID>
        <rasd:Parent>3</rasd:Parent>
        <rasd:ResourceType>17</rasd:ResourceType>
      </Item>    
      <Item>
        <rasd:AddressOnParent>1</rasd:AddressOnParent>
        <rasd:ElementName>disk2</rasd:ElementName>
        <rasd:HostResource>/disk/vmdisk2</rasd:HostResource>
        <rasd:InstanceID>7</rasd:InstanceID>
        <rasd:Parent>3</rasd:Parent>
        <rasd:ResourceType>17</rasd:ResourceType>
      </Item>    
       <Item>
        <rasd:AddressOnParent>0</rasd:AddressOnParent>
        <rasd:ElementName>disk3</rasd:ElementName>
        <rasd:HostResource>/disk/vmdisk3</rasd:HostResource>
        <rasd:InstanceID>8</rasd:InstanceID>
        <rasd:Parent>4</rasd:Parent>
        <rasd:ResourceType>17</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>1</rasd:AddressOnParent>
        <rasd:ElementName>disk4</rasd:ElementName>
        <rasd:HostResource>/disk/vmdisk4</rasd:HostResource>
        <rasd:InstanceID>9</rasd:InstanceID>
        <rasd:Parent>4</rasd:Parent>
        <rasd:ResourceType>17</rasd:ResourceType>
      </Item>  
      <Item>
        <rasd:AddressOnParent>1</rasd:AddressOnParent>
        <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
        <rasd:Connection>hostonly</rasd:Connection>
        <rasd:Description>E1000 ethernet adapter on &quot;hostonly&quot;</rasd:Description>
        <rasd:ElementName>ethernet0</rasd:ElementName>
        <rasd:InstanceID>10</rasd:InstanceID>
        <rasd:ResourceSubType>E1000</rasd:ResourceSubType>
        <rasd:ResourceType>10</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>2</rasd:AddressOnParent>
        <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
        <rasd:Connection>hostonly</rasd:Connection>
        <rasd:Description>E1000 ethernet adapter on &quot;hostonly&quot;</rasd:Description>
        <rasd:ElementName>ethernet1</rasd:ElementName>
        <rasd:InstanceID>11</rasd:InstanceID>
        <rasd:ResourceSubType>E1000</rasd:ResourceSubType>
        <rasd:ResourceType>10</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>3</rasd:AddressOnParent>
        <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
        <rasd:Connection>nat</rasd:Connection>
        <rasd:Description>E1000 ethernet adapter on &quot;nat&quot;</rasd:Description>
        <rasd:ElementName>ethernet2</rasd:ElementName>
        <rasd:InstanceID>12</rasd:InstanceID>
        <rasd:ResourceSubType>E1000</rasd:ResourceSubType>
        <rasd:ResourceType>10</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>4</rasd:AddressOnParent>
        <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
        <rasd:Connection>nat</rasd:Connection>
        <rasd:Description>E1000 ethernet adapter on &quot;nat&quot;</rasd:Description>
        <rasd:ElementName>ethernet3</rasd:ElementName>
        <rasd:InstanceID>13</rasd:InstanceID>
        <rasd:ResourceSubType>E1000</rasd:ResourceSubType>
        <rasd:ResourceType>10</rasd:ResourceType>
      </Item>
    </VirtualHardwareSection>
  </VirtualSystem>
</Envelope>                                                                                                                  

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

Missed your post. 

 

So, following your instructoins, I got the OVF file imported, and hit the error you mentioned:

 

2016-01-25_17-57-19.png

 

 

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

VIrtualbox seems to have difficulty constructing a VM from an OVF if the elements are not presented in a certain order.  All I did was re-order the item elements, for example so ide controller 0 comes before ide controller 1, and the disks connect in order, etc.  The ovf I posted above also has vmdk names, etc, that match what is included in the vsim tgz archives.  The vsim OVA archives have different filenames/elements needed to connect the disks but re-ordering was the key to get it to import.  The InstanceID fields need to be reordered as well as the order the items appear in the xml.   

 

For more than you ever wanted to know about ovf and ova, you can read the standard:
https://www.dmtf.org/standards/ovf

 

The various implementations seem to each have their own idiosyncrasies.  Virtualbox is sensitive to ordering, microsoft can't cope with vmdk files... its all part of the fun.

 

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

Wait, is the ordering in the VMDK files or in the virtual storage itself? I'm totally new to NetApp, so I'm not sure what's what.

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

This isn't really NetApp specific, its how virtualbox parses the ovf format in their implementation of the standard.

 

Inside an OVA file (which is a tar with specific constraints), you'll find the ovf, the vmdk file, a manifest file (for checksum validation), and sometimes other elements.  The ovf is an xml-like standards based way tof defining the virtual machine.  The intent of the standard is to allow VMs to be interchanged between virtualization platforms,  In practice there are a lot of rough edges.  

 

Inside the TGZ archives you'll find when you download the older simulator releases, you'll find the vmdk files, and a vmx file (among others).  These are virtual machines in a format native to VMware.  Adding an ovf to this file set just facilitates importing them into virtualbox, as a less error prone alternative to hand crafting a new vm in virtualbox and attaching the virtual disks.

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Highlighted

Re: Simulate ONTAP 8.1.1 withVirtualBox

From your screenshot it looks like you imported successfully.  Now you just need to ctrl-c at the boot menu during the next reboot and pick option 4 to install Data ONTAP.

 

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Try the NEW Knowledgebase!
NetApp KB Site
Forums