You are not logged in.

#1 2011-09-21 18:57:53

Leonid.I
Member
From: Aethyr
Registered: 2009-03-22
Posts: 999

[qemu-kvm] virtio_blk (or virtio_pci) problem

I have several qemu-kvm VMs running arch i686  on an arch x86_64 host. All of the VMs run fine as long as I don't use virtio_{blk,pci} paravirtualized drivers. When these drivers are enabled (I added them to the MODULES array in mkinitcpio.conf and rebuilt the linux image), the guest boots OK and correctly recognizes the virtual hdd as /dev/vda1.

However, after a random amount of time the whole qemu-kvm crashes on the host with errno 134 (SIGABRT) and error message:

pthread_create failed: Resource temporarily unavailable

More precisely:

$ cat vm-start
#!/bin/bash

qemu-kvm -drive file=$1,if=virtio,boot=on -net nic,model=virtio \
	-net user,hostfwd=tcp:127.0.0.1:15000-:22 -vga vmware \
	-usbdevice tablet -device intel-hda -device hda-duplex -m 384
$
$ ./vm-start ./vm/arch-i686-raw 
pthread_create failed: Resource temporarily unavailable
./vm-start: line 5:  5305 Aborted
$ echo $?
134

I initially suspected this is due to my pam settings, but increasing "hard nproc" in limits.conf from 150 to 250 does not have any effect...

Any ideas how to fix this problem?.. Thanks.


Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd

Offline

Board footer

Powered by FluxBB