On Fri, Oct 30, 2015 at 1:25 AM, Cornelia Huck <cornelia.huck@xxxxxxxxxx> wrote: > 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)? I have a file called events that contains: css_* virtio_ccw_* pointing -trace events= at it results in a trace-<pid> file that's 549 bytes long and contains nothing. Are wildcards not as well-supported as the docs suggest? > > Which qemu version is this, btw.? > git from yesterday. --Andy -- Andy Lutomirski AMA Capital Management, LLC -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
