Hacker News Reader

This is perfect for gaming VM. Installing Windows in a VM requires an extra license. With Wine, I can install Linux in a VM and install Wine in it to run Windows games. Anything blows up in the VM can be rolled back.

View on HN

Maintaining several wineprefixes is trivial too. The wineprefix describes where wine installs the "drive_c" and other stuff. So essentially it's the "chroot" of wine. It's of course more secure to do so in a VM but I run several wineprefixes locally for convenience.

Are you sure that's going to work? I don't think you'll be able to take full advantage of your graphics hardware that way. (Last I checked, Virtualbox and friends refused to allocate more than 256MB of VRAM... so I could play Duck Game and no more.)

Good question.

I was thinking it'd be fun to benchmark an application running on Windows vs. that same application running on Wine running in the Ubuntu Userspace in Windows. I'd have to guess it'd be at least a few times slower.

That would make since, considering the overhead involved in translating the syscalls twice. It would be really interesting to see if/how the native Windows syscalls differed from the ones coming out of the Wine->WSL pipeline.

Not the latest games that stress the hardware. Mainly the games I download from the web that I don't trust to run outside of a sandbox.

Reply on news.ycombinator.com