Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Topic on Talk:Virtualization

This page shows the changes between two versions of a post by Mirh in the topic "Different levels of virtualization" on Talk:Virtualization. You can see other versions of this post at its history page.
Line 7: Line 7:
 
As a fun fact this [https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/software_hardware_tech_x86_virt.pdf#page=4 could not] have been used on Intel CPUs to virtualize 64 bit efficiently. And since VirtualBox 6.1 and Workstation 14 it is not even supported anymore.  
 
As a fun fact this [https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/software_hardware_tech_x86_virt.pdf#page=4 could not] have been used on Intel CPUs to virtualize 64 bit efficiently. And since VirtualBox 6.1 and Workstation 14 it is not even supported anymore.  
  
−
Thankfully between 2005 and 2006 Intel and AMD made trap-and-emulate possible in hardware, and that's what VT-X and AMD-V are all about eventually. It is more about lessening the burden to have a smart hypervisor (and perhaps some edge case) [https://www.vmware.com/pdf/asplos235_adams.pdf than] performance though. And for historical reason, I'm not sure if solutions other than VMware's ever supported "64 bit at all" without it. It is also needed for 64/32 and 32/64 bit mixed host and guests (KVM doesn't support the latter [https://www.mail-archive.com/search?l=qemu-devel@nongnu.org&q=subject:%22<nowiki>[</nowiki>Bug+596106\<nowiki>]</nowiki>%22&o=oldest&f=1 for reasons])
+
Thankfully between 2005 and 2006 Intel and AMD made trap-and-emulate possible in hardware, and that's what VT-X and AMD-V are all about eventually. It is more about lessening the burden to have a smart hypervisor (and perhaps some edge case) [https://www.vmware.com/pdf/asplos235_adams.pdf than] performance though. And for historical reason, I'm not sure if solutions other than VMware's ever supported "64 bit at all" without it. It is also needed for 64/32 and 32/64 bit mixed host and guests (KVM doesn't support the latter [https://www.mail-archive.com/search?l=qemu-devel@nongnu.org&q=subject:%22%5BBug+596106\%5D%22&o=oldest&f=1 for reasons])
  
 
Note: when [https://web.archive.org/web/20080726233057/http://blogs.msdn.com/virtual_pc_guy/archive/2008/05/07/it-doesn-t-feel-like-a-hypervisor-to-me.aspx Hyper-V] is enabled, it pretends "Hardware Virtual Machine"s not to be supported.  
 
Note: when [https://web.archive.org/web/20080726233057/http://blogs.msdn.com/virtual_pc_guy/archive/2008/05/07/it-doesn-t-feel-like-a-hypervisor-to-me.aspx Hyper-V] is enabled, it pretends "Hardware Virtual Machine"s not to be supported.