VMware Communities
mihirjasani
Contributor
Contributor
Jump to solution

Problem starting a VM converted to VMX from OVF

Hello Everyone,

I am using Workstation 10 and trying to access a VM that was converted to VMX from OVF using ovftool. The VM does not start at all and I see the following in the log repeatedly until the log fills up and doesnt rollover anymore:

2014-02-19T09:33:23.702+05:30| mks| I120: SVGA disabling SVGA

2014-02-19T09:33:23.702+05:30| vcpu-0| I120: PCIBridge4: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.702+05:30| vcpu-0| I120: pciBridge4:1: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.702+05:30| vcpu-0| I120: pciBridge4:2: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.702+05:30| vcpu-0| I120: pciBridge4:3: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.702+05:30| vcpu-0| I120: pciBridge4:4: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.702+05:30| vcpu-0| I120: pciBridge4:5: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.702+05:30| vcpu-0| I120: pciBridge4:6: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge4:7: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: PCIBridge5: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge5:1: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge5:2: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge5:3: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge5:4: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge5:5: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge5:6: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge5:7: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: PCIBridge6: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge6:1: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge6:2: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge6:3: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge6:4: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge6:5: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge6:6: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge6:7: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: PCIBridge7: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.718+05:30| vcpu-0| I120: pciBridge7:1: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.733+05:30| vcpu-0| I120: pciBridge7:2: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.733+05:30| vcpu-0| I120: pciBridge7:3: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.733+05:30| vcpu-0| I120: pciBridge7:4: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.733+05:30| vcpu-0| I120: pciBridge7:5: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.733+05:30| vcpu-0| I120: pciBridge7:6: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.733+05:30| vcpu-0| I120: pciBridge7:7: ISA/VGA decoding enabled (ctrl 0004)

2014-02-19T09:33:23.858+05:30| vcpu-0| I120: DISKUTIL: scsi0:0 : geometry=6527/255/63

2014-02-19T09:33:23.858+05:30| vcpu-0| I120: DISKUTIL: scsi0:0 : capacity=104857600

2014-02-19T09:33:23.858+05:30| vcpu-0| I120: SCSI0: RESET BUS

2014-02-19T09:33:23.952+05:30| vcpu-1| I120: CPU reset: soft (mode 2)

2014-02-19T09:33:23.967+05:30| vcpu-0| I120: BIOS-UUID is 56 4d 6d 54 57 74 05 7c-c5 a0 02 a1 74 40 66 b7

2014-02-19T09:33:24.264+05:30| vcpu-0| I120: SVGA enabling SVGA

So, there appears to be a problem with SVGA and I dont know how to get around it. Has anyone experienced this and found a resolution? The VM was originally hosted on an ESXi server from where it was converted to OVF. I am attaching the complete log in case that is useful. Any help/pointers will be highly appreciated!

0 Kudos
1 Solution

Accepted Solutions
WoodyZ
Immortal
Immortal
Jump to solution

Yes it is safe to enable VT-x in the BIOS and you'll need to in order to run 64-bit Guest OSes. (Processor Requirements for Host Systems)

Also once VT-x is enabled you need to completely shutdown the Host, not just reboot.

After that other things to consider is removing the following from the .vmx configuration file (if only temporarily) and if need be for testing disabling 3D acceleration too.


svga.maxWidth = "1280"

svga.maxHeight = "1024"

svga.vramSize = "5242880"

BTW I would not necessarily update the BIOS unless the Manufacture recommends it or it's a case when a newer BIOS allows for VT-x to be enabled because a previous version didn't.  If you've never updated a BIOS before then I'd suggest you not do it yourself unless you absolutely know what you're doing! Smiley Wink

View solution in original post

0 Kudos
6 Replies
WoodyZ
Immortal
Immortal
Jump to solution

What OS is installed in the Virtual Machine?

0 Kudos
mihirjasani
Contributor
Contributor
Jump to solution

The VM's OS is Windows 7

0 Kudos
WoodyZ
Immortal
Immortal
Jump to solution

Then change it from Other and Other to Microsoft Windows and Windows 7 x64 (assuming x64 from the amount of RAM you've assigned).

VM > Settings > Options > General > Guest operating system

Now see if it will run properly.

mihirjasani
Contributor
Contributor
Jump to solution

Thanks Woody.

That did make some difference in that the VM actually shows as running. However, it is not and the log messages are the same wrt SVGA enable/disable. One interesting thing, my guest is supposed to be Windows 7 x64. However, when I tried to run it in that mode, I got the following error message:

2014-02-19T10:23:00.139+05:30| vmx| I120: Msg_Post: Error

2014-02-19T10:23:00.139+05:30| vmx| I120: [msg.cpuid.noLongmode2] This virtual machine is configured for 64-bit guest operating systems. However, 64-bit operation is not possible.

2014-02-19T10:23:00.139+05:30| vmx| I120+ This host supports Intel VT-x, but Intel VT-x is disabled.

2014-02-19T10:23:00.139+05:30| vmx| I120+ Intel VT-x might be disabled if it has been disabled in the BIOS/firmware settings or the host has not been power-cycled since changing this setting.

2014-02-19T10:23:00.139+05:30| vmx| I120+ (1) Verify that the BIOS/firmware settings enable Intel VT-x and disable 'trusted execution.'

2014-02-19T10:23:00.139+05:30| vmx| I120+ (2) Power-cycle the host if either of these BIOS/firmware settings have been changed.

2014-02-19T10:23:00.139+05:30| vmx| I120+ (3) Power-cycle the host if you have not done so since installing VMware Workstation.

2014-02-19T10:23:00.139+05:30| vmx| I120+ (4) Update the host's BIOS/firmware to the latest version.

2014-02-19T10:23:00.139+05:30| vmx| I120+ For more detailed information, see http://vmware.com/info?id=152.

I did follow the link at the end of the message, however, I am not sure if I should update the BIOS or not. I believe since the guest OS is 64-bit, I do need to run it as that. My host OS is 64-bit so not a problem there.

Any more pointers in this regard, specifically if its safe to change the BIOS settings?

Thanks again,

Mihir

0 Kudos
WoodyZ
Immortal
Immortal
Jump to solution

Yes it is safe to enable VT-x in the BIOS and you'll need to in order to run 64-bit Guest OSes. (Processor Requirements for Host Systems)

Also once VT-x is enabled you need to completely shutdown the Host, not just reboot.

After that other things to consider is removing the following from the .vmx configuration file (if only temporarily) and if need be for testing disabling 3D acceleration too.


svga.maxWidth = "1280"

svga.maxHeight = "1024"

svga.vramSize = "5242880"

BTW I would not necessarily update the BIOS unless the Manufacture recommends it or it's a case when a newer BIOS allows for VT-x to be enabled because a previous version didn't.  If you've never updated a BIOS before then I'd suggest you not do it yourself unless you absolutely know what you're doing! Smiley Wink

0 Kudos
mihirjasani
Contributor
Contributor
Jump to solution

A thing of beauty is joy forever! Well, I took the leap of faith and changed the bios. And we are up and running! Thank you for the timely help. Next time, I will remember to ask for help first before spending time tinkering with things! Smiley Happy

0 Kudos