On Wednesday, 8 January 2020 11:46:52 UTC, Claudia wrote:
> ...Xen uses QEMU just to emulate virtual hardware devices for HVMs, not
> for the actual virtualization. "Normal" Qemu is actually Qemu/KVM, which is
> not supported on Xen as far as I know. The next best thing is to create an
> HVM, see
> https://www.qubes-os.org/doc/standalone-and-hvm/#installing-an-os-in-an-hvm
Here is a bit more background -- not strictly necessary to your immediate Q
For Linux users, "normal" QEMU is indeed Qemu/KVM.
However, some QEMU fans would probably argue that the definitive QEMU is
the version that emulates everything. Obviously that leads to a slow
running system, but will certainly run in an HVM. QEMU/KVM leverages the
Linux kernel to run as much of the code as possible directly (ie on bare
metal or in an HVM).
There is also a Windows variant (iirr called KQEMU) which runs on Windows
(but only after you install the KQEMU drivers).
> qemu-img-xen is used for formatting image files or block devices for VMs.
> qemu-nbd-xen is for network block devices, though I'm not sure if/how
> they're used in Qubes.
>
Most, or maybe all, the programs whise name begins qemu-... are utilities
borrowed from the QEMU project, rather than actually part of the QEMU
emulator itself. Why write a utility when the QEMU team already did what
you want?
In fact, both KVM and XEN use QEMU code internally, but not in a way that
you can easily leverage for what you are trying to do. So too does
VirtualBox, which means Oracle cannot make it closed source without
re-inventing a lot of QEMU wheels
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/51a4add5-ed79-46fa-9171-f70d7c86eb3e%40googlegroups.com.
