Page 3 of 4
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 7. Dec 2013, 01:20
by pepe_gotera
Perryg wrote:I would think that it would have to be the exact same version you had before. You may get away with 4.2.18 or .20.
At this point there are no promises it will work or make things worse.
Thanks! As I have just posted, it finally worked with .20 but... it's a bit incomprehensible anyway.
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 7. Dec 2013, 01:32
by Perryg
Well its hard to explain but the changes to the way ring0 and ring3 talk just upsets the application and the new API.
Just remember this and don't try to update while machines are not shut down and you will not see this issue again.
Actually you had two issues and the one that is still waiting for you will need to be addressed if they don't get that fixed. Its the whole longmode debacle.
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 7. Dec 2013, 02:00
by pepe_gotera
Perryg wrote:Well its hard to explain but the changes to the way ring0 and ring3 talk just upsets the application and the new API.
Just remember this and don't try to update while machines are not shut down and you will not see this issue again.
Actually you had two issues and the one that is still waiting for you will need to be addressed if they don't get that fixed. Its the whole longmode debacle.
What do you mean?
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 7. Dec 2013, 02:15
by Perryg
Read the subject line. That error is not the same as the one where you updated without shutting down ( guest is not mutable )
Updating to 4.3.* is where this VT-x error is waiting. Its fixable but you need to not have extra issue to deal with at the same time.
Long story short. If you update to 4.3.0 and get this error you need to set --longmode off on 32-bit guests and sometimes even turn --hwvirtex off
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 8. Dec 2013, 00:59
by pepe_gotera
Perryg wrote:Read the subject line. That error is not the same as the one where you updated without shutting down ( guest is not mutable )
Updating to 4.3.* is where this VT-x error is waiting. Its fixable but you need to not have extra issue to deal with at the same time.
Long story short. If you update to 4.3.0 and get this error you need to set --longmode off on 32-bit guests and sometimes even turn --hwvirtex off
Graet! I'll take it in account for the future updating!
Thanks!
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 3. Jan 2014, 10:56
by VikramAdi
I have the same error, and even after setting long mode off and hwdvirtex off the vm does not start. I have attached the log file.The processor does not have vt ex. system is running windows 7 32 bit.
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 3. Jan 2014, 11:18
by mpack
VikramAdi.VBox.log wrote:
00:00:01.586242 NumCPUs <integer> = 0x0000000000000002 (2)
...
00:00:01.454326 Guest OS type: 'Ubuntu'
00:00:01.462687 Forced fHMEnabled to TRUE by SMP guest.
00:00:01.462714 fHMForced=true - SMP
This has nothing to do with upgrading to 4.3.6, or with the problems described above. In your case the problem is that you can't assign multiple CPUs to a guest if the host CPU doesn't have VT-x. The VT-x service is
required for this feature, so of course turning it on in the GUI then off on the command line will not help at all.
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 3. Jan 2014, 11:23
by VikramAdi
I am a noob. can you specify the steps to resolve this problem?
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 3. Jan 2014, 11:28
by mpack
In the VM settings, set the number of CPUs to 1. Make sure VT-x is not enabled.
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 3. Jan 2014, 11:33
by VikramAdi
The no of cpus is already set to 1. and i have already taken all the steps mentioned above to have vt-x disabled
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 3. Jan 2014, 11:44
by mpack
The number of CPUs is set to 2, according to the log you posted.
Post the .vbox file of the VM (zipped). Make sure the VM is shut down (not suspended) before you make settings changes. Make sure you're looking in the right VM folder.
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 3. Jan 2014, 11:51
by VikramAdi
I have attached the file
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 3. Jan 2014, 12:17
by mpack
Still says 2 CPUs.
.vbox file wrote:
<CPU count="2" hotplug="false">
I suspect that the GUI may be correcting the settings before it shows the fields to you. Try using VBoxManage to force nCPUs to 1, i.e. shut VBox down then :-
Code: Select all
VBoxManage modifyvm 638fd8c8-490f-41b0-ac8f-eee313121b5b --cpus 1
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 3. Jan 2014, 12:36
by VikramAdi
This worked!! (i had to change the <name> though!!)
thanx alot!!
do i restore the previous settings that i changed??
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
Posted: 3. Jan 2014, 14:09
by mpack
You have only mentioned turning longmode off and VT-x off, I would now leave both as they are.