Opened 13 years ago
Closed 8 years ago
#10269 closed defect (obsolete)
virtualbox does not work with AMD 8120 FX (codename bulldozer)
| Reported by: | bogdanstoica | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.1.8 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description
Hello
I as able to instll vbox on a new computer with AMD FX 8120 processor (8 cores) and 32 GB memory. Host OS: windows 2008 R2 S1. For HyperV Microsoft released a patch which enable features for HyperV Unfortunately with VirtualBox I'm not able to change number of processors and AMD virtualisation is not enable.
Attachments (4)
Change History (8)
comment:1 by , 13 years ago
by , 13 years ago
| Attachment: | only 1 processor available.JPG added |
|---|
by , 13 years ago
| Attachment: | unknown processor.JPG added |
|---|
by , 13 years ago
| Attachment: | taskmanager.JPG added |
|---|
by , 13 years ago
| Attachment: | computer info.JPG added |
|---|
comment:2 by , 13 years ago
Attached some captures. AMD-V is enabled, HyperV works fine under this configuration, but after a patch has been applied. Some info about AMD Bulldozer: http://www.anandtech.com/show/5448/the-bulldozer-scheduling-patch-tested From M$ site: http://support.microsoft.com/kb/2568088/en-us , found on http://www.overclockers.com/forums/showthread.php?t=690662
comment:3 by , 12 years ago
Check below link http://kunaludapi.blogspot.in/2012/05/get-hyperv-working-in-vmware.html
Replying to bogdanstoica:
Hello
I as able to instll vbox on a new computer with AMD FX 8120 processor (8 cores) and 32 GB memory. Host OS: windows 2008 R2 S1. For HyperV Microsoft released a patch which enable features for HyperV Unfortunately with VirtualBox I'm not able to change number of processors and AMD virtualisation is not enable.
comment:4 by , 8 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Reopen if still relevant with a recent release of VirtualBox and you provided the requested VBox.log file.
Could you attach a VBox.log file? I'm not entirely convinced that this is really an incompatibility. I rather assume that AMD-V is not enabled for some reason. The log file would give some hint.