[Qemu-devel] Qemu stucking

[Qemu-devel] Qemu stucking

[sonia verma]

[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]

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


cannot manage 'OHCI USB controller' PCI device type 'usb':
>>  106b 3f (c 3 10)

>> =============================================================
>> OpenBIOS 1.0 [Aug 28 2012 05:40]
>> 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.

Thanks
Sonia

[-- Attachment #2: Type: text/html, Size: 2162 bytes --]

Re: [Qemu-devel] Qemu stucking

[Mark Cave-Ayland]

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.

Re: [Qemu-devel] Qemu stucking

[sonia verma]

[-- Attachment #1: Type: text/plain, Size: 2702 bytes --]

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-ayland@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.
>
>

[-- Attachment #2: Type: text/html, Size: 3795 bytes --]

Re: [Qemu-devel] Qemu stucking

[sonia verma]

[-- Attachment #1: Type: text/plain, Size: 4088 bytes --]

Hi Mark

I tried booting KVM using qemy-system-ppc with your suggesstion but ended
up stucking at below logs..

/usr/bin/qemu-system-ppc -m 512 -nographic -hda
kvm/debian_lenny_powerpc_standard.qcow2
qemu-system-ppc: pci_add_option_rom: failed to find romfile
"efi-ne2k_pci.rom"
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle
>> set_property: NULL phandle

>> =============================================================
>> OpenBIOS 1.1 [May 26 2013 13:52]
>> Configuration device id QEMU version 1 machine id 2
>> CPUs: 1
>> Memory: 512M
>> UUID: 00000000-0000-0000-0000-000000000000
>> CPU type PowerPC,750


Actually I'm trying to boot KVM from the powerpc board having ubuntu 13.10
on it,so i need to provide the -nographic option.

Please help regarding this.





On Thu, May 15, 2014 at 3:14 PM, sonia verma <soniaverma9727@gmail.com>wrote:

> 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-ayland@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.
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 5785 bytes --]

Re: [Qemu-devel] Qemu stucking

[Mark Cave-Ayland]

On 15/05/14 11:01, sonia verma wrote:

> Hi Mark
>
> I tried booting KVM using qemy-system-ppc with your suggesstion but
> ended up stucking at below logs..
>
> /usr/bin/qemu-system-ppc -m 512 -nographic -hda
> kvm/debian_lenny_powerpc_standard.qcow2
> qemu-system-ppc: pci_add_option_rom: failed to find romfile
> "efi-ne2k_pci.rom"
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle
>  >> set_property: NULL phandle

This looks broken :/  I've seen similar errors to this caused by faulty 
gcc compilers around the 4.7 era breaking OpenBIOS binaries, but I 
always test the images supplied with stock QEMU to make sure they work 
for me here before sending a pull request.

Perhaps it is something within the KVM code? Does it work if you use 
standard QEMU?


ATB,

Mark.

P.S. You should also CC qemu-ppc as that's where the PPC users tend to 
hang out...

Re: [Qemu-devel] Qemu stucking

[sonia verma]

[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]

Hi Mark

The gcc version I'm using is 4.8.1 .
It is not working with the standard Qemu.


On Thu, May 15, 2014 at 3:46 PM, Mark Cave-Ayland <
mark.cave-ayland@ilande.co.uk> wrote:

> On 15/05/14 11:01, sonia verma wrote:
>
>  Hi Mark
>>
>> I tried booting KVM using qemy-system-ppc with your suggesstion but
>> ended up stucking at below logs..
>>
>> /usr/bin/qemu-system-ppc -m 512 -nographic -hda
>> kvm/debian_lenny_powerpc_standard.qcow2
>> qemu-system-ppc: pci_add_option_rom: failed to find romfile
>> "efi-ne2k_pci.rom"
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>  >> set_property: NULL phandle
>>
>
> This looks broken :/  I've seen similar errors to this caused by faulty
> gcc compilers around the 4.7 era breaking OpenBIOS binaries, but I always
> test the images supplied with stock QEMU to make sure they work for me here
> before sending a pull request.
>
> Perhaps it is something within the KVM code? Does it work if you use
> standard QEMU?
>
>
> ATB,
>
> Mark.
>
> P.S. You should also CC qemu-ppc as that's where the PPC users tend to
> hang out...
>
>

[-- Attachment #2: Type: text/html, Size: 2314 bytes --]

Re: [Qemu-devel] Qemu stucking

[Mark Cave-Ayland]

On 15/05/14 11:50, sonia verma wrote:

> Hi Mark
>
> The gcc version I'm using is 4.8.1 .
> It is not working with the standard Qemu.

Unfortunately if it doesn't work with standard QEMU then it sounds as if 
there is something wrong with either your OpenBIOS binary or build 
environment.

The debian_lenny_powerpc_standard.qcow2 image boots fine for me (albeit 
not with -nographic) using a fresh build from git. I would suggest 
trying the same, using the pre-built OpenBIOS images and see if that works.

It may also be worth raising a bug report with your distro if they are 
shipping corrupt binaries.


Kind regards,

Mark.

Re: [Qemu-devel] Qemu stucking

[sonia verma]

[-- Attachment #1: Type: text/plain, Size: 858 bytes --]

Hi Mark

Thanks for the information.It will help me alot.
I'll let you know if any further issues.


On Thu, May 15, 2014 at 4:32 PM, Mark Cave-Ayland <
mark.cave-ayland@ilande.co.uk> wrote:

> On 15/05/14 11:50, sonia verma wrote:
>
>  Hi Mark
>>
>> The gcc version I'm using is 4.8.1 .
>> It is not working with the standard Qemu.
>>
>
> Unfortunately if it doesn't work with standard QEMU then it sounds as if
> there is something wrong with either your OpenBIOS binary or build
> environment.
>
> The debian_lenny_powerpc_standard.qcow2 image boots fine for me (albeit
> not with -nographic) using a fresh build from git. I would suggest trying
> the same, using the pre-built OpenBIOS images and see if that works.
>
> It may also be worth raising a bug report with your distro if they are
> shipping corrupt binaries.
>
>
> Kind regards,
>
> Mark.
>
>

[-- Attachment #2: Type: text/html, Size: 1425 bytes --]