{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 The star\" 的问题《Does a Type 2 virtual host suffer the same limitat》','https://www.manongdao.com/q-1093020.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Does the host OS impose limitations on the guest OS for a Type 2 virtual host (i.e. VirtualBox)?
For example: In Ruby, creating a child process is as easy as making a call to fork. However, forking on windows is not supported and instead an entire process must be spawned for multithreaded.
As I understand, this is a limitation of the operating system and not the programming language. Will having Windows as the host OS force these restrictions on a linux guest OS?
How are commands given to the guest OS passed to the host OS?
Short answer: No
Longer answer:
A type-2 hypervisor such as VirtualBox emulates the entire hardware platform that the guest (such as Linux) runs on. As such, the guest OS does not actually call any host OS system calls, which allows the guest to bypass any limitations of the host OS (such as the
forking limitation on Windows).