[Solved] Troubles upgrading from 5.x to 6.x with Windows 10

[TheRedhead]

Hello,

I am running VirtualBox on a Fedora x86_64 machine. I have been running the 5.x series for a while with no issues.

I recently tried upgrading to 6.0 when it came out, but had problems with my Windows 10 VM where it just won't start. I held out for 6.0.2 hoping it would get resolved, but I am now having the same issue with it as well.

When I try to start the VM, I get a pop up stating starting virtual machine, but it stays at 0%. After a minute or so, another will pop up and move to 20% but then freezes. The main VM window just remains black. I never see the bios screen or anything else.

I am not using EFI which seems to be an issue in the other theads.

My Linux guests all seem to boot fine.

Attached is a screen shot and the VBox.log.

Any suggestions?

[andyp73]

Can you zip up and post the .vbox recipe file for the guest in question. You can get it by right clicking on the guest in the VirtualBox Manager and selecting "Show in File Manager". We will also need the global configuration file VirtualBox.xml. The Where Oracle VM VirtualBox Stores its Files will tell you where to look for it.

There is a rogue extra settings in one of these files that is causing the following error:

[quote]00:00:00.461187 VMSetError: Duplicate config values '/CPUM/CMPXCHG16B' and '/CPUM/IsaExts/CMPXCHG16B' - please remove the former![/quote]

-Andy.

[TheRedhead]

Attached are the files requested

[TheRedhead]

The Windows 10.vbox file does contain this line:

<ExtraDataItem name="VBoxInternal/CPUM/CMPXCHG16B" value="1"/>

I tried deleting it manually, but it gets recreated. I am guessing there is some other way I am supposed to get rid of it.

[andyp73]

That is the line that needs deleting. I think you should be OK deleting it manually provided that the guest is fully shutdown and all of the VirtualBox services have been terminated on the host.

-Andy.

[TheRedhead]

Thanks.

I couldn't find the process that was holding that file, so I ended up removing VirtualBox all together, rebooted, edited the file, and reinstalled.

After that, I was able to start the VM without issue.

Thank you very much for the input!