Then I created a Docker image with Linux, Gnome, and novnc so I can spin one up instantly with little resource overhead and control it from any web browser.
Correct me I'd I'm wrong, but with docker you're limited to the filesyatems and the image of the OS you're installing. If you need to experiment with the pre-OS boot events, can that even be accomplished with docker? E.g., trying out different GRUB settings, setting up LUKS with dropbear etc. I think those things require a VM.
Yeah, you are correct. Docker shares the kernel with the host operating system, it doesn't use hardware virtualization. That's why it's so fast and simple, but it also means it's not a traditional VM and thus comes with some limitations.
I go to the host folder I want to transfer files from and run ‘’’python3 -m http.server’’’. Then (I can’t remove if I use ‘’’ip a’’’ to find the IP address of the host or if I used mDNS), I use the guest web browser to download files.
I have two GPUs - an RX 550 hooked to the monitors and 580 for VMs. Until recently, once the VM shut down, the 580 was able to return to Linux and be used again via PRIME - no reset bug. It randomly stopped working and I’ve tried to debug it to fix the problem to little avail.
Besides VMWare it always seemed the easiest for me to quickly make a Windows VM or so. Everything else usually had more configuration steps. But that's been a while ago. There could very well have been easier tools available in the mean time. I never bothered to look.
I only ever used "permanent" virtualization once on my server. I think with Xen. But it didn't give me any benefits for my use case so I dropped it later on. Also probably at least ten years ago.
I used KVM with virt-manager for a long time. Even ran a gaming VM with GPU pass-through.
Then I created a Docker image with Linux, Gnome, and novnc so I can spin one up instantly with little resource overhead and control it from any web browser.
I use virt-manager, aka Virtual Machine Manager. Using this specifically because of the winapps for Linux repo has instructions on how to get Windows apps to run through the VM to be integrated in a Linux environment.
My biggest issue with VirtualBox is that I have to install OSes as if I'm actually installing them. There aren't any images (at least that I'm aware of) that can run with a command, like deploying an EC2.
Proxmox isn't really its own hypervisor. It combines a few common projects to make a OS. It is pretty much KVM with corosync for clustering.
With that being said it is a solid platform. Just keep in mind it is just standard Linux virtualization and for single nodes you can get the exact same setup easily on any Linux system.
Well, the exact same except for the frontend. It's arguably better than virt-manager imo. I wonder how hard it would be to get pve-manager running outside the OS.
Qemu+Kvm with virt-manager is my boy nowadays. But I'm not a heavy user of Vms, just experimented with this to build some Flatpak. But plan on trying out other distributions, just for science. It wasn't easy to figure out how to share a folder, and I could not get drag and drop or clipboard share to work. Still though, its faster than any other solution. I used VirtualBox in the past, which was easy to work with.
Virt manager for qemu. I use docker and distrobox for Linux distros
I recently managed to use my windows partition (for dual boot) as a disk for a qemu. I don't use it but really cool trick anyways. Tutorial here
Also it's not very healthy for windows since it is not designed for constant hardware changes. But idc all my apps are installed on D: so I can just reinstall it without thinking about it much
I tried doing tbe same thing as you on my separate windows ssd gives me a error on bootup and qemu/kvm won't let me boot from my vendor usb I tried only putting the isos and windows cannot find the ssd and hiren just gets a error
So far I’ve been fine with some Oracle Virtualbox and some using the VM Manager that was in my distro or maybe I downloaded it. It’s just called Virtual Machine Manager made by Red Hat. Libvirt.
Between those I’ve been able to do everything I have needed.
Currently virt-manager on top of qemu/kvm on Debian 12. It was the easiest to get to emulate a TPM on my ancient hardware (9ish years old, but still powerful).
I'm learning enough about the backend that I'm hoping to get off the Redhat maintained software and only use the qemu cli, maybe write my own monitor with rust-vmm when I learn enough rust to do so.
xcp-ng. except now everything is just containers on atomic fedora because it seems to fit my laziness better and doesn't require updating multiple vm os's
I tried using virt-manager+kvm to try some stuff out the other day but I failed to set-up some crucial things. Probably me being incompetent.
Not like virtualization is a big part of my life anyway. I just wanted to try some other distros and such without rebooting.
If I were to get serious about virtualization I'd need to build a new PC with a second GPU. Then I could stop dual-booting and do everything with VMs. But it'd only be worth it to get serious about learning how to virtualize stuff if I were to do that.
Raw qemu at the command line for the one I use on a daily basis (not recommended for the average user). VirtualBox if I need to spin something up quickly but don't expect to need to keep it past the current testing cycle.
Virtualbox is slow and the licensing for guest addons is nasty. It is proprietary of course and if a person in a company uses it unlicensed they will send the company a massive invoice.
I only need it for the very occasional testing of open-source software on Windows, using the precanned VM images provided by Microsoft (last I checked, they had none for qemu, or I would be using that instead). And if you're using software commercially, you'd better be damned sure you understand the licensing before setting up. A company of any size will have lawyers vetting that anyway.
In other words, I don't disagree with you, but those issues don't matter for my use case.
If I'm running another Linux distro that will be happy under the host kernel then I use LXD (or Incus) containers. Otherwise it's QEMU+KVM or occasionally Virtual Box.
They run a full distro rather than the minimalist that Docker containers use. You can also use them to run gui apps but that needs a bit more work to configure. I run Google Chrome sandboxed this way.
Replied to others with this but realized you won't get those notifications. I finally got around to releasing this, which is Debian in your browser via Docker: https://nowsci.com/webbian