Simulate ONTAP 8.3.1 with mounting /cfcard and panic

[Tonica]

Hello,

It is my first time installing the Simulate ONTAP.  I was able to get the virtual box running but when ONTAP booting up, it keep panic with below error.

Any help will be much appreciated. 

[SeanHatfield]

Reboot it and stop at the VLOADER prompt.  Then run lsdev and make sure the disk layout matches this output:

VLOADER> lsdev
cd devices:
disk devices:
    disk0:   BIOS drive A:
    disk1:   BIOS drive C:
      disk1s2: FAT-16
    disk2:   BIOS drive D:
      disk2s1: FFS  bad disklabel
      disk2s2: FFS  bad disklabel
    disk3:   BIOS drive E:
      disk3s1: FFS  bad disklabel
      disk3s2: FFS  bad disklabel
    disk4:   BIOS drive F:
      disk4s1: FFS  bad disklabel
pxe devices:
VLOADER> 

Specifically, you want to verify the FAT-16 volume is detected as disk1s2.

[nitish]

make sure your virtual machine includes a "floppy" controller with a single "empty" drive

You can visit below URL to see all steps followed while setting up a 8.3 simulator in VirtualBox

NetApp 8.3 Simulator in VirtualBox

[Tonica]

I see FAT-16 is there.  Is there anything else I should check to make it work?

[Tonica]

I followed that instruction to the letter but I still get the same error.

Here is my configuration.

[SeanHatfield]

ah, 5gb ram may be the problem.  While that works on vmware, it doesn't on vbox.  Either bump it to 6 or drop it to 3.

[Tonica]

I tried both 3GB and it did not work so I tried 6GB and still not working.

Here some more error before the mounting.  I checked out the log on Vbox and it reported LUN#0 disk write error.

Have you see that before?

:00:03.747172 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0002

00:00:03.747592 VMMDev: Guest Log: BIOS: Booting from Hard Disk...

00:00:06.728910 VMMDev: Guest Log: BIOS: int13_diskette_function: unsupported AH=41

00:00:22.366597 PIT: mode=2 count=0x2e9c (11932) - 99.99 Hz (ch=0)

00:00:24.216578 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0xc4 (-1 usec ago) CmdIf1=0xec (-1 usec ago)

00:00:24.226660 PIIX3 ATA: Ctl#0: finished processing RESET

00:00:24.327024 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=1 CmdIf0=0xec (-1 usec ago) CmdIf1=0xec (-1 usec ago)

00:00:24.337089 PIIX3 ATA: Ctl#1: finished processing RESET

00:00:26.885535 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)

00:00:26.956961 PIIX3 ATA: LUN#0: disk write error (rc=VERR_INVALID_PARAMETER iSector=0x103e1 cSectors=0x8)

00:00:26.960788 PIIX3 ATA: LUN#0: disk write error (rc=VERR_INVALID_PARAMETER iSector=0x103e1 cSectors=0x8)

00:00:26.962993 PIIX3 ATA: LUN#0: disk write error (rc=VERR_INVALID_PARAMETER iSector=0x103e1 cSectors=0x8)

[SeanHatfield]

So a few questions:

What is the host OS?

What version of virtual box?

Which method did you use to create the VM?

In my case, its OSX, vbox 5.0.16 r105871, and I use the ovf import method.

On mine, the IDE controllers are type PIIX4.  From your log output yours are type PIIX3. That may or may not be relevant.  The logs imply a problem writing to the virtual disk.

[Tonica]

My host is OS X El Capitan

Virtual Box is version 5.0.14 r105127

I just created the new virtual server with option you have on your output.

For the drives, I uncompressed with gunzip and point the storage to it.

I alos tried to import but I got "NS_ERROR_CALL FAILED" when it try to mount the disk1.

Thank you Sean for helping me with it.

[SeanHatfield]

Try using the ovf import method.  I posted a sample ovf file in this thread. Over here. The 832 version shoould work for 831.  If not post back and I'll paste in the one from my 831 ovf.

[Tonica · Accepted solution]

Thank you Sean for take the time to answer my questions.  I was abled to resolve this issue.  As the disks are all having the same 

UUID.  I had to set the UUID for disk2, disk3 and disk4 for it to work.

I used the below command.

 % VboxManage internalcommands sethduuid vsim-netapp-DOT8.3.1-cm-disk2.vmdk

[nsananguly]

I am getting the following errors while trying to run the Ontap simulator 8.3.2 on Virtual Box. I have followed the exact steps as suggested on this youtube video.

https://www.youtube.com/watch?v=I56BzAgmms4

Seeking for guidance on the same. 

I did try Tonica's suggestion. The error ouput says the following : " Syntax error: Invalid command 'sethduuid'"

[SeanHatfield]

If thats where you got the error, check the vmdk filename/path. 

I use a completely different approach to virtualbox.  I make some adjustments to the ova to allow it to import directly.  I've posted about that in some other threads on vbox, but I can post an 832 version that helps.

[ADailey]

I've gone through this thread and tried/checked all of the recommended settings, but am still receiving a /cfcard panic upon booting the 8.3.2 cDOT simulator in VirtualBox 5.0.26. Has anyone else been able to get this setup working from the OVA that's provided and if so would you mind sharing the steps taken? Thank you in advance.

[SeanHatfield]

Here are the steps for bringing up the OVA in virtualbox:

1. Download Simulate ONTAP 8.3.2 for VMware Workstation, VMware Player, and VMware Fusion (vsim-netapp-DOT8.3.2-cm.ova)
2. Extract the .ova file (use 7-zip or a similar tool).  You should now have a folder containing these files:
   

   vsim-netapp-DOT8.3.2-cm-disk1.vmdk.gz
   vsim-netapp-DOT8.3.2-cm-disk2.vmdk.gz
   vsim-netapp-DOT8.3.2-cm-disk3.vmdk.gz
   vsim-netapp-DOT8.3.2-cm-disk4.vmdk.gz
   vsim-netapp-DOT8.3.2-cm.mf
   vsim-netapp-DOT8.3.2-cm.ovf

3. Extract each of the .vmdk.gz files
4. Delete the .vmdk.gz files, the vsim-netapp-DOT8.3.2-cm.mf file and vsim-netapp-DOT8.3.2-cm.ovf
5. Save the text file attached to this post and rename it vsim-netapp-DOT8.3.2-cm-vbox.ovf.  Now your file set should match this list:
   

   vsim-netapp-DOT8.3.2-cm-disk1.vmdk
   vsim-netapp-DOT8.3.2-cm-disk2.vmdk
   vsim-netapp-DOT8.3.2-cm-disk3.vmdk
   vsim-netapp-DOT8.3.2-cm-disk4.vmdk
   vsim-netapp-DOT8.3.2-cm-vbox.ovf

6. Import the appliance into virtualbox (File->Import Appliance)

You can power it up and configure it at this point, but the nics will need to be connected to the appropriate networks for your virtualbox configuration.

I made the following edits to the .ovf:

1. Adjusted the RAM to 6GB to compensate for differences in the pciHole.
2. Explicitly added a floppy device to compensate for differences in bios behaviour
3. Reordered the IDE devices to overcome an idiosyncracy in the virtualbox OVF importer
4. Removed the gz compressed vmdk markers because the windows version of virtualbox doesn't support gzip compressed vmdk import.

[nsananguly]

Sean,

Thanks a lot for the solution. It worked. Really appreciate your work around suggestion. Thanks a million again.