Re: QEMU-kvm installation a dependency hell?
> Am 13.03.2022 um 22:10 schrieb Samuel Sieb : > > ... > qemu-kvm is a metapackage which points to qemu-system-x86. That is also a > metapackage which brings in all the qemu packages including the graphical > parts. If you don't want that, then you have to install just the packages > that you need. > > "dnf repoquery --requires qemu-system-x86" will give you the list of included > packages. I found, fortunately there is a package qemu-system-x86-core as well. It installs friendly 21 packages on top of a fresh default Fedora Server Edition, and without any guy stuff. Thanks for the hint. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: QEMU-kvm installation a dependency hell?
> There's not a companion libvirt-daemon-kvm-core though, so I think you > just have to pick and chose the libvirt-daemon-* packages you want > manually (libvirt-daemon-kvm is another virtual package that pulls in, > among other things, the qemu-kvm virtual package). > > So, a package set that might be more what you are looking for would be: > > qemu-kvm-core > libvirt-daemon-driver-qemu > libvirt-daemon-driver-network > libvirt-daemon-driver-storage-core > virt-install I did some testing and found that set of packages work basically fine on a Fedora Server Edition, besides (a) default network is not defined. After defining it manually everything work fine (b) Daemon virtstoraged is installed (part of libvirt-daemon-driver-storage-core) but is not enabled after installation so it is not active after reboot. When manually enabled everything works fine after reboot (c) virsh console vm1 doesn't work with a vm I created earlier. There is a console (I get the message Connected to domain 'vm1' \ Escape character is ...), but nothing is displayed. I imported the vm using virt-install --name vm1\ --memory 2048 --cpu host --vcpus 3 --graphics none\ --os-type linux --os-variant fedora35\ --import \ --graphics none \ --disk /var/lib/libvirt/images/vm1.qcow2,format=qcow2,bus=virtio \ --network type=direct,source=enp1s0,source_mode=bridge,model=virtio \ --network bridge=virbr0,model=virtio (That's the same way I created the vom previously, if I remember correctly) Any idea how I may get these things working? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: QEMU-kvm installation a dependency hell?
> Am 13.03.2022 um 22:20 schrieb Chris Adams : > > Once upon a time, Peter Boy said: >> ... >> I’m wondering, why I need Wayland or X11 etc for kernel virtualization and >> running virtual machines? It turns my headless server into a graphical >> workstation. It installs software that I don't need for running a headless >> server, and don't want there. > > If you install qemu-kvm, that includes GUI console support, so you get a > bigger set of dependencies (qemu-kvm is a virtual package that just > pulls in all the necessary things). You can instead install > qemu-kvm-core to get a more "headless" setup. I think that some of the > graphical libraries are related to supporting graphical VMs (e.g. > Windows), but I'm not sure. > > There's not a companion libvirt-daemon-kvm-core though, so I think you > just have to pick and chose the libvirt-daemon-* packages you want > manually (libvirt-daemon-kvm is another virtual package that pulls in, > among other things, the qemu-kvm virtual package). Folks, thanks for all the information. It didn't occur to me that the management software, and then as a GUI, would be installed at the same time in one step. I always saw that as a separate area, and I always used virtual manager remotely. > So, a package set that might be more what you are looking for would be: > > qemu-kvm-core > libvirt-daemon-driver-qemu > libvirt-daemon-driver-network > libvirt-daemon-driver-storage-core > virt-install That looks way better, indeed. I'm just trying to figure out if this is all I need or what else is missing. > There are two comps groups for virtualization: Virtualization and > Headless Virtualization, but the "headless" group still pulls in the > full qemu-kvm and libvirt-daemon-kvm virtual packages, so a bigger > footprint with a bunch of GUI support. I just managed to find the virtualization-headless group, it’s hidden. Do you know why it is? Maybe we could create a group virtualization-really-headless and make it public. :-) Thanks for the quick info. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: QEMU-kvm installation a dependency hell?
Once upon a time, Peter Boy said: > I just checked installation of qemu-kvm & libvirt & virt-install on a Fedora > Server Edition, that is a headless server. It installed 338 packages / 158 > mb including poppler, mesa, wayland, libX11, gtk3, cairo and a lot of > additional graphic related software. > > I’m wondering, why I need Wayland or X11 etc for kernel virtualization and > running virtual machines? It turns my headless server into a graphical > workstation. It installs software that I don't need for running a headless > server, and don't want there. If you install qemu-kvm, that includes GUI console support, so you get a bigger set of dependencies (qemu-kvm is a virtual package that just pulls in all the necessary things). You can instead install qemu-kvm-core to get a more "headless" setup. I think that some of the graphical libraries are related to supporting graphical VMs (e.g. Windows), but I'm not sure. There's not a companion libvirt-daemon-kvm-core though, so I think you just have to pick and chose the libvirt-daemon-* packages you want manually (libvirt-daemon-kvm is another virtual package that pulls in, among other things, the qemu-kvm virtual package). So, a package set that might be more what you are looking for would be: qemu-kvm-core libvirt-daemon-driver-qemu libvirt-daemon-driver-network libvirt-daemon-driver-storage-core virt-install There are two comps groups for virtualization: Virtualization and Headless Virtualization, but the "headless" group still pulls in the full qemu-kvm and libvirt-daemon-kvm virtual packages, so a bigger footprint with a bunch of GUI support. The only difference for the "headless" group is that it doesn't include the desktop GUI VM management tools virt-manager and virt-viewer -- Chris Adams ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: QEMU-kvm installation a dependency hell?
On 3/13/22 13:45, Peter Boy wrote: I just checked installation of qemu-kvm & libvirt & virt-install on a Fedora Server Edition, that is a headless server. It installed 338 packages / 158 mb including poppler, mesa, wayland, libX11, gtk3, cairo and a lot of additional graphic related software. I’m wondering, why I need Wayland or X11 etc for kernel virtualization and running virtual machines? It turns my headless server into a graphical workstation. It installs software that I don't need for running a headless server, and don't want there. If I install the same combo on a Debian / Ubuntu headless Server it installs about 40 packages / 20 mb. I know, the packages are not the same, but Debian/Ubunt doesn’t need X11, poppler, mesa, etc. for virtualization on a headless server. Can't we do the same? qemu-kvm is a metapackage which points to qemu-system-x86. That is also a metapackage which brings in all the qemu packages including the graphical parts. If you don't want that, then you have to install just the packages that you need. "dnf repoquery --requires qemu-system-x86" will give you the list of included packages. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: QEMU-kvm installation a dependency hell?
On Sun, Mar 13, 2022 at 4:45 PM Peter Boy wrote: > > I just checked installation of qemu-kvm & libvirt & virt-install on a Fedora > Server Edition, that is a headless server. It installed 338 packages / 158 > mb including poppler, mesa, wayland, libX11, gtk3, cairo and a lot of > additional graphic related software. > > I’m wondering, why I need Wayland or X11 etc for kernel virtualization and > running virtual machines? It turns my headless server into a graphical > workstation. It installs software that I don't need for running a headless > server, and don't want there. > qemu-kvm installs the full graphical virtualization stack. You want qemu-kvm-core to get a subset without the graphical UI. Those libraries are required for the QEMU GUI to work, which people *do* use. It also allows QEMU to work properly as an X11/Wayland client app in a desktop environment. > If I install the same combo on a Debian / Ubuntu headless Server it installs > about 40 packages / 20 mb. I know, the packages are not the same, but > Debian/Ubunt doesn’t need X11, poppler, mesa, etc. for virtualization on a > headless server. Can't we do the same? > By default, Debian does the same thing. The qemu-system-x86 package recommends the qemu-system-gui package, which pulls in that stuff. This is not "dependency hell". "Dependency hell" is a *very* specific thing, and this isn't it. -- 真実はいつも一つ!/ Always, there's only one truth! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
QEMU-kvm installation a dependency hell?
I just checked installation of qemu-kvm & libvirt & virt-install on a Fedora Server Edition, that is a headless server. It installed 338 packages / 158 mb including poppler, mesa, wayland, libX11, gtk3, cairo and a lot of additional graphic related software. I’m wondering, why I need Wayland or X11 etc for kernel virtualization and running virtual machines? It turns my headless server into a graphical workstation. It installs software that I don't need for running a headless server, and don't want there. If I install the same combo on a Debian / Ubuntu headless Server it installs about 40 packages / 20 mb. I know, the packages are not the same, but Debian/Ubunt doesn’t need X11, poppler, mesa, etc. for virtualization on a headless server. Can't we do the same? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure