AMD-V with Ryzen not yet supported?
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: AMD-V with Ryzen not yet supported?
A "microcode update" is still a software update and a really harder one to implement and deploy. And as long as AMD has not released one, then VirtualBox has to work around it, until (and if) such a microcode update ever happens. And even then, the workaround would still be in the VirtualBox code, it will never go away...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Oracle Corporation
- Posts: 2973
- Joined: 19. Dec 2007, 15:45
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Any and all
- Contact:
Re: AMD-V with Ryzen not yet supported?
We have reported the problem to AMD. The workaround (not "hack") has to stay in place until we have information about how to distinguish Ryzens with working vs. non-working VME.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: AMD-V with Ryzen not yet supported?
Off-topic question maybe, but when wouldn't a "workaround" like this be called a "hack"? You check your CPU, and if it's one of the affected ones, you modify the CPU leafs to present something different, to impersonate another CPU, right? I mean *I* could call it either, but why specifically a "not hack"?michaln wrote:The workaround (not "hack")
Honest question, maybe a little two much in the fine details of the English language?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Oracle Corporation
- Posts: 2973
- Joined: 19. Dec 2007, 15:45
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Any and all
- Contact:
Re: AMD-V with Ryzen not yet supported?
A hack implies something that could (or should) be done better, but it's quick and simple and does most of what's needed. A workaround means something that works around a bug (typically someone else's bug) in a way that solves the problem while triggering a minimum of negative side effects.
A workaround is a non-optimal but typically the best possible solution. A hack is by definition not the best possible solution.
In this particular case, we can't fix the CPU (that would be the optimal solution) but we can make the problem invisible for 99.99% of affected users (which makes it the best possible solution). I hope that makes some sense.
A workaround is a non-optimal but typically the best possible solution. A hack is by definition not the best possible solution.
In this particular case, we can't fix the CPU (that would be the optimal solution) but we can make the problem invisible for 99.99% of affected users (which makes it the best possible solution). I hope that makes some sense.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: AMD-V with Ryzen not yet supported?
Yes, it does. As in:
Hack: we quickly hacked together a quick and dirty solution.
Workaround: we thought of this thoroughly and found a safe working solution.
And yes, it was the fine details of the English language, but once you explained it, terms like Hackathon and hack* started being "clearer".
Thank you ser!
Hack: we quickly hacked together a quick and dirty solution.
Workaround: we thought of this thoroughly and found a safe working solution.
And yes, it was the fine details of the English language, but once you explained it, terms like Hackathon and hack* started being "clearer".
Thank you ser!
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Oracle Corporation
- Posts: 2973
- Joined: 19. Dec 2007, 15:45
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Any and all
- Contact:
Re: AMD-V with Ryzen not yet supported?
There will be a fix coming from AMD in the form of a microcode update (embedded in updated BIOS). When that will actually become available to users is unknown and depends on OEMs.
-
- Posts: 2
- Joined: 14. Jul 2017, 15:15
Re: AMD-V with Ryzen not yet supported?
Any update on this? Has a microcode update been released, which resolves the issues raised?michaln wrote:There will be a fix coming from AMD in the form of a microcode update (embedded in updated BIOS). When that will actually become available to users is unknown and depends on OEMs.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: AMD-V with Ryzen not yet supported?
I'm afraid you should ask AMD about that, not Oracle.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: AMD-V with Ryzen not yet supported?
Actually the microcode update would come from the motherboard manufacture as provided from AMD. That makes it take a lot longer if at all, but that's the way it happens.
-
- Oracle Corporation
- Posts: 2973
- Joined: 19. Dec 2007, 15:45
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Any and all
- Contact:
Re: AMD-V with Ryzen not yet supported?
AMD did their part and released the fix in AGESA 1.0.0.6. Whether an update is available for your board is something you need to check with your OEM.metastatic wrote:Any update on this? Has a microcode update been released, which resolves the issues raised?
-
- Posts: 2
- Joined: 14. Jul 2017, 15:15
Re: AMD-V with Ryzen not yet supported?
Thanks for the informative reply. It is appreciated.
Re: AMD-V with Ryzen not yet supported?
I use the AGESA 1.0.0.6b with ryzen 1800x. And VirtualBox-5.1.28 is working perfectly.
Re: AMD-V with Ryzen not yet supported?
I am supposedly running AGESA 1.0.0.6 (but not 6b) on an MSI board. I copied an XP VM from a previous machine to a new Ryzen 2 2700x box. Virtualization is on in the BIOS and detected via lscpu. VirtualBox warned me to turn CPU virtualization off, and I did. The options are now disabled. I ran
Is this expected before 1.0.0.6b or merely before 1.0.0.6? I'm going to ask MSI either way. Thoughts appreciated!
as suggested. My XP VM still hard-locks during boot on version 6.0.5-128513 installed from the .run file on Arch Linux. Attached is the most recent log and output of lscpu.modifyvm a2858727-f303-46cd-b44a-90af035aa114 --cpuidset 1 00800f11 00000800 56d8220b 078bfbfd
Is this expected before 1.0.0.6b or merely before 1.0.0.6? I'm going to ask MSI either way. Thoughts appreciated!
- Attachments
-
- VBox.log.gz
- (58.7 KiB) Downloaded 47 times
-
- lscpu.out.gz
- (857 Bytes) Downloaded 49 times