I don't know what this achieves over booting up a VM of an old OS to run your programs.
[deleted]
Wine on Windows 10
11–20 of 135 posts
Re: Wine on Windows 10
#12This can be very helpful in the future for playing games with strange 16-bit-mixed-with-32-bit installers that fail to run properly on modern Windows, even 32-bit versions. I hope WSL2 comes out soon. Now that installing wine in Linux on windows is possible, the next step becomes clear. We must compile and run cygwin on wine in Linux on Windows.
This project is only completed when you can recursively keep doing this forever, without it ever breaking.
Any CPU can only have one hypervisor running at a time. Thus the recursion stops pretty quick.
Re: Wine on Windows 10
#13Earlier quoted context omitted.
This project is only completed when you can recursively keep doing this forever, without it ever breaking.
Any CPU can only have one hypervisor running at a time. Thus the recursion stops pretty quick.
Cygwin and Wine don't use virtualization. And even if they did, most hypervisors support nesting these days.
Re: Wine on Windows 10
#14I don't know what this achieves over booting up a VM of an old OS to run your programs.
WSL is VM. So it's pretty pointless to run application on Linux VM emulating WinAPI, indeed. But at least you don't need to care about licenses, that might be one reason.
Re: Wine on Windows 10
#15Earlier quoted context omitted.
This project is only completed when you can recursively keep doing this forever, without it ever breaking.
Any CPU can only have one hypervisor running at a time. Thus the recursion stops pretty quick.
Why? There's only one hypervisor involved for the initial "wine" environment.
Re: Wine on Windows 10
#16Earlier quoted context omitted.
This project is only completed when you can recursively keep doing this forever, without it ever breaking.
Any CPU can only have one hypervisor running at a time. Thus the recursion stops pretty quick.
Actually most modern hypervisors allow nested virtualization.
Re: Wine on Windows 10
#17I don't know what this achieves over booting up a VM of an old OS to run your programs.
First and foremost, security. Also convenience - no need to mess around with shared folders, NAT-based VM networking, OS updates, user accounts/passwords etc.
Re: Wine on Windows 10
#18I don't know what this achieves over booting up a VM of an old OS to run your programs.
WSL is VM. So it's pretty pointless to run application on Linux VM emulating WinAPI, indeed. But at least you don't need to care about licenses, that might be one reason.
WSL is not a VM. The upcoming WSL2 might be, though.
Re: Wine on Windows 10
#19Earlier quoted context omitted.
This project is only completed when you can recursively keep doing this forever, without it ever breaking.
Any CPU can only have one hypervisor running at a time. Thus the recursion stops pretty quick.
Well, yes and no. On modern enough hardware you can do nested virtualisation, so you can run kvm in esxi on hyper-v if you want. Not that it's very usefull, but it is a fun weekend project nonetheless.
Re: Wine on Windows 10
#20Earlier quoted context omitted.
This project is only completed when you can recursively keep doing this forever, without it ever breaking.
Any CPU can only have one hypervisor running at a time. Thus the recursion stops pretty quick.
Intel and AMD CPUs have supported hardware-accelerated nested virtualisation for quite some time now.
https://docs.microsoft.com/en-us/virtualization/hyper-v-on-w...
https://www.redhat.com/en/blog/inception-how-usable-are-nest...