Bug 143648

Summary: AMD-V is not recognized on amd64 with emulators/virtualbox-ose 3.1.2_1
Product: Ports & Packages Reporter: pieterb <pieterb>
Component: Individual Port(s)Assignee: Virtualbox Team (Nobody) <vbox>
Status: Closed FIXED    
Severity: Affects Only Me CC: pieterb
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description pieterb 2010-02-07 15:20:01 UTC 
I upgraded my virtual box from 3.0.51 to 3.1.2
following the instructions from 
http://wiki.freebsd.org/VirtualBox

After that starting a virtual machine gives an error:

Failed to start the virtual machine foobar.
VT-x is not available. (VERR_VMX_NO_VMX).
Unknown error creating VM (VERR_VMX_NO_VMX).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {6375231a-c17c-464b-92cb-ae9e128d71c3}

The same virtual machine worked fine with virtualbox 3.0.51.
The VT-x/AMD-V is enabled for the virtual machine (disabling does not work either).

Fix: 

I don't know of a fix. I migrated to Proxmox ve because of this issue.
How-To-Repeat: 	Upgrade virtualbox 3.0.51 and try to start a virtual machine.
Comment 1 Martin Wilke freebsd_committer freebsd_triage 2010-02-07 20:29:56 UTC 
State Changed
From-To: open->feedback

hi, 

build failed: 

http://64bit.miwibox.org/index.php?action=describe_port&id=1021 
http://32bit.miwibox.org/index.php?action=describe_port&id=1020
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2010-02-07 23:59:04 UTC 
State Changed
From-To: feedback->open

Fix synopsis and note that previous request for feedback seems to have 
been a misfile intended for another PR.  Over to maintainers.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2010-02-08 00:04:10 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->vbox

Over to maintainers.  (Missed in last edit)
Comment 4 Juergen Lock 2010-02-08 20:07:57 UTC 
That suspiciously sounds like this issue:
	http://www.virtualbox.org/ticket/5639
i.e. it would be a bios bug.  If you need the workaround mentioned
in that ticket (VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=true) because you can't
update the bios you'll have to try the svn versions of the vbox ports
until the official ones are updated:
	svn co https://svn.bluelife.at/projects/blueports/emulators/

 Good luck!
Comment 5 Beat Gaetzi freebsd_committer freebsd_triage 2010-03-27 10:46:02 UTC 
State Changed
From-To: open->feedback

Could you please update to 3.1.6 and retest. The fix mentioned by nox 
was merged to VirtualBox 3.1.4.
Comment 6 Bernhard Froehlich freebsd_committer freebsd_triage 2011-05-02 12:28:30 UTC 
State Changed
From-To: feedback->closed

Timeout. (>1 year)