Votes for vNinja.net and vSoup.net would be greatly appreciated, but since we´re not affiliated with the Dutch vMaffia we promise that you will not have to wear concrete boots or wake up to a horses head in your bed if you don´t vote for us.
I decided to take this a little step further, and try to upgrade my old (and discontinued) Iomega IX2-200 to the new IX2-200 Cloud Edition firmware.
Initially this was a big failure, as I seemingly managed to brick my device. It was only responding to pings (so the TCP/IP stack was loaded and working), but I could not bring up the web based management tool nor connect via telnet or SSH.
The only real difference between doing this in Hyper-V and on ESXi, is that the virtual floppy drive on ESXi by default doesn’t emulate an empty floppy. So, in order to mount a virtual floppy you need to create a new floppy image. Thankfully the vSphere Client can do this for you!
To use the vSphere Client to create a floppy image you can later mount in a VM, you need to edit a VM’s settings. Find the floppy drive, if the VM doesn’t have one add one, close the window and return to the VM settings once the floppy drive has been added, and select “Create new floppy image in datastore: “.
Click on the Browse button and browse to your preferred location for the floppy image. Name it, and click on Ok.
Click on Ok again to close the VM settings window and return to the vSphere Client.
There you go, an empty virtual floppy image that you can mount in a VM is now created.
To mount the image, find the floppy drive icon in the vSphere client and select the Connect to floppy image on a datastore option.
Browse to the location where you created the floppy image, and select it.
Now, the VM has an empty floppy that you’ll need to format before you can use it.