On Fri, Jan 22, 2010 at 9:27 AM, Alexander Graf <agraf@xxxxxxx> wrote: > > On 22.01.2010, at 18:23, Corey Minyard wrote: > >> Hollis Blanchard wrote: >>> As for console, you probably want to use qemu's "-nographic" or at >>> least "-serial stdio" options. >>> >> Thanks for the info. However, "-serial stdio" doesn't seem to work. I get: >> >> root@ebony:~# ./qemu-system-ppcemb --enable-kvm -nographic -m 128 -M bamboo -kernel uImage.bamboo -L . -append "" -m 64 -serial stdio >> chardev: opening backend "stdio" failed >> qemu: could not open serial device 'stdio': Success Haven't seen that one. :( Does the same thing happen if you remove --enable-kvm? If so, it sounds like an issue for qemu-devel@xxxxxxxxxxx (No code will actually run like that, since qemu is missing 440 MMU emulation, but it's an easy way to identify the culprit.) > BookE KVM uses virtio console, no? I think that was explained on the wiki too. Sure doesn't. Book E SoCs typically contain NS16550-compatible UARTs, so qemu's normal serial emulation works just fine. -Hollis -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
