qemu-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-discuss] kvm instance hangs at boot while starting with iSCSI


From: Josef Johansson
Subject: [Qemu-discuss] kvm instance hangs at boot while starting with iSCSI
Date: Wed, 13 Jun 2012 05:25:08 -0000 (UTC)

Hi,

I'm trying out QEMU 1.0 from debian sid, running this on the Ubuntu distro. 
While starting with iSCSI, it hangs with 100% CPU-usage.

backtrace
--

(gdb) backtrace
#0  0x00007f835425ed27 in ioctl () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f8357ea489c in iscsi_service () from 
/usr/lib/x86_64-linux-gnu/libiscsi.so.1
#2  0x00007f835885a521 in iscsi_process_read (arg=<optimized out>) at 
/build/josef-qemu-kvm_1.0+precise-ilait-amd64-12-amd64-HPZ0Ib/qemu-kvm-1.0+precise-ilait-amd64/block/iscsi.c:120
#3  0x00007f8358844832 in qemu_aio_wait () at 
/build/josef-qemu-kvm_1.0+precise-ilait-amd64-12-amd64-HPZ0Ib/qemu-kvm-1.0+precise-ilait-amd64/aio.c:210
#4  0x00007f835885a99d in iscsi_open (bs=0x7f835a46d700, 
filename=0x7f835a457ea0 
"iscsi://[2a01:2b0:301d:102::3]:3260/iqn.2010-08.se.ilait.storage1-2.pool10-images/10",
 flags=<optimized out>)
    at 
/build/josef-qemu-kvm_1.0+precise-ilait-amd64-12-amd64-HPZ0Ib/qemu-kvm-1.0+precise-ilait-amd64/block/iscsi.c:536
#5  0x00007f8358853505 in bdrv_open_common (bs=0x7f835a46d700, 
filename=0x7f835a457ea0 
"iscsi://[2a01:2b0:301d:102::3]:3260/iqn.2010-08.se.ilait.storage1-2.pool10-images/10",
 flags=<optimized out>, 
    drv=0x7f8358d82540) at 
/build/josef-qemu-kvm_1.0+precise-ilait-amd64-12-amd64-HPZ0Ib/qemu-kvm-1.0+precise-ilait-amd64/block.c:510
#6  0x00007f8358853686 in bdrv_file_open (pbs=0x7f835a46d5f8, 
filename=0x7f835a457ea0 
"iscsi://[2a01:2b0:301d:102::3]:3260/iqn.2010-08.se.ilait.storage1-2.pool10-images/10",
 flags=226)
    at 
/build/josef-qemu-kvm_1.0+precise-ilait-amd64-12-amd64-HPZ0Ib/qemu-kvm-1.0+precise-ilait-amd64/block.c:560
#7  0x00007f83588535f9 in bdrv_open_common (bs=0x7f835a46cd90, 
filename=0x7f835a457ea0 
"iscsi://[2a01:2b0:301d:102::3]:3260/iqn.2010-08.se.ilait.storage1-2.pool10-images/10",
 flags=<optimized out>, 
    drv=0x7f8358d83820) at 
/build/josef-qemu-kvm_1.0+precise-ilait-amd64-12-amd64-HPZ0Ib/qemu-kvm-1.0+precise-ilait-amd64/block.c:512
#8  0x00007f8358854207 in bdrv_open (bs=0x7f835a46cd90, filename=0x7f835a457ea0 
"iscsi://[2a01:2b0:301d:102::3]:3260/iqn.2010-08.se.ilait.storage1-2.pool10-images/10",
 flags=226, drv=<optimized out>)
    at 
/build/josef-qemu-kvm_1.0+precise-ilait-amd64-12-amd64-HPZ0Ib/qemu-kvm-1.0+precise-ilait-amd64/block.c:644
#9  0x00007f8358877926 in drive_init (opts=<optimized out>, 
default_to_scsi=<optimized out>) at 
/build/josef-qemu-kvm_1.0+precise-ilait-amd64-12-amd64-HPZ0Ib/qemu-kvm-1.0+precise-ilait-amd64/blockdev.c:536
#10 0x00007f83588d5d4b in drive_init_func (opts=<optimized out>, 
opaque=<optimized out>) at 
/build/josef-qemu-kvm_1.0+precise-ilait-amd64-12-amd64-HPZ0Ib/qemu-kvm-1.0+precise-ilait-amd64/vl.c:766
#11 0x00007f83588f6d72 in qemu_opts_foreach (list=<optimized out>, 
func=0x7f83588d5d40 <drive_init_func>, opaque=0x7f8358da97a0, 
abort_on_failure=<optimized out>)
    at 
/build/josef-qemu-kvm_1.0+precise-ilait-amd64-12-amd64-HPZ0Ib/qemu-kvm-1.0+precise-ilait-amd64/qemu-option.c:1002
#12 0x00007f835883edb7 in main (argc=<optimized out>, argv=<optimized out>, 
envp=<optimized out>) at 
/build/josef-qemu-kvm_1.0+precise-ilait-amd64-12-amd64-HPZ0Ib/qemu-kvm-1.0+precise-ilait-amd64/vl.c:3305
--

I'm running kvm with
kvm -name xxxxx -m 1024 -smp threads=1 -M pc -vnc 
[xxxx:xxxx:xxxx:xxxx::xx:xxxx]:0 -k sv -qmp 
tcp:xxx.xxx.xxx:4444,server,wait=off -vga std -rtc base=localtime -uuid 
20ab0a40-c01c-012e-e943-52540033c845 -daemonize -enable-kvm -nodefconfig 
-nodefaults -usb -device usb-tablet,id=input0 -device 
virtio-net-pci,addr=0x1f,netdev=n584.1003811,mac=54:52:00:01:88:1D -netdev 
tap,id=n584.1003811,ifname=584.1003811 -drive 
file=iscsi://[xxxx:xxxx:xxxx::3]:3260/iqn.2010-08.xx.xxx.xxxxxxx.pool10-images/10,if=none,id=drive-virtio-disk0,boot=on,cache=none,aio=native,format=raw
 -device virtio-blk-pci,drive=drive-virtio-disk0,id=virtio-disk0

Is there any thing I could try to fix this?

Regards,
Josef



reply via email to

[Prev in Thread] Current Thread [Next in Thread]