VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 1 "helpful" answer available (6 pts)
7 Replies Last post: Nov 10, 2009 11:28 AM by continuum  

Could not open virtual machine: c:\path\to\my_machine.vmx. Something is wrong with the configuration file. posted: Nov 6, 2009 11:42 AM

Click to view aachkar's profile Novice 4 posts since
Oct 9, 2009

Hello,

I'm using VMware Workstation 6.5.3 build-185404.

When I try to open (File->Open) my VM, I get the error:

"Could not open virtual machine: C:\QNX641_1\QNX641_1.vmx. Something is wrong with the configuration file."

Contents of .mvx file:

.encoding = "windows-1252"
config.version = "8"
virtualHW.version = "7"
scsi0.present = "TRUE"
memsize = "256"
ide0:0.present = "TRUE"
ide0:0.fileName = "QNX641_1-0-000002.vmdk"
ide1:0.present = "TRUE"
ide1:0.autodetect = "FALSE"
ide1:0.deviceType = "cdrom-raw"
floppy0.startConnected = "FALSE"
floppy0.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.wakeOnPcktRcv = "FALSE"
sound.present = "TRUE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
mks.enable3d = "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"
roamingVM.exitBehavior = "go"
displayName = "QNX641_1"
guestOS = "other"
nvram = "QNX641_1.nvram"
virtualHW.productCompatibility = "hosted"
ft.secondary0.enabled = "TRUE"
tools.upgrade.policy = "useGlobal"

extendedConfigFile = "QNX641_1.vmxf"

floppy0.fileName = "A:"

ide1:0.startConnected = "FALSE"
ethernet0.addressType = "generated"
tools.syncTime = "FALSE"
uuid.location = "56 4d 8d 26 8e 72 d6 0f-e2 09 6c 32 2f c0 f3 c8"
uuid.bios = "56 4d 8d 26 8e 72 d6 0f-e2 09 6c 32 2f c0 f3 c8"
ide0:0.redo = ""
vmotion.checkpointFBSize = "134217728"
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "16"
ethernet0.pciSlotNumber = "32"
sound.pciSlotNumber = "33"
vmci0.pciSlotNumber = "34"
ethernet0.generatedAddress = "00:0c:29:c0:f3:c8"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "801174472"
ide1:0.fileName = "D:"

ethernet0.connectionType = "nat"

checkpoint.vmState = ""

priority.grabbed = "normal"
priority.ungrabbed = "idle"

ide0:1.present = "FALSE"
ide0:1.fileName = "QNX641_1-0-000002.vmdk"

ide0:1.redo = ""

annotation = "This is the latest QNX VM, as of 2009-11-06.|0D|0AIt has the following:|0D|0A-QNX SDP 6.4.1|0D|0A-MME 1.2 (Aviage)|0D|0A|0D|0A- Ran out of disk space on IDE 0:0 (2GB)|0D|0A[ ] Trying to copy everything to IDE0:1 (8GB) and run from there.|0D|0A"

ide0:0.mode = "undoable"

Here's what got me to this point:


  1. Create VM as Other, with 2GB hard disk (IDE 0:0 PM /dev/hd0).
  2. Install QNX 6.4.1
  3. Needed more space, so created a second hard disk 8GB (IDE 0:1 PS /dev/hd1).
  4. Using QNX, create partition, format, install boot loader, etc.
  5. Change BIOS to boot from the 8GB hard disk (Primary Slave)
  6. QNX boots fine.
  7. Now, I wanted to delete the first hard disk since it's no longer needed. Powered down the VM. Took a snapshot. Tried to remove the disk. Got an error message (forgot what it was). Exit VMware Worksation. Open VMware Workstation. Try to open my QNX VM... I get the error described in this message's Subject heading.


I have attached a .zip of most of the files in my VM directory (except the disks).

Any help would be greatly appreciated.

Thanks!

Alain.

Attachments:
Click to view jameslin's profile Master 1,087 posts since
Jan 31, 2005
Open the .vmx file in a text editor and remove the line:

ide0:0.mode = "undoable"

That's an old setting from the Workstation 3 days. It's weird that it somehow ended up in your .vmx file. (Any idea if this is reproducible?)
Click to view jameslin's profile Master 1,087 posts since
Jan 31, 2005
aachkar wrote:
Now, I'm reluctant to try deleting the first disk again :(

If you take a snapshot first, you should be able to revert back to it if anything goes wrong.
Click to view continuum's profile Guru 12,689 posts since
Dec 18, 2003
very interesting - can you post all the vmware.logs from that special VM ?

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

Click to view continuum's profile Guru 12,689 posts since
Dec 18, 2003
none of those logs show any issues with "undoable" flag - I assume they were created before the problem occured ?

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities