I use VMs (virtual machines) almost every day. I use them for work and for learning more about Linux. Also a great way to harmlessly experiment with an operating system.
In the past I have used VMWare and more recently VirtualBox (Vbox), but this past year, I have begun using QEMU/KVM. There's a learning curve for sure, but I have managed to convert 6 VBox VMs of various operating systems to QEMU using Virtual Machine Manager.
Part of the reason for the transition away from VBox is the performance isn't great and the dkms packages and other requirements a bit of a nuisance. QEMU seems more Linux integrated and performs WAY better. Also, one can configure hardware-pass through with QEMU but not with VBox (VMWare also allows this but it's not free in any sense of the word). I haven't yet needed or attempted hardware-pass through but I will someday figure that out.
I recently - as in this month - found and have begun attempting to use AQEMU rather than virt-manager. The bulk of my VM building has been done with VBox. AQEMU has a more familiar graphical interface like VBox whereas virt-manager is more textual. I wanted to try both. I built my first two VMs using AQEMU last week but I haven't figured out all I need to know yet.
For example, several of my work VMs require multiple monitors (displayed as separate windows). With VBox, you just select the number desired in the VM settings and launch. With virt-manager, you have to manually edit the XML file pertaining to the VM and then open the VM using "remote viewer" to see all the monitors. Kind of an annoying extra step. AQEMU has a GUI to enable multiple monitors but I haven't figured that out yet, so I;m not sure if it's easier or not.
Editing the XML in virt-manager seems more powerful and direct than using a pretty GUI, but also more dangerous because nothing is checking your syntax. I've broken a few VMs already. With my limited experience so far I feel like virt-manager is for a power user and AQEMU more friendly for a casual user.
The reason I most often use VMs other than for work is to test a new release or another OS or trouble shoot a problem. I used to test out a new software install or update, but now I use snapshots so I just go for it these days and roll back when it fails. It's really a good idea to have a VM of the same version of your current install so you can test a potential new PPA or system update or upgrade. It's really nice to be able to attempt something and just wipe the VM and start over when it fails.
I'd like to hear about your opinion, experiences, how or why you use VMs if you do, and of course questions and comments welcome.
In the past I have used VMWare and more recently VirtualBox (Vbox), but this past year, I have begun using QEMU/KVM. There's a learning curve for sure, but I have managed to convert 6 VBox VMs of various operating systems to QEMU using Virtual Machine Manager.
Part of the reason for the transition away from VBox is the performance isn't great and the dkms packages and other requirements a bit of a nuisance. QEMU seems more Linux integrated and performs WAY better. Also, one can configure hardware-pass through with QEMU but not with VBox (VMWare also allows this but it's not free in any sense of the word). I haven't yet needed or attempted hardware-pass through but I will someday figure that out.
I recently - as in this month - found and have begun attempting to use AQEMU rather than virt-manager. The bulk of my VM building has been done with VBox. AQEMU has a more familiar graphical interface like VBox whereas virt-manager is more textual. I wanted to try both. I built my first two VMs using AQEMU last week but I haven't figured out all I need to know yet.
For example, several of my work VMs require multiple monitors (displayed as separate windows). With VBox, you just select the number desired in the VM settings and launch. With virt-manager, you have to manually edit the XML file pertaining to the VM and then open the VM using "remote viewer" to see all the monitors. Kind of an annoying extra step. AQEMU has a GUI to enable multiple monitors but I haven't figured that out yet, so I;m not sure if it's easier or not.
Editing the XML in virt-manager seems more powerful and direct than using a pretty GUI, but also more dangerous because nothing is checking your syntax. I've broken a few VMs already. With my limited experience so far I feel like virt-manager is for a power user and AQEMU more friendly for a casual user.
The reason I most often use VMs other than for work is to test a new release or another OS or trouble shoot a problem. I used to test out a new software install or update, but now I use snapshots so I just go for it these days and roll back when it fails. It's really a good idea to have a VM of the same version of your current install so you can test a potential new PPA or system update or upgrade. It's really nice to be able to attempt something and just wipe the VM and start over when it fails.
I'd like to hear about your opinion, experiences, how or why you use VMs if you do, and of course questions and comments welcome.
Comment