Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I dumped it after realizing Xen does its damndest in preventing you from hiding VM attributes from Guest OSes.

Proxmox uses KVM, and is easy to configure a VM to make the guest think it's on bare metal.

In the proprietary software space, a LOT of things run badly or refuse to run, or license stupidity with a guest OS. So for me, spoofing bare metal is an essential part of running ilk like Windows and proprietary apps. And also, school remote testing garbage.

 help



Doesn't that preclude paravirtualization drivers? Seems like a major tradeoff for daily driver desktop stuff.

Xen prevents modifying ACPI data.

It also passes obvious "Xen emulated drive", and similar for all hardware interfaces.

Passes CPUID.

Can't stop any of this with Qubes/Xen. But is trivial with Proxmox/KVM.

Honestly, I wish there was a Qubes/KVM variant. It would fix every complaint, and enable running potentially malicious software (MS windows) and lie to it regarding hardware interfaces.


> Honestly, I wish there was a Qubes/KVM variant.

Relayed Issue: https://github.com/QubesOS/qubes-issues/issues/7051





Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: