Simulator Discussions

OnTap Simulator 8.1.1 no longer running on ESXi 5.1 free

rkeu
26,176 Views

I'm the only one with this issue? After upgrade of my ESXi host to 5.1 the OnTap Simulator 8.1.1 no longer work. I only get the follwoing error:

 

Cannot open the disk '/vmfs/volumes/<id>/vsim-DOT811-7m/DataONTAP-sim.vmdk' or one of the snapshot disks it depends on.

The system cannot find the file specified

VMware ESX cannot find the virtual disk "/vmfs/volumes/<id>/vsim-DOT811-7m/DataONTAP-sim.vmdk". Verify the path is valid and try again.

 

Before the Update everything worked without any issue. The vmdk Files are there, it also not works if i manually assign those disk files. I have also never made any snapshots, this cannot be the problem.

A re-download of the Simulator files and add to the Host, get the same issue.

1 ACCEPTED SOLUTION

CCIE17603
26,145 Views

Everyone I have the fix. It's a VMWare issue. By default ESXi 5.1 does not load the the vmkernel multiextent module. See the KB Below.

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=2036572&sliceId=1&docTypeID=DT_KB_1_1&dialogID=448358018&stateId=1%200%...

The Fix: all you have to do is ssh into your host and  run this command from the cli: 

# vmkload_mod multiextent

The other stuff in this article didn't apply to me. All I had to do was run this command and my ONTAP Sims booted like usual, no issues. Unfortunately after a ESXi host reboot the multiextent module unloads and you have to perform this again to get your Sims to boot. If anyone can find a way to make this persistent with a switch or write a script that makes it load upon host reboot. I'm sure everyone would be very thankful.

View solution in original post

25 REPLIES 25

cratanamook
24,799 Views

Same problem here. I also tried upgrading VM hardware but no success.

rkeu
24,799 Views

Ok, then let's hope NetApp is working on this issue.

cratanamook
25,251 Views

Hi Roland,

           I got it working! The trick is in the name of the disk itself. Here's how I got it working. I think step 4, 5 and 6 is more relevant. Thanks.

1. Install vmware-workstation on my desktop (version 9)

2. add netapp 8.1.1 ESX version (vsim-DOT811-7m-esx) as VM to my vmware-workstation

3. right click manage and change hardware compatibility to workstation 9,,,

4. right click settings -> select harddisk 4 -> click utitlies -> compact

5. export as OVF template

6. import this OVF template to ESX5.1 (from web client) giving it a new name ie. test1

7. power on!

Regards,

Chakrit

rkeu
25,252 Views

Hi Chakrit

Can you perhaps place the vmx file here, especially the Disk Part? And how are the Disk named now?

cratanamook
24,799 Views

Hi Roland,

         Sure thing,, but sadly to say it boots up and let me do the config but then kernel panic out. I'm out of ideas, sorry.

-rw-------1 root root 1677721600 Oct  2 10:14 test1-73bb8b70.vswp
-rw-------1 root root 5370806272 Oct  2 10:37 test1-flat.vmdk
-rw-------1 root root      8684 Oct  2 10:38 test1.nvram
-rw-------1 root root       487 Oct  2 10:16 test1.vmdk
-rw-r--r--1 root root         0 Oct  2 10:10 test1.vmsd
-rwxr-xr-x1 root root      1751 Oct  2 10:14 test1.vmx
-rw-------1 root root         0 Oct  2 10:14 test1.vmx.lck
-rw-r--r--1 root root       260 Oct  2 10:10 test1.vmxf
-rwxr-xr-x1 root root      1728 Oct  2 10:14 test1.vmx~
-rw-------1 root root 268435456000 Oct  2 10:38 test1_1-flat.vmdk
-rw-------1 root root       490 Oct  2 10:15 test1_1.vmdk
-rw-------1 root root 1108344832 Oct  2 10:38 test1_2-flat.vmdk
-rw-------1 root root       487 Oct  2 10:15 test1_2.vmdk
-rw-------1 root root 1616904192 Oct  2 10:38 test1_3-flat.vmdk
-rw-------1 root root       487 Oct  2 10:16 test1_3.vmdk
-rw-r--r--1 root root    193589 Oct  2 10:38 vmware.log
-rw-------1 root root  96468992 Oct  2 10:14 vmx-test1-1941670768-1.vswp

Regards,

Chakrit

rkeu
24,799 Views

Ok, thanks for the Info. So we have to see how we can fix this issue.

timmyrico
12,335 Views

good info!

stephent
25,250 Views

I can confirm this behaviour. I just put esx 5.1 on my server at home and tried to get the 8.1.1 simulator working. It came back with exactly the error you are reporting.

Looks like a 5.1 compatible release is needed.

Steve

CCIE17603
26,146 Views

Everyone I have the fix. It's a VMWare issue. By default ESXi 5.1 does not load the the vmkernel multiextent module. See the KB Below.

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=2036572&sliceId=1&docTypeID=DT_KB_1_1&dialogID=448358018&stateId=1%200%...

The Fix: all you have to do is ssh into your host and  run this command from the cli: 

# vmkload_mod multiextent

The other stuff in this article didn't apply to me. All I had to do was run this command and my ONTAP Sims booted like usual, no issues. Unfortunately after a ESXi host reboot the multiextent module unloads and you have to perform this again to get your Sims to boot. If anyone can find a way to make this persistent with a switch or write a script that makes it load upon host reboot. I'm sure everyone would be very thankful.

stephent
25,250 Views

This has certainly resolved the issue for me. Thank you.

rkeu
12,786 Views

Wow thanks!! That was the Trick! Now it works!!

cratanamook
12,785 Views

Brilliant! Thank you! I'll give it a try.

AdriaansenT
12,785 Views

Great. Thanks.

I had the same issue and it worked instantly after giving the

# vmkload_mod multiextent

command

ckeith
10,750 Views

Hmm, I'm having a problem getting ESXi 5.0.0 to even register the simulator.  From vSphere pointing to vCenter I get the following error after trying to add the simulator to the inventory:

A general system error occurred:

The system returned an error.

Communication with the virtual machine might have been interrupted.

If I point the vSphere client to the actual ESX host it is able to add it to its inventory, but if I try and power it on the "action get canceled by a user" (or something like that) and it stops trying to power it on.  Basically, I think it is vCenter trying to register it but fails so it stopped the ESX host from powering it on.

Any ideas?

wolfohyeah
8,631 Views

Thanks. This command fixed my same issue in ESX4.1.

DARREN_REED
12,785 Views

To ensure that the "multiextent" module is present on every boot, you need to edit /etc/rc.local.d/local.sh and add a single line "vmkload_mod multiextent".

AdriaansenT
12,785 Views

Thanks,

I found it already

With kind Regards,

Tom Adriaansen (Storage Engineer)

Tom Adriaansen | Infrastructure Analyst | Reed Business Media

T +31 (0)314 34 92 23 | M +31 (0)6 238 76 099 | www.reedbusiness.nl<http://www.reedbusiness.nl/>

Van: Darren Reed

Verzonden: donderdag 29 november 2012 23:47

Aan: Adriaansen, Tom (RB-NL)

Onderwerp: - Re: OnTap Simulator 8.1.1 no longer running on ESXi 5.1 free

<https://communities.netapp.com/index.jspa>

Re: OnTap Simulator 8.1.1 no longer running on ESXi 5.1 free

created by Darren Reed<https://communities.netapp.com/people/darren.reed> in Simulator - View the full discussion<https://communities.netapp.com/message/95751#95751>

To ensure that the "multiextent" module is present on every boot, you need to edit /etc/rc.local.d/local.sh and add a single line "vmkload_mod multiextent".

Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/95751#95751>

Start a new discussion in Simulator by email<mailto:discussions-community-interfaces_and_tools-simulator@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=2010>

nicola_mendella
10,750 Views

Hello,

i had the same issue. What i did to fix it was to load vmkload_mod multiextent

and to use the Vcenter converter to convert the vsim-DOT812-7m into my vcenter.

It worked directly for me.


shariq_aijaz
9,504 Views

Thanks... It worked for me as well.

But now licenses are not working. Can someone help please

Regards

Shariq

sdy
NetApp
9,504 Views

which licenses and are you sure you're running 8.1.1 as in this thread? if you switched to 8.2 then the licensing infrastructure changed

and you have to pull the new set when you pull the vsim/vsa

Also its possible that the simulator you're using might not be a promoted build, the (8.1 7-mode) released simulator licenses

will only work on a promoted build and will fail with an invalid message on non-promoted builds

can you send the output of the version command, thats usually the easiest way to see if the build

was properly promoted.

Public