I use to run a PC, now on a Power Book. I just opened an old Win98 VM guest from the old days. (Fusion v5.0.3) Upgraded tools, got it working sweet again. My "problem" is that for some reason I had taken snapshots while the guest was on my old PC with Workstation. For the life of me, I cant see how to remove them in Fusion, it acts like there isn't any snapshots, but looking in the folder I can see them. Anyone have ideas short of finding a PC somewhere and installing Workstation? (which I assume would have to be the newest version and I don't have)
FILES:
11/13/2013 10:34 AM <DIR> .
11/12/2013 01:28 PM <DIR> ..
09/23/2011 05:39 PM 6,830,080 Everything.iso
11/12/2013 02:21 PM 1,474,560 TweakUI.flp
11/12/2013 03:38 PM 260,571,136 Windows 98-s001.vmdk
11/12/2013 03:38 PM 327,680 Windows 98-s002.vmdk
11/12/2013 03:38 PM 327,680 Windows 98-s003.vmdk
11/12/2013 03:38 PM 327,680 Windows 98-s004.vmdk
11/12/2013 03:38 PM 65,536 Windows 98-s005.vmdk
11/12/2013 03:38 PM 8,684 Windows 98.nvram
11/13/2013 10:34 AM 19,834 Windows 98.plist
11/12/2013 03:35 PM 670 Windows 98.vmdk
11/11/2013 04:40 PM 0 Windows 98.vmsd
11/12/2013 03:38 PM 2,586 Windows 98.vmx
11/11/2013 04:40 PM 265 Windows 98.vmxf
13 File(s) 269,957,343 bytes
2 Dir(s) 134,197,178,368 bytes free
VMX:
.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "9"
memsize = "256"
ide0:0.present = "TRUE"
ide0:0.fileName = "Windows 98.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "Everything.iso"
ide1:0.deviceType = "cdrom-image"
ethernet0.present = "TRUE"
ethernet0.connectionType = "bridged"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet0.addressType = "generated"
ethernet0.linkStatePropagation.enable = "TRUE"
usb.present = "TRUE"
ehci.present = "TRUE"
sound.present = "TRUE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
hpet0.present = "TRUE"
tools.syncTime = "TRUE"
displayName = "Windows 98"
guestOS = "win98"
nvram = "Windows 98.nvram"
virtualHW.productCompatibility = "hosted"
proxyApps.publishToHost = "FALSE"
tools.upgrade.policy = "upgradeAtPowerCycle"
powerType.powerOff = "soft"
powerType.powerOn = "soft"
powerType.suspend = "soft"
powerType.reset = "soft"
extendedConfigFile = "Windows 98.vmxf"
ethernet0.generatedAddress = "00:0C:29:6D:56:F7"
vmci0.id = "980244215"
uuid.location = "56 4d 5e 23 04 42 37 aa-0c 9c 28 55 c2 30 d7 e6"
uuid.bios = "56 4d 0f d0 6b 76 f3 ba-88 19 ea 14 3a 6d 56 f7"
cleanShutdown = "TRUE"
replay.supported = "FALSE"
replay.filename = ""
ide0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
usb.pciSlotNumber = "32"
ethernet0.pciSlotNumber = "33"
sound.pciSlotNumber = "34"
ehci.pciSlotNumber = "35"
vmci0.pciSlotNumber = "36"
usb:1.present = "TRUE"
ethernet0.generatedAddressOffset = "0"
vmotion.checkpointFBSize = "16777216"
usb:1.speed = "2"
usb:1.deviceType = "hub"
usb:1.port = "1"
usb:1.parent = "-1"
usb.autoConnect.device0 = ""
checkpoint.vmState = ""
softPowerOff = "TRUE"
ide1:0.startConnected = "TRUE"
ethernet0.startConnected = "TRUE"
tools.remindInstall = "FALSE"
floppy0.present = "TRUE"
gui.exitOnCLIHLT = "FALSE"
floppy0.fileType = "file"
floppy0.fileName = "/Users/sthoms/Documents/Virtual Machines.localized/Win98/TweakUI.flp"
floppy0.clientDevice = "FALSE"
floppy1.present = "FALSE"
usb:0.present = "TRUE"
usb:0.deviceType = "hid"
usb:0.port = "0"
usb:0.parent = "-1"
The "-s00x.vmdk" files are no snapshots. These are 2GB-sparse files which make up the virtual disk. Snapshot .vmdk files are usually named "...-00000x.vmdk".
André
The "-s00x.vmdk" files are no snapshots. These are 2GB-sparse files which make up the virtual disk. Snapshot .vmdk files are usually named "...-00000x.vmdk".
André
Thank you.
Your comment led me to: VMDK-Handbook-Basics which has a nice write up on identification.
The most reliable way to identify the vmdk-type is to look it up in the description itself.
The "createType" parameter lists the exact type.
You can guess the type by looking at the size and extensions of the files that are present.
a 1 Kb small *.vmdk is probably the description text file used by most types
a 1 Kb small *-00000*.vmdk is probably the descriptor of a snapshot
a max 2Gb large *-s00*.vmdk is probably part of twoGbMaxExtentSparse
a max 2Gb large *-00000*-s00*.vmdk is probably part of snapshot on hosted platforms
a 2Gb large *-f00*.vmdk is probably part of a twoGbMaxExtentFlat
a *-f00*.vmdk smaller then 2 Gb is probably the last slice of part of a twoGbMaxExtentFlat
a large *-flat.vmdk is probably part of a monolithicFlat or vmfs
a large *-delta.vmdk is probably part of a ESX-snapshot
a large *-00000*.vmdk is probably a snapshot with embedded descriptor used on hosted platforms
Guess I could start another thread, but can Fusion convert Sparse to Flat? VMConverter maybe?
Afaik Fusion contains the vmware-vdiskmanager command line tool, which can be used to convert virtual disks into other formats. However, the current 2GB sparse format is the default virtual disk format and there's no need to change it.
André
can Fusion convert Sparse to Flat? VMConverter maybe?
No, just Settings > Hard Disk > Advanced options.
a.p., Good point, think I will leave well enough alone then.
Irucker, thanks for the pointer. Note, I didn't see it in my copy/version of Fusion though.
Thanks all!!!