Hi Mark Thanks for the reply. I'll test and let you know the result soon.
On Thu, May 15, 2014 at 2:36 PM, Mark Cave-Ayland < mark.cave-ayl...@ilande.co.uk> wrote: > On 15/05/14 06:41, sonia verma wrote: > > Hi >> >> I'm getting below error when trying to boot the KVM with ethernet >> bridging,kvm support and universel TUN enabled by the following command.. >> >> /usr/bin/qemu-system-ppc64 -m 512 -nographic -hda >> /var/volatile/debian_lenny_ >> powerpc_standard.qcow2 >> > > FWIW I think this image will boot with normal qemu-system-ppc too. > > > >> cannot manage 'OHCI USB controller' PCI device type 'usb': >> >> 106b 3f (c 3 10) >> >> >> ============================================================= >> >> OpenBIOS 1.0 [Aug 28 2012 05:40] >> > > Wow, that's fairly old... > > > >> Configuration device id QEMU version 1 machine id 3 >> >> CPUs: 1 >> >> Memory: 512M >> >> UUID: 00000000-0000-0000-0000-000000000000 >> >> CPU type PowerPC,970FX >> Welcome to OpenBIOS v1.0 built on Aug 28 2012 05:40 >> Second-stage QUIK loader >> Welcome to quik. mate is good. >> Debian GNU/Linux PowerPCchosen/bootargs = >> boot: ` >> Enter the kernel image name as [device:][partno]/path, where partno is a >> number from 0 to 16. Instead of /path you can type [mm-nn] to specify a >> range of disk blocks (512B) >> boot: Linux >> initrd imagename = /initrd.img, mem_size: 4406840 >> initrd_start: >> Starting at 510000, , 10240000 >> OF stdout device is: /pci@f0000000/mac-io@e/escc@13000/ch-b@13000 >> command line: console=ttyS0,9600 console=tty0 >> memory layout at init: >> alloc_bottom : 00c01000 >> alloc_top : 20000000 >> alloc_top_hi : 20000000 >> rmo_top : 20000000 >> ram_top : 20000000 >> Looking for displays >> found display : /pci@f0000000/QEMU,VGA@c, opening ... done >> copying OF device tree ... >> Building dt strings... >> Building dt structure... >> Device tree strings 0x00c02000 -> 0x00c024f0 >> Device tree struct 0x00c03000 -> 0x00c05000 >> Calling quiesce ... >> returning from prom_init >> >> The prompt is stuck at init and is not able to proceed even after wating >> for 15-20 minutes. >> >> Please help regarding this. >> > > In my testing here, I tend to find that some versions of Linux don't > particularly like running in -nographic mode and hangs at the point above. > Some kernels even get upset running with a 32/15-bit display and must be > forced to 8-bit instead :/ > > Can you try removing -nographic and instead try one or both of the > following: > > -g 800x600x32 > -g 800x600x8 > > And if those don't work, try the same image again but with qemu-system-ppc > rather than qemu-system-ppc64. > > > HTH, > > Mark. > >
