qemu-discuss
[Top][All Lists]
Advanced

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

[Qemu-discuss] How to debug blocked QEMU run


From: Ilya Katsnelson
Subject: [Qemu-discuss] How to debug blocked QEMU run
Date: Wed, 6 Jan 2016 04:55:28 +0000

Hello:


I'm trying to test my ARM build on QEMU from Yocto script.

The command line is this:


runqemu qemuarm qemuparams="-D /tmp/a.log -smp cpus=1 -nographic -serial mon:stdio -append 'console=ttyS0'" ./tmp/deploy/images/vcm4-qemu/zImage-vcm4-qemu.bin ./tmp/deploy/images/vcm4-qemu/core-image-minimal-vcm4-qemu.ext4


The core rootfs is correct because I've tested it with a different kernel. With the different kernel the simulator comes up fine, but with this one it just tits there at this output:


pirate-builds:~/work/tmp/poky/build$ runqemu qemuarm qemuparams="-D /tmp/a.log -smp cpus=1 -nographic -serial mon:stdio -append 'console=ttyS0'" ./tmp/deploy/images/vcm4-qemu/zImage-vcm4-qemu.bin ./tmp/deploy/images/vcm4-qemu/core-image-minimal-vcm4-qemu.ext4 
Please use simplified serial or kvm options instead

Continuing with the following parameters:
KERNEL: [./tmp/deploy/images/vcm4-qemu/zImage-vcm4-qemu.bin]
ROOTFS: [~/work/tmp/poky/build/tmp/deploy/images/vcm4-qemu/core-image-minimal-vcm4-qemu-20160106020750.rootfs.ext4]
FSTYPE: [ext4]
Acquiring lockfile for tap0...
Using preconfigured tap device 'tap0'
If this is not intended, touch /tmp/qemu-tap-locks/tap0.skip to make runqemu skip tap0.
-net nic,model=virtio -net tap,vlan=0,ifname=tap0,script=no,downscript=no -M versatilepb -drive file=~/work/tmp/poky/build/tmp/deploy/images/vcm4-qemu/core-image-minimal-vcm4-qemu-20160106020750.rootfs.ext4,if=virtio,format=raw -no-reboot -show-cursor -usb -usbdevice wacom-tablet   -D /tmp/a.log -smp cpus=1 -nographic -serial mon:stdio -append 'console=ttyS0' -m 128
Running qemu-system-arm...
~/work/tmp/poky/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-arm -kernel ./tmp/deploy/images/vcm4-qemu/zImage-vcm4-qemu.bin -net nic,model=virtio -net tap,vlan=0,ifname=tap0,script=no,downscript=no -M versatilepb -drive file=~/work/tmp/poky/build/tmp/deploy/images/vcm4-qemu/core-image-minimal-vcm4-qemu-20160106020750.rootfs.ext4,if=virtio,format=raw -no-reboot -show-cursor -usb -usbdevice wacom-tablet -no-reboot -D /tmp/a.log -smp cpus=1 -nographic -serial mon:stdio -append 'console=ttyS0' -m 128 -serial null --append "root=/dev/vda rw console=ttyAMA0,115200 console=tty ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=128M highres=off rootfstype=ext4 "
qemu-system-arm: unable to init msix vectors to 3
qemu-system-arm: -drive file=~/work/tmp/poky/build/tmp/deploy/images/vcm4-qemu/core-image-minimal-vcm4-qemu-20160106020750.rootfs.ext4,if=virtio,format=raw: unable to init msix vectors to 2

Is there any way to know what is really going on in QEMU? To see what it is really unhappy about? Otherwise I'm flying blind and can't really debug the problem.


Thank you,

-Ilya.





reply via email to

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