On Thu, 29 Oct 2015 15:50:38 -0700 Andy Lutomirski <luto@xxxxxxxxxxxxxx> wrote: > Progress! After getting that sort-of-working, I figured out what was > wrong with my earlier command, and I got that working, too. Now I > get: > > qemu-system-s390x -fsdev > local,id=virtfs1,path=/,security_model=none,readonly -device > virtio-9p-ccw,fsdev=virtfs1,mount_tag=/dev/root -M s390-ccw-virtio > -nodefaults -device sclpconsole,chardev=console -parallel none -net > none -echr 1 -serial none -chardev stdio,id=console,signal=off,mux=on > -serial chardev:console -mon chardev=console -vga none -display none > -kernel arch/s390/boot/bzImage -append > 'init=/home/luto/devel/virtme/virtme/guest/virtme-init > psmouse.proto=exps "virtme_stty_con=rows 24 cols 150 iutf8" > TERM=xterm-256color rootfstype=9p > rootflags=ro,version=9p2000.L,trans=virtio,access=any > raid=noautodetect debug' The commandline looks sane AFAICS. (...) > vrfy: device 0.0.0000: rc=0 pgroup=0 mpath=0 vpm=80 > virtio_ccw 0.0.0000: Failed to set online: -5 > > ^^^ bad news! I'd like to see where in the onlining process this fails. Could you set up qemu tracing for css_* and virtio_ccw_* (instructions in qemu/docs/tracing.txt)? Which qemu version is this, btw.? -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
