Search the Community
Showing results for tags 'kvm'.
Found 2 results
-
Wouldn't it be nice to have all the virtualization/emulation software in one kit instead it being all over the place? It would make testing and deploying virtualization technologies much easier. Most of the virtualization software is in nokit. LXC and LXD are in core-kit. Some libvirt python bindings are in python-kit, and virtualbox guest additions are in xorg-kit. virtualzation pkgs: app-emulation/libvirt::nokit app-emulation/qemu::nokit app-emulation/lxc::core-kit app-emulation/lxd::core-kit app-emulation/virtualbox::nokit app-emulation/virtualbox-bin::nokit app-emulation/xen::nokit virtualization tools: app-emulation/virt-manager::nokit app-emulation/virt-viewer::nokit app-emulation/virtio-win::nokit app-emulation/virtualbox-guest-additions::xorg-kit app-emulation/open-vm-tools::nokit dev-python/libvirt-python::python-kit cloud related virtualization software: app-emulation/docker::nokit app-emulation/cloud-init::nokit app-emulation/containerd::nokit hard emulators: app-emulation/bochs::nokit app-emulation/armv8-fast-model::nokit app-emulation/edumips64::nokit app-emulation/vmips::nokit I'm sure I forgot many packages, the open-vz kernel sources, probably more emulators, and more stuff related to docker, but this is just an idea how to consolidate the virtualization packages into one kit.
-
So AQEMU is complaining about me not having qemu installed, which is wrong because it's a dependency. >This VM uses an emulator "QEMU" which is not installed in the system. >The work of the VM is not possible! I've added myself to the kvm group, which didn't change anything and I've tried rebooting to see if some kernel module needed loading or something, which was apparently not the case.
