Subscribe

Simulator 8.3.2 - Login Data?

[ Edited ]

Old topic:

Simulator 8.0.1 in KVM

http://community.netapp.com/t5/Simulator-Discussions/Simulator-8-0-1-in-KVM/td-p/22510

 

--

 

OS: openSUSE 42.1

VM: Qemu 2.6.0

 

NetApp ONTAP Simulator: 8.3.2

 

 

Preparation:

 

tar xf vsim-netapp-DOT9.0RC1-cm.ova
for i in *.gz; do gunzip -k "${i}"; done for i in *.vmdk; do qemu-img convert -f vmdk -O qcow2 "${i}"; done

 

Qemu command:

 

qemu-system-x86_64 \
\
-boot order=c,menu=on \
-drive if=floppy,index=0 \
-drive file=vsim-netapp-DOT9.0RC1-cm-disk1.qcow2,media=disk,if=ide,index=0,format=qcow2 \
-drive file=vsim-netapp-DOT9.0RC1-cm-disk2.qcow2,media=disk,if=ide,index=1,format=qcow2 \
-drive file=vsim-netapp-DOT9.0RC1-cm-disk3.qcow2,media=disk,if=ide,index=2,format=qcow2 \
-drive file=vsim-netapp-DOT9.0RC1-cm-disk4.qcow2,media=disk,if=ide,index=3,format=qcow2 \
-drive media=cdrom,if=scsi,index=0 \
\
\
-device e1000-82545em,id=e1000-82545em.0,mac=52:54:00:00:00:01,vlan=1 \
-net tap,script=no,downscript=no,ifname=tap1,vlan=1 \
-device e1000-82545em,id=e1000-82545em.1,mac=52:54:00:00:00:02,vlan=2 \
-net tap,script=no,downscript=no,ifname=tap2,vlan=2 \
-device e1000-82545em,id=e1000-82545em.2,mac=52:54:00:00:00:03,vlan=3 \
-net tap,script=no,downscript=no,ifname=tap3,vlan=3 \
-device e1000-82545em,id=e1000-82545em.3,mac=52:54:00:00:00:04,vlan=4 \
-net tap,script=no,downscript=no,ifname=tap4,vlan=4 \
\
-cpu host \
-smp 2 \
-m 8192 \
-enable-kvm \
\
-vga cirrus \
-k de \
-rtc base=utc \
\
-nodefaults \
-serial vc \
\
-display gtk \

 

On first boot I pressed CTRL-C and chose 4 to initialize the system.

 

On the second boot I get this:

The root volume is not up. This node is not fully operational. Contact support personnel for further assistance.

Error: "setup" is not a recognized command

Thu Aug 18 11:21:01 UTC 2016
login: 

Does anyone know the login data for this?

Re: Simulator 8.x in KVM

If you haven't set it yet, its admin with a blank password.  Did it panic along the way? You shouldn't be seeing the note about the root volume.

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

Re: Simulator 8.x in KVM

[ Edited ]

Looks like I can't login with user "admin" and password ""  because of the errors.

 

These are screenshots from starting and setting up a new VM with the following configuration. I tried to configure Qemu/KVM to look as similar as possible to an VMware-Player virtual machine.

 

OS: openSUSE 42.1

VM: Qemu 2.6.0

 

NetApp ONTAP Simulator: 8.3.2

 

qemu-system-x86_64 \
\
-boot c,menu=on \
-drive if=floppy,index=0 \
-device piix4-ide,id=piix4-ide.1,bus=pcie.0,addr=7.0 \
-drive file=vsim-esx-DOT8.3.2-cm-disk1.qcow2,media=disk,if=none,id=ide0-hd0,format=qcow2 \
-device ide-hd,bus=piix4-ide.1.0,drive=ide0-hd0,bootindex=0 \
-drive file=vsim-esx-DOT8.3.2-cm-disk2.qcow2,media=disk,if=none,id=ide0-hd1,format=qcow2 \
-device ide-hd,bus=piix4-ide.1.0,drive=ide0-hd1,bootindex=1 \
-drive file=vsim-esx-DOT8.3.2-cm-disk3.qcow2,media=disk,if=none,id=ide1-hd0,format=qcow2 \
-device ide-hd,bus=piix4-ide.1.1,drive=ide1-hd0,bootindex=2 \
-drive file=vsim-esx-DOT8.3.2-cm-disk4.qcow2,media=disk,if=none,id=ide1-hd1,format=qcow2 \
-device ide-hd,bus=piix4-ide.1.1,drive=ide1-hd1,bootindex=3 \
\
-device megasas,bus=pcie.0,id=scsi.0,bus=pcie.0,addr=10.0 \
-drive media=cdrom,if=none,id=scsi0-cd0 \
-device scsi-cd,bus=scsi.0.0,drive=scsi0-cd0,bootindex=4 \
\
-device i82801b11-bridge,bus=pcie.0,id=pcie.1 \
-device i82801b11-bridge,bus=pcie.0,id=pcie.2 \
-device e1000-82545em,id=e1000-82545em.0,mac=00:0C:29:DE:F2:F0,vlan=1,bus=pcie.2,addr=0.0 \
-net tap,script=no,downscript=no,ifname=tap24,vlan=1 \
-device e1000-82545em,id=e1000-82545em.1,mac=00:0C:29:DE:F2:FA,vlan=2,bus=pcie.2,addr=1.0 \
-net tap,script=no,downscript=no,ifname=tap25,vlan=2 \
-device e1000-82545em,id=e1000-82545em.2,mac=00:0C:29:DE:F2:04,vlan=3,bus=pcie.2,addr=2.0 \
-net user,hostfwd=tcp:127.0.0.1:50124-:80,id=user.0,vlan=3 \
-device e1000-82545em,id=e1000-82545em.3,mac=00:0C:29:DE:F2:0E,vlan=4,bus=pcie.2,addr=3.0 \
-net user,hostfwd=tcp:127.0.0.1:50125-:80,id=user.1,vlan=4 \
\
-cpu host \
-smp 2 \
-m 8192 \
-balloon virtio \
-enable-kvm \
\
-device vmware-svga,addr=F.0 \
-k de \
-device nec-usb-xhci,id=xhci \
-usb \
-usbdevice tablet \
-rtc base=utc \
\
-M q35 \
-nodefaults \
-nographic \
-no-user-config \
-nodefconfig \

 

Update: Replace seperate screenshots by a single "long" cut-together screenshot.

original.png

Re: Simulator 8.x in KVM

It looks like the e1000 type in the VM isn't recognized by ONTAP.  

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

Re: Simulator 8.x in KVM

I especially choose the "e1000-82545em" device (instead of the KVM/Qemu default "e1000-82540em" for e1000) , because this kind of e1000 is also emulated by VMware.

And, as said before by PYITESOAM, "e1000-82545em" should work.

http://community.netapp.com/t5/Simulator-Discussions/Simulator-8-0-1-in-KVM/td-p/22510#messagebodydisplay_0_8

Re: Simulator 8.x in KVM

RIght, but you are also getting

"Warning: Theere do not appear to be any network interfaces attached to this system."

So either, the PCI ID is different, its not finding it behind the bridge, or QEMUs implementation is different enough to prevent the driver from claiming the device.

 

Maybe try moving one or two of them to the PCI root and see if that message goes away.

 

 

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

Re: Simulator 8.x in KVM

[ Edited ]

I replaced the screenshots above by one cut-together "long" screenshot, also including some parts left out before. You may have another look at it.

 

Looks like I can't login because "the root volume is not up". And this has first priority for me, because if I can login I can debug everything else from the BSD shell.

 

Switching the pci bus positions as following didn't changed anything in the bahaviour of the VM.

 

-device e1000-82545em,id=e1000-82545em.0,mac=00:0C:29:DE:F2:F0,vlan=1,bus=pcie.2,addr=0.0 \
-net tap,script=no,downscript=no,ifname=tap24,vlan=1 \
-device e1000-82545em,id=e1000-82545em.1,mac=00:0C:29:DE:F2:FA,vlan=2,bus=pcie.2,addr=1.0 \
-net tap,script=no,downscript=no,ifname=tap25,vlan=2 \
-device e1000-82545em,id=e1000-82545em.2,mac=00:0C:29:DE:F2:04,vlan=3,bus=pcie.0,addr=3.0 \
-net user,hostfwd=tcp:127.0.0.1:50124-:80,id=user.0,vlan=3 \
-device e1000-82545em,id=e1000-82545em.3,mac=00:0C:29:DE:F2:0E,vlan=4,bus=pcie.1,addr=0.0 \
-net user,hostfwd=tcp:127.0.0.1:50125-:80,id=user.1,vlan=4 \

Re: Simulator 8.x in KVM

Thats easier to read.  Earlier it says "giving up waiting for mroot", so for some reason the root volume is not coming up.

 

Try rebooting, stop at the boot menu, and pick option 5.  Once maintenance mode comes up check the status of the aggrs and volumes.

 

 

 

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

Re: Simulator 8.x in KVM

Unfortunately I can't get to the BSD shell. What else can I check in the ONTAP shell?

 

bootlog_5.png

Re: Simulator 8.x in KVM

Not a lot.  The aggr is up but the root volume is not coming up. I was able to replicate this on a regular VMware based vsim by removing all the nics. It took a really long time to come up but I eventually got:

*********************** 
**  SYSTEM MESSAGES  ** 
*********************** 

The root volume is not up. This node is not fully operational. Contact support 
personnel for further assistance. 
 
 

Error: "setup" is not a recognized command


login: 

Logging in as admin goes directly to the setup script, which fails, and drops back to the login prompt.  Diag is still locked at this point.  You can unlock it by rebooting and using option 3 to set the diag password, but you're still not going to get very far without nics.  

 

After I add working nics to my test vm, I can complete node setup but the root vol needs recovery:

*********************** 
**  SYSTEM MESSAGES  ** 
*********************** 

The contents of the root volume may have changed and the local management 
configuration may be inconsistent and/or the local management databases may be 
out of sync with the replicated databases. This node is not fully operational. 
Contact support personnel for the root volume recovery procedures.  

Once you get the nics figured out, its probably better to start over.

 

 

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