On Thu, 16 May 2019 18:18:09 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
On 05/16/2019 04:49 PM, Dave Howorth wrote:
I have no idea what that means. Is there a set of instructions somewhere that's suitable for a noob to do what I want? Alternatively, can somebody tell me what the error means and what I need to do to fix it?
I've always gone through the process manually and have had good success, though admittedly, I'm have never spent the time to fully learn all aspect of KVM/QEMU to be able to tweak my VM's to what I get by default with vbox (which can essentially act as a front-end to QEMU)
Two very good links that got me though the process were:
https://wiki.archlinux.org/index.php/QEMU
and
https://wiki.archlinux.org/index.php/KVM (minimal page to confirm KVM support, the bulk is above in the QEMU page)
Hmm, I guess =y means the module is built-in and =m means it is dynamically loadable? And lsmod only lists those that are dynamically loaded? In which case the KVM stuff looks OK but the VIRTIO stuff doesn't: $ zgrep CONFIG_KVM /proc/config.gz CONFIG_KVM_GUEST=y # CONFIG_KVM_DEBUG_FS is not set CONFIG_KVM_MMIO=y CONFIG_KVM_ASYNC_PF=y CONFIG_KVM_VFIO=y CONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=y CONFIG_KVM_COMPAT=y CONFIG_KVM=m CONFIG_KVM_INTEL=m CONFIG_KVM_AMD=m CONFIG_KVM_AMD_SEV=y CONFIG_KVM_MMU_AUDIT=y $ lsmod | grep kvm kvm_intel 233472 0 kvm 704512 1 kvm_intel irqbypass 16384 1 kvm $ zgrep VIRTIO /proc/config.gz CONFIG_BLK_MQ_VIRTIO=y CONFIG_VIRTIO_VSOCKETS=m CONFIG_VIRTIO_VSOCKETS_COMMON=m CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m # CONFIG_VIRTIO_BLK_SCSI is not set CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_DRM_VIRTIO_GPU=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_PCI_LEGACY=y CONFIG_VIRTIO_BALLOON=m CONFIG_VIRTIO_INPUT=m CONFIG_VIRTIO_MMIO=m # CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES is not set CONFIG_CRYPTO_DEV_VIRTIO=m $ lsmod | grep virtio $ Not sure what that implies or why it wouldn't have been installed/set up by YaST and also complained about by virt-manager? Nor what to do about it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org