Taking the plunge with QEMU; couple of questions...
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Quick question: My understanding is that, to build QEMU-KVM, I need QEMU installed too -- at least the versions from Slackbuilds.org. Is that no longer the case?
Regards,
Never has been. qemu-kvm is a standalone application which incorporates some patches / added code to qemu to allow it access to kvm.
From the read me of SBo's qemu-kvm
Quote:
KVM (Kernel-based Virtual Machine) is a full virtualization solution
for Linux on x86 hardware containing virtualization extensions
(Intel VT or AMD-V). KVM requires QEMU-KVM to create and run virtual
machines (e.g. Windows, Linux, BSD) under full system emulation or user
mode emulation. QEMU-KVM is a slightly modified QEMU designed to work
with KVM kernel modules.
My understanding is that, to build QEMU-KVM, I need QEMU installed too -- at least the versions from Slackbuilds.org. Is that no longer the case?
It never was the case that QEMU was required for QEMU-KVM. In order for the KVM project to release their changes in a timely manner they have had to continue to provide a modified QEMU which is named QEMU-KVM.
The goal is for QEMU to incorporate all the changes in QEMU-KVM so that one package would rule them all but it just hasn't happened yet.
I got confused with KVM. From the KVM Slackbuild page/readme (13.0 respository):
Quote:
KVM (Kernel-based Virtual Machine) is a full virtualization solution
for Linux on x86 hardware containing virtualization extensions (Intel VT
or AMD-V). It consists of a loadable kernel module, kvm.ko, that provides
the core virtualization infrastructure and a processor specific module,
kvm-intel.ko or kvm-amd.ko. KVM also requires a modified QEMU although
work is underway to get the required changes upstream.
I know now that the "modified QEMU" refers to QEMU-KVM; at least I think that's correct.
So it looks like I can uninstall the base QEMU and just run QEMU-KVM.
Do/did I need to install the KVM package to use QEMU-KVM?
The goal is for QEMU to incorporate all the changes in QEMU-KVM so that one package would rule them all but it just hasn't happened yet.
That makes it a lot clearer.
For what it's worth: I went from being a complete newbie at virtualization to having succesfully set up two separate distros in VMs in the course of two evening's work. The combination of Eric's wiki post on QEMU and the very helpful posts here are absolutely invaluable.
Fair play to the original poster, good persistence.
I saw some comments earlier on in this thread that i wanted to correct for the record.
QEMU supports the same graphics driver used in VMware. Which gives it DirectX9c.
My understanding of the virtual environment is that there are two techiques. 1) to emulate and process on a general processing thread (ie, CPU) 2) create a hole through the DOM and allow direct access.
the 2nd option is not possible with Graphics cards because they are too proprietary, closed source and used by the host system. Due to their VGA BIOS. It is however possible with generic/universal devices such as USB.
so the first option is used for graphics. Although extensions for DirectX9c are supported they are computed on your hosts CPU. This can not provide the same graphical power compared to your hosts middling nvidia card. This is the same for VMWare as it is for QEMU
vt-X allows guest systems direct access to the hosts CPU. which gives near very near native performance....
vt-d allows guest systems direct access to any device on the PCI/PCI express bus direct access.... QEMU appears to already be looking at patches to allow direct access to graphics cards.
My understanding of the virtual environment is that there are two techiques. 1) to emulate and process on a general processing thread (ie, CPU) 2) create a hole through the DOM and allow direct access.
the 2nd option is not possible with Graphics cards because they are too proprietary, closed source and used by the host system. Due to their VGA BIOS. It is however possible with generic/universal devices such as USB.
so the first option is used for graphics. Although extensions for DirectX9c are supported they are computed on your hosts CPU. This can not provide the same graphical power compared to your hosts middling nvidia card. This is the same for VMWare as it is for QEMU
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.