U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
(1/6)
If you’re a #hypervisor developer, please pay attention to these tweets as it wastes a significant amount of time for me to find the cause and fix the bug and I see the same bug in many of the open source hypervisors available on GitHub.pic.twitter.com/Ulo3cgAskE
(2/6) As you know EXIT_REASON_CR_ACCESS is one of the reasons that might cause VM-Exit (Especially if you’re subject to 1-setting of CRs in your VMCS). Hypervisors used to save all the general purpose registers every time a VM-Exit occurs and then restore it at the next VMRESUME.
(3/6) Almost every case that I see is ignoring RSP and save some trash instead of it, that’s because RSP of guest is already saved in GUEST_RSP in VMCS and after VMRESUME it’s loaded automatically and you know, our current RSP is invalid (it’s host RSP).pic.twitter.com/wipLBctazD
(4/6) But seems that in Windows 10 1903, Microsoft compiler decides to use MOV Cr3,RSP (I didn’t see this in Windows before.) and as you saved trash instead of RSP (or you saved RSP of host which is not valid.) then you change CR3 to an invalid value and it silently crashespic.twitter.com/W8zl7y3UrS
(5/6) with TRIPLE FAULT VM-Exit. It won’t give you the exact error. This bug occurs every time I loaded my hypervisor driver and start my VMM so try to fix it guys. Here is mine :pic.twitter.com/PvaBl6sjt9
(6/6)
I also updated Hypervisor From Scratch (Part 6) driver, I test it and it works in a Windows 10 1903 + VMWare Workstation (nested virtualization).
Thanks to @standa_t and @gerhart_x for their help.https://github.com/SinaKarvandi/Hypervisor-From-Scratch …
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
