qemu-devel
[Top][All Lists]
Advanced

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

[Qemu-devel] Re: [RFC PATCH 0/8] virtio-console: Move to qdev, multiple


From: Alexander Graf
Subject: [Qemu-devel] Re: [RFC PATCH 0/8] virtio-console: Move to qdev, multiple devices, generic ports
Date: Thu, 24 Dec 2009 12:33:17 +0100

On 24.12.2009, at 11:34, Amit Shah wrote:

> On (Thu) Dec 24 2009 [11:28:25], Alexander Graf wrote:
>> 
>> address@hidden:/tmp/qemu> ./s390x-softmmu/qemu-system-s390x -enable-kvm -vnc 
>> :0 -kernel /boot/image
>> Did not find PCI bus for virtio-serial-pci
>> Did not find virtio-serial-bus bus for virtconsole
>> address@hidden:/tmp/qemu> 
>> address@hidden:/tmp/qemu> ./s390x-softmmu/qemu-system-s390x -enable-kvm -vnc 
>> :0 -kernel /boot/image -virtioconsole stdio
>> Did not find PCI bus for virtio-serial-pci
>> Did not find virtio-serial-bus bus for virtconsole
>> address@hidden:/tmp/qemu> 
> 
> Please try with
> 
> -chardev ...,id=cons  -device virtio-serial-s390 -device
> virtconsole,chardev=cons

That looks pretty good:

address@hidden:/tmp/qemu> ./s390x-softmmu/qemu-system-s390x -enable-kvm -vnc :0 
-kernel /boot/image -chardev stdio,id=cons  -device virtio-serial-s390 -device 
virtconsole,chardev=cons
Did not find PCI bus for virtio-serial-pci
cio.b5d5f6: Channel measurement facility initialized using format basic (mode 
autodetected)
TCP cubic registered
registered taskstats version 1
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "ram0" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
DEBUG_BLOCK_EXT_DEVT is enabled, you need to specify explicit textual name for 
"root=" boot option.
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
CPU: 0 Not tainted 2.6.32.1-0.1-default #1
Process swapper (pid: 1, task: 0000000007e60038, ksp: 0000000007e67b20)
0000000000000000 0000000007e67cd0 0000000000000002 0000000000000000 
       0000000007e67d70 0000000007e67ce8 0000000007e67ce8 0000000000105e52 
       0000000000000000 0000000000000000 0000000000000000 0000000000000000 
       000000000000000d 0000000000000000 0000000007e67d38 000000000000000e 
       000000000047bb18 0000000000105e52 0000000007e67cd0 0000000007e67d18 
Call Trace:
([<0000000000105d62>] show_trace+0xe6/0x134)
 [<000000000046f3e4>] panic+0x90/0x200
 [<000000000075812a>] mount_block_root+0x1e2/0x32c
 [<000000000075844c>] prepare_namespace+0x150/0x1cc
 [<00000000007575cc>] kernel_init+0x108/0x130
 [<000000000010a722>] kernel_thread_starter+0x6/0xc
 [<000000000010a71c>] kernel_thread_starter+0x0/0xc



reply via email to

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