VirtualBox

Opened 9 years ago

Closed 9 years ago

#14661 closed defect (fixed)

Cannot Start VM After Moving From 4.3.30 to 5.0.4

Reported by: Stewart Berman Owned by:
Component: other Version: VirtualBox 5.0.4
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

Host: Windows 8.1 Pro x64 on a Surface Pro 3 512GB Gurest: Windows 8 x64

I have a number of VMs that I use as base machines. That is when I have to test something in a specific environment I clone the machine.

To avoid having a huge delay in using one when I need it I periodically start each one and apply Windows Updates.

I recently upgraded my VirtualBox from 4.3.30 to 5.0.4.

I was able to update most of my test VMs including a Windows 8 x64 machine. However, when I tried to start another Windows 8 x64 VM I got: Failed to open a session for the virtual machine <VM Name>.

Configuration error: TM setting &quot;MaybeUseOffsettedHostTSC&quot; is no longer supported. Use the &quot;Mode&quot; setting instead. (VERR_CFGM_CONFIG_UNKNOWN_VALUE).

Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

The above is not very informative. I don't know why the setting was needed and I have no idea how to replace it. I cannot find any reference to it in the documentation.

Attachments (2)

VBox.log (36.7 KB ) - added by Stewart Berman 9 years ago.
Machine Log File
W8PX64PROD.vbox (14.6 KB ) - added by Stewart Berman 9 years ago.
Machine Description

Download all attachments as: .zip

Change History (8)

comment:1 by Perry G, 9 years ago

I suspect something to do with paravirtualization interface settings but I don't see a log file to be able to verify.

by Stewart Berman, 9 years ago

Attachment: VBox.log added

Machine Log File

by Stewart Berman, 9 years ago

Attachment: W8PX64PROD.vbox added

Machine Description

comment:2 by Stewart Berman, 9 years ago

Have attached machine log file and machine definition.

comment:3 by Frank Mehnert, 9 years ago

Resolution: worksforme
Status: newclosed

Please do

VBoxManage setextradata W8PX64PROD VBoxInternal/TM/MaybeUseOffsettedHostTSC

to remove the setting which is no longer supported with VBox 5.0.

in reply to:  3 comment:4 by Stewart Berman, 9 years ago

Replying to frank:

Please do

VBoxManage setextradata W8PX64PROD VBoxInternal/TM/MaybeUseOffsettedHostTSC

to remove the setting which is no longer supported with VBox 5.0.

What did the setting do under VBox 4.0 and what is the replacement for the setting under VBox 5.0?

comment:5 by Stewart Berman, 9 years ago

Resolution: worksforme
Status: closedreopened

comment:6 by Frank Mehnert, 9 years ago

Resolution: fixed
Status: reopenedclosed

This is a non-standard setting so you must have set it yourself and I wonder why you are asking this question. This setting was replaced by TSCMode which can have the values VirtTSCEmulated, RealTSCOffset and Dynamic.

I wouldn't explain anything else right now unless you explain why you need this setting. The timing was improved with VBox 5.0 so the first step is to remove the old setting and try with the 5.0 default setting. Enabling the Hyper-V paravirt extension for the Windows 8 guest might help as well.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use