[Qemu-devel] qemu error
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: ---- >> 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 51, , 1024 OF stdout device is: /pci@f000/mac-io@e/escc@13000/ch-b@13000 command line: console=ttyS0,9600 console=tty0 memory layout at init: alloc_bottom : 00c01000 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 Looking for displays found display : /pci@f000/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
[Qemu-devel] Qemu stucking
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: ---- >> 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 51, , 1024 OF stdout device is: /pci@f000/mac-io@e/escc@13000/ch-b@13000 command line: console=ttyS0,9600 console=tty0 memory layout at init: alloc_bottom : 00c01000 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 Looking for displays found display : /pci@f000/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
Re: [Qemu-devel] Qemu stucking
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: ---- >> >> 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 51, , 1024 >> OF stdout device is: /pci@f000/mac-io@e/escc@13000/ch-b@13000 >> command line: console=ttyS0,9600 console=tty0 >> memory layout at init: >>alloc_bottom : 00c01000 >>alloc_top: 2000 >>alloc_top_hi : 2000 >>rmo_top : 2000 >>ram_top : 2000 >> Looking for displays >> found display : /pci@f000/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
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: ---- >> 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 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-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: ---- >>> >> 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 51, , 1024 >>> OF stdout device is: /pci@f000/mac-io@e/escc@13000/ch-b@13000 >>> command line: console=ttyS0,9600 console=tty0 >>> memory layout at init: >>>alloc_bottom : 00c01000 >>>alloc_top: 2000 >>>alloc_top_hi : 2000 >>>rmo_top : 2000 >>>ram_top : 2000 >>> Looking for displays >>> found display : /pci@f000/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
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-ayl...@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... > >
Re: [Qemu-devel] Qemu stucking
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-ayl...@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. > >
[Qemu-devel] qemu does not support PAPR
Hi I'm trying to run libguestfs-test-tool which in turn is using kvm utility on powerpc ubuntu.Below are the logs when I'm trying to run the libguesfs-test-tool utility.. libguestfs: launch: umask=0002 libguestfs: launch: euid=1000 libguestfs: [0ms] begin building supermin appliance libguestfs: [0ms] run supermin libguestfs: command: run: /usr/bin/supermin libguestfs: command: run: \ --build libguestfs: command: run: \ --verbose libguestfs: command: run: \ --if-newer libguestfs: command: run: \ --lock /var/tmp/.guestfs-1000/lock libguestfs: command: run: \ --copy-kernel libguestfs: command: run: \ -f ext2 libguestfs: command: run: \ --host-cpu powerpc64 libguestfs: command: run: \ /usr/local/lib/guestfs/supermin.d libguestfs: command: run: \ -o /var/tmp/.guestfs-1000/appliance.d supermin: version: 5.1.8 supermin: package handler: debian/dpkg supermin: acquiring lock on /var/tmp/.guestfs-1000/lock supermin: if-newer: output does not need rebuilding libguestfs: [00014ms] finished building supermin appliance libguestfs: [00014ms] begin testing qemu features libguestfs: command: run: /usr/bin/kvm libguestfs: command: run: \ -display none libguestfs: command: run: \ -help libguestfs: command: run: /usr/bin/kvm libguestfs: command: run: \ -display none libguestfs: command: run: \ -version libguestfs: qemu version 1.4 libguestfs: command: run: /usr/bin/kvm libguestfs: command: run: \ -display none libguestfs: command: run: \ -machine accel=kvm:tcg libguestfs: command: run: \ -device ? libguestfs: [00072ms] finished testing qemu features [00073ms] /usr/bin/kvm \ -global virtio-blk-pci.scsi=off \ -nodefconfig \ -enable-fips \ -nodefaults \ -display none \ -M pseries \ -machine accel=kvm:tcg \ -m 768 \ -no-reboot \ -rtc driftfix=slew \ -global kvm-pit.lost_tick_policy=discard \ -kernel /var/tmp/.guestfs-1000/appliance.d/kernel \ -initrd /var/tmp/.guestfs-1000/appliance.d/initrd \ -device virtio-scsi-pci,id=scsi \ -drive file=/tmp/libguestfscN7Ta1/ scratch.1,cache=unsafe,format=raw,id=hd0,if=none \ -device scsi-hd,drive=hd0 \ -drive file=/var/tmp/.guestfs-1000/appliance.d/root,snapshot=on,id=appliance,cache=unsafe,if=none \ -device scsi-hd,drive=appliance \ -device virtio-serial-pci \ -serial stdio \ -chardev socket,path=/tmp/libguestfscN7Ta1/guestfsd.sock,id=channel0 \ -device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \ -append 'panic=1 console=ttyS0 udevtimeout=600 no_timer_check acpi=off printk.time=1 cgroup_disable=memory root=/dev/sdb selinux=0 guestfs_verbose=1 TERM=xterm' qemu: fatal: This KVM version does not support PAPR NIP LR CTR XER MSR HID0 HF idx 0 TB DECR GPR00 GPR04 GPR08 GPR12 GPR16 GPR20 GPR24 GPR28 CR [ - - - - - - - - ] RES FPR00 FPR04 FPR08 FPR12 FPR16 FPR20 FPR24 FPR28 FPSCR SRR0 SRR1 PVR 80400010 VRSAVE SPRG0 SPRG1 SPRG2 SPRG3 SPRG4 SPRG5 SPRG6 SPRG7 CSRR0 CSRR1 MCSRR0 MCSRR1 TCR TSR ESR DEAR PIR DECAR IVPR EPCR MCSR SPRG8 EPR MCAR PID1 PID2 SVR MAS0 MAS1 MAS2 MAS3 MAS4
Re: [Qemu-devel] qemu does not support PAPR
Hi Paolo I'm running this on ubuntu with powerpc arch with kernel 3.8.13-rt9-QorIQ-SDK-V1.4. Thanks On Thu, Jun 5, 2014 at 11:21 AM, Paolo Bonzini wrote: > Il 05/06/2014 06:50, sonia verma ha scritto: > > Hi >> >> I'm trying to run libguestfs-test-tool which in turn is using kvm >> utility on powerpc ubuntu.Below are the logs when I'm trying to run the >> libguesfs-test-tool utility.. >> > > What machine are you running on? What kernel version? > > Paolo > >
Re: [Qemu-devel] qemu does not support PAPR
So what can be the solution for this?
On Thu, Jun 5, 2014 at 1:13 PM, Paolo Bonzini wrote:
> Il 05/06/2014 08:09, sonia verma ha scritto:
>
> Hi Paolo
>>
>> I'm running this on ubuntu with powerpc arch with kernel
>> 3.8.13-rt9-QorIQ-SDK-V1.4.
>>
>
> I'll note that this is a fairly old kernel for PowerPC KVM. However, the
> problem looks like libguestfs supporting only "server" PowerPC (also known
> as "book3s"), not "embedded" ("booke").
>
> Paolo
>
Re: [Qemu-devel] [Qemu-ppc] qemu does not support PAPR
Hi Stuart. Thanks for the information.I need to run libguestfs on powerpc ubuntu.How can i do that? Are there any patches for the same. On Jun 5, 2014 8:59 PM, "Stuart Yoder" wrote: > > > > -Original Message- > > From: Alexander Graf [mailto:ag...@suse.de] > > Sent: Thursday, June 05, 2014 2:59 AM > > To: sonia verma > > Cc: Paolo Bonzini; abhishek jain; qemu-...@nongnu.org; qemu-devel; Yoder > > Stuart-B08248 > > Subject: Re: [Qemu-ppc] qemu does not support PAPR > > > > > > > > > Am 05.06.2014 um 09:45 schrieb sonia verma : > > > > > > > > > So what can be the solution for this? > > > > Please don't top post. > > > > You're running on QorIQ which is a Freescale chip. The pseries target > > only works on IBM PPC chips. > > > > The target you're looking for is ppce500: > > > > $ qemu-system-ppc64 -M ppce500 -nographic -kernel uImage ... > > > > I don't know about the status of libvirt in your sdk version, but I'm > > sure Stuart does, so let's ask him ;). > > libvirt is supported in Freescale SDK 1.4 in the Yocto-built rootfs, so I > would expect anything that uses libvirt interfaces to work there. But, we > haven't specifically tested libguestfs. > > However, it looks like you may not be using the SDK Yocto rootfs, but a > ubuntu rootfs. In that case there may be a issue with the ubuntu libvirt. > There are some patches that we apply to libvirt that you will find only in > the > Freescale SDK...you can find them if you look at the libvirt Yocto > recipe. > > Stuart > >
Re: [Qemu-devel] [Qemu-ppc] qemu does not support PAPR
Hi Stuart Thanks for the information.I'm able to run libvirt on my system.I need to run libguestfs on the same powerpc ubuntu. Can you help me regarding that? On Thu, Jun 5, 2014 at 11:10 PM, Stuart Yoder wrote: > > From: sonia verma [mailto:soniaverma9...@gmail.com] > > Sent: Thursday, June 05, 2014 12:13 PM > > To: Yoder Stuart-B08248 > > Cc: abhishek jain; Alexander Graf; qemu-...@nongnu.org; qemu-devel; > Paolo Bonzini > > Subject: RE: [Qemu-ppc] qemu does not support PAPR > > > > Hi Stuart. > > Thanks for the information.I need to run libguestfs on powerpc > ubuntu.How can i do that? > > Are there any patches for the same. > > I think you will have to build/install libvirt yourself on ubuntu with the > Freescale patches. > > For SDK 1.4, you can see the Yocto recipe used here: > > http://git.freescale.com/git/cgit.cgi/ppc/sdk/meta-fsl-networking.git/tree/recipes-append/libvirt > > ...we use the stock Yocto libvirt recipe and and apply 2 patches. > > The 2 patches are here: > > http://git.freescale.com/git/cgit.cgi/ppc/sdk/meta-fsl-networking.git/tree/recipes-append/libvirt/files > > I have not built libvirt from scratch myself, so can't help you there. > > Thanks, > Stuart > >
Re: [Qemu-devel] [Qemu-ppc] qemu does not support PAPR
Thanks stuart for the help you have provided me. The libguestfs is directly related with qemu. Could you help me regarding qemu with latest version having freescale patches. I think that will solve my problem. Thanks
[Qemu-devel] qemu-bridge-helper issue
Hi I'm able to run the below command using root permission sudo kvm -netdev bridge,br=qbr0ccdca50-fa,id=hostnet -M ppce500 Warning: netdev hostnet has no peer Could not initialize SDL(No available video device) - exiting However when I'm running the same command without root authority,I'm getting following logs... kvm -netdev bridge,br=qbr0ccdca50-fa,id=hostnet -M ppce500 failed to create tun device: Operation not permitted failed to launch bridge helper kvm: -netdev bridge,br=qbr0ccdca50-fa,id=hostnet: Device 'bridge' could not be initialized I need to run the above command without root authority.Please help regarding this. Thanks Sonia
