8 ms·
VME Broken on AMD Ryzen
- m_mueller 10y agoSo if I get this correctly, as long as the Host OS is 64bit we're fine, since VME isn't supported on that anyways? I'm thinking 32bit hosts running VMs of any sort should be an increasingly rare case, but nevertheless it's going to be interesting to see if and when AMD releases a fixed version.
- yuhong 10y agoIt can affect 32-bit guest OSes running on 64-bit hosts, and that is how they discovered the bug.
- mrb 10y agoA 64-bit host, running a 32-bit guest, itself running a 16-bit app. This scenario can run into the VME bug.
- xienze 10y agoOr a 64bit host running a WinXP guest.
- brownbat 10y agoAny exploitation scenarios here? Could you package a trimmed down version of that stack up and cause a reliable crash on Ryzens operating on a more typical platform? Maybe it becomes a bit of a rube goldberg malware at that point...
- Dylan16807 10y agoThe first part of that is optional, and the last part of that is also optional.
- pcwalton 10y agoThis may be an unpopular opinion, but making ancient x86 features unreliable strikes me as a good thing. Virtual 8086 mode is an awful virtualization solution, as you can't enter protected mode from within it. This makes it only good for running a subset of DOS apps: either real-mode-only apps or those written to an unspecified subset of DPMI [1]. Ryzen CPUs are easily fast enough to emulate them. And if that's not enough, x86 has had real virtualization for years now, with a functioning protected mode (and long mode!) in addition to real mode. We're long overdue for a simplification of the PC platform. Having CPUs out there with broken legacy features accelerates the migration away from those features. Hopefully this leads to dropping them outright at some point. [1]: https://en.wikipedia.org/wiki/DOS_Protected_Mode_Interface#History https://en.wikipedia.org/wiki/DOS_Protected_Mode_Interface#H...
- yuhong 10y agoI think this is just a bug though. But yes, I have been thinking of creating a new version of x86 that drops things like segmentation, real mode, virtual 8086 mode, and 16-bit protected mode.
- pcwalton 10y agoRight, I know it's not intentional. My point is that this bug has unintended benefits. :)
- yjftsjthsd-h 10y agoKeep in mind that if you drop the old stuff, you'll have to provide a bootloader and even then it'll be weird; modern systems still boot in 16 bits, bootstrap in 32 bit mode, then configure 64 bit. Unless UEFI fixed that madness?
- amluto 10y agoLinux should be immune simply because it doesn't use VME.
- zAy0LfpBZLC8mAC 10y agoI think dosemu does?
- amluto 10y agoDOSEMU uses virtual 8086 mode but not VME. The Linux kernel never bothered implementing VME.
- jandrese 10y agoWhat if you run DOS in a Virtual container though?
- johncolanduoni 10y agoWindows doesn't use it either. It's not possible to use it on a processor running in long mode except within a virtual machine (or by putting the processor into actual protected mode).
- frik 10y agoYou can use 16 bit Win 3.1 apps on 64 bit Linux with Wine.
- KenoFischer 10y agoYeah, modern CPUs have tons of bugs in the obscure corners of the architecture. The x86 boot process is an amazing amalgamation of all the legacy CPUs of the past two decades. This does seem fixable in microcode though, so presumably they'll just do that. I very much agree with the other comments though that at some point we should just get rid of all of that junk and use software emulation.
- sneak 10y agoI misread VME as VMX at first. Totally different.
- namuol 10y ago> As incredible as it is, Ryzen has buggy VME implementation; specifically, the INT instruction is known to misbehave in V86 mode with VME enabled when the given vector is redirected It's much more incredible to me that our computers work, at all.
- api 10y agoIn other news, crank-to-start mode is broken on the Tesla Model S.
- userbinator 10y agoAs incredible as it is, Ryzen has buggy VME implementation What I find more incredible is that this bug could get by without being noticed. A CPU literally has billions of possible regression tests --- all the world's existing software --- and of everyone working on the project, not a single one thought to try some older software (XP/2k3 is not even that old, as far as x86 compatibility is concerned) to see if it worked? This is an old feature too, meaning it should've been well-characterised by now. I'm particularly surprised that FreeDOS is affected, since it's commonly used as a minimal "non-OS" OS for running things like low-level diagnostics and debugging of hardware. This begs the question: if old features are this broken, what about the new ones (for which there is far less software available to test them with)? I think the most recently discovered one was https://news.ycombinator.com/item?id=13924192 https://news.ycombinator.com/item?id=13924192
- nine_k 10y agoOld features, especially this old, fossil-level old, are just not used in real life. Modern software never enters this ancient mode for any reason. Ancient software is emulated in software again, e.g. in DOSbox. New features are actively used, and thus actively tested. They are likely much less broken than disused old ones.
- qb45 10y agoDOSBox can't run various firmware update and low-level hardware diagnostics tools that are still used in real life under DOS running on bare metal. And Windows XP might be out of support but it still is used in some places too. And even if it wasn't, somebody could still think of using it as a test case to increase coverage. It would be extremely lame if some bug which crashes newer Windows in 0.1% of cases turned out to be trivially detectable in XP.
- nikanj 10y agoAs we have learned today, the UK NHS is very much still on XP.
- dis-sys 10y agoAMD should just drop the support for VME. There is no need to carry such baggage in 2017. If you need to run your legacy systems that require VME: buy yourself a processor designed in 2016.
- pja 10y agoAm I the only one who thinks that it’s not particularly incredible that a new CPU that implements the ridiculously complex (for good reasons, but still) x86 instruction set with all its historical baggage has bugs? Every x86 has had errata. Why should we expect Ryzen to be any different? “As incredible as it is...” seems a bit of an over-reaction to me.
- c0nfused 10y agoPeople think that the world a is a prefect black and white place where everything that works is prefect and everything else is garbage. Typically, the person reporting this sort of %^&* has an agenda, ranging from "fixit fixit fixit" to "I only buy the competition and so should you". The knowledge is good to have you just have if you are into doing crazy old things with new hardware. But the hyperbolic "the world is ending" bit you should just ignore.
- faragon 10y agoRyzen is amazing, I hope AMD fixes this via BIOS update for motherboards, so the updated microcode can be loaded before the OS boots.
- brownbat 10y agoRyzen 7s cannot seem to find their level, I wonder if this will drive the price down even further, or if it's too specific for anyone to notice. https://pcpartpicker.com/product/9Q98TW/amd-ryzen-7-1700x-34ghz-8-core-processor-yd170xbcaewof https://pcpartpicker.com/product/9Q98TW/amd-ryzen-7-1700x-34...
- Dolores12 10y agoThey will issue patch for processor that will fix it. Just another bug.