[opensuse] KVM & Raspbian
I've never used virtual machines before but I want to bring up an instance of Raspbian. So I installed KVM with YaST and I downloaded https://downloads.raspberrypi.org/rpd_x86_latest and ran its checksum, so I know I got a good copy. I started virt-manager and selected File/New VM and got a dialog box/wizard which I clicked through. When I got to the end and clicked Finish it says: Unable to complete install: 'internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 12 Cannot allocate memory 2019-05-16T21:41:00.397990Z qemu-system-x86_64: failed to initialize KVM: Cannot allocate memory' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 2633, in _do_async_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 527, in start_install doboot, transient) File "/usr/share/virt-manager/virtinst/guest.py", line 463, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/lib64/python3.6/site-packages/libvirt.py", line 3659, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirt.libvirtError: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 12 Cannot allocate memory 2019-05-16T21:41:00.397990Z qemu-system-x86_64: failed to initialize KVM: Cannot allocate memory 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? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On Fri, 17 May 2019 11:19:29 +0100 Dave Howorth <dave@howorth.org.uk> wrote:
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?
snip
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.
Hmm, just before I gave up for now, I thought I'd try one more click. So I clicked on Finish in virt manager again, and this time instead of an error it's given me the Pi's boot screen! :) I've no idea why the result is different this time, but for now I'll just carry on ... Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/17/2019 06:15 AM, Dave Howorth wrote:
Hmm, just before I gave up for now, I thought I'd try one more click. So I clicked on Finish in virt manager again, and this time instead of an error it's given me the Pi's boot screen! :)
I've no idea why the result is different this time, but for now I'll just carry on ...
Cheers, Dave
We like to fool ourselves into believing computing is more a science than an art. Nonsense... you just were not holding your mouth right during your previous mouse-clicks on [Finish]. Case solved :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi, Am 16.05.19 um 23:49 schrieb Dave Howorth:
Unable to complete install: 'internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 12 Cannot allocate memory 2019-05-16T21:41:00.397990Z qemu-system-x86_64: failed to initialize KVM: Cannot allocate memory'
what host you have leap or tumbleweed? did you have additional repos activ so maybe some kvm/virtmanager parts are not from official repo? is libvirtd running? do you start virt-manager from console as user (you should do so)? i use kvm for everyday use (3kvm's) on tumbleweed with virtmanager (more or less standard settings) (without knowing details) never run in such a problem. simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 17 May 2019 08:00:54 +0200 Simon Becherer <simon@becherer.de> wrote:
Hi,
Am 16.05.19 um 23:49 schrieb Dave Howorth:
Unable to complete install: 'internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 12 Cannot allocate memory 2019-05-16T21:41:00.397990Z qemu-system-x86_64: failed to initialize KVM: Cannot allocate memory'
what host you have leap or tumbleweed?
What do you mean? $ uname -a Linux acer-suse 4.12.14-lp150.12.7-default #1 SMP Tue Jul 17 12:08:37 UTC 2018 (4804d19) x86_64 x86_64 x86_64 GNU/Linux
did you have additional repos activ so maybe some kvm/virtmanager parts are not from official repo?
Don't know. Which parts would I need to check and how would I do that?
is libvirtd running?
$ ps -fe | grep libvirtd root 3718 1 0 May16 ? 00:00:10 /usr/sbin/libvirtd --listen
do you start virt-manager from console as user (you should do so)?
Yes.
i use kvm for everyday use (3kvm's) on tumbleweed with virtmanager (more or less standard settings) (without knowing details) never run in such a problem.
simoN
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Dave Howorth -
David C. Rankin -
Simon Becherer