[Qemu-devel] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
sorry for the extra comment on g5 quad i use this options gigi@gigi-desktop:~/qemu-2.9.0-rc1/ppc64-softmmu$ sudo ./qemu-system-ppc64 -enable-kvm -m 1024 -display sdl,gl=on -device virtio-gpu-pci,virgl --nodefaults -vga none -M pseries-2.5 -smp 2 -serial stdio for no serial sudo ./qemu-system-ppc64 -enable-kvm -m 1024 -display sdl,gl=on -device virtio-gpu-pci,virgl --nodefaults -vga none -M pseries-2.5 -smp 2 -serial stdio . you can see i dont have any output on the virtio-gpu-pci . itry with virgl and without and i try with -device virtio-vga too .. all gave the same result changing the pseries too. ** Attachment added: "Schermata del 2017-03-30 20-18-40.png" https://bugs.launchpad.net/qemu/+bug/1674925/+attachment/4850711/+files/Schermata%20del%202017-03-30%2020-18-40.png -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected Status in QEMU: New Bug description: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1674925/+subscriptions
[Qemu-devel] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
Hi thomas, this is the quad G5 shot on ubuntu mate 17.04 with last stable kernel 4.10.7 with xics builded inside you can see i have the same result i have on Qoriq on fedora ppc64 . the only way for see something is use -serial stdio option ** Attachment added: "quad g5 qemu 2.91" https://bugs.launchpad.net/qemu/+bug/1674925/+attachment/4850710/+files/Schermata%20del%202017-03-30%2020-19-14.png -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected Status in QEMU: New Bug description: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1674925/+subscriptions
[Qemu-devel] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
hi thomas on Qoriq Xics isnt present and cant be selected and i dont have video output too this is a shot of the kernel config. On G5 Quad i will made a shoot too i thinks screenshots is better then may english knowledge :P ** Attachment added: "Qoriq kenel cofig" https://bugs.launchpad.net/qemu/+bug/1674925/+attachment/4850656/+files/Screenshot_2017-03-30_18-23-26.png -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected Status in QEMU: New Bug description: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1674925/+subscriptions
[Qemu-devel] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
attched the booted mate 16.10 Qemu system ppc64 --kvm on Qoriq without video initialized only way i have to see something is with --serial stdio here i post the log of Qemu-system-ppc64 i filed a new bug about https://bugs.launchpad.net/qemu/+bug/1677247 soon the G5 Quad shots ** Attachment added: "Screenshot_2017-03-29_21-15-08.png" https://bugs.launchpad.net/qemu/+bug/1674925/+attachment/4850658/+files/Screenshot_2017-03-29_21-15-08.png -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected Status in QEMU: New Bug description: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1674925/+subscriptions
[Qemu-devel] [Bug 1399957] Re: Strange colors on PowerMac Machine OsX
** Changed in: qemu Status: New => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1399957 Title: Strange colors on PowerMac Machine OsX Status in QEMU: Fix Released Bug description: Strange colors on PowerMac Machine OsX if it used VmWare or Std i have strange color palette as result. I had benn made a grab of screen here http://i1249.photobucket.com/albums/hh511/tlosm/qyellow_zps1d2dfc18.jpg My Machine is a PowerMac G5 Quad with Nvidia 7800Gtx 512mb thankyou Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1399957/+subscriptions
[Qemu-devel] [Bug 1569491] Re: qemu system i386 poor performance on e5500 core
** Changed in: qemu Status: New => Opinion -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1569491 Title: qemu system i386 poor performance on e5500 core Status in QEMU: Opinion Bug description: I had been tested with generic core net building or with mtune e5500 but i have the same result: performances are extremly low compared with other classes of powerpc cpu. The strange is the 5020 2ghz in all emulators been tested by me is comparable with a 970MP 2.7 ghz in speed and benchmarks but im facing the half of performance in i386-soft-mmu compared with a 2.5 ghz 970MP. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1569491/+subscriptions
[Qemu-devel] [Bug 1571084] Re: Qemu 2.x dont build on last Gtk dev 3.0+
** Changed in: qemu Status: New => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1571084 Title: Qemu 2.x dont build on last Gtk dev 3.0+ Status in QEMU: Fix Released Bug description: here the build exit ui/gtk.c: In function ‘gd_mouse_set’: ui/gtk.c:479:5: error: ‘gdk_display_get_device_manager’ is deprecated: Use 'gdk_display_get_default_seat' instead [-Werror=deprecated-declarations] mgr = gdk_display_get_device_manager(dpy); ^ In file included from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32:0, from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, from /usr/local/include/gtk-3.0/gdk/gdk.h:32, from /usr/local/include/gtk-3.0/gtk/gtk.h:30, from /home/amigaone/src/qemu/include/ui/gtk.h:9, from ui/gtk.c:42: /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:170:20: note: declared here GdkDeviceManager * gdk_display_get_device_manager (GdkDisplay *display); ^ ui/gtk.c:482:5: error: ‘gdk_device_manager_get_client_pointer’ is deprecated [-Werror=deprecated-declarations] gdk_device_warp(gdk_device_manager_get_client_pointer(mgr), ^ In file included from /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:32:0, from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32, from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, from /usr/local/include/gtk-3.0/gdk/gdk.h:32, from /usr/local/include/gtk-3.0/gtk/gtk.h:30, from /home/amigaone/src/qemu/include/ui/gtk.h:9, from ui/gtk.c:42: /usr/local/include/gtk-3.0/gdk/gdkdevicemanager.h:44:14: note: declared here GdkDevice * gdk_device_manager_get_client_pointer (GdkDeviceManager *device_manager); ^ ui/gtk.c: In function ‘gd_grab_devices’: ui/gtk.c:1316:5: error: ‘gdk_display_get_device_manager’ is deprecated: Use 'gdk_display_get_default_seat' instead [-Werror=deprecated-declarations] GdkDeviceManager *mgr = gdk_display_get_device_manager(display); ^ In file included from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32:0, from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, from /usr/local/include/gtk-3.0/gdk/gdk.h:32, from /usr/local/include/gtk-3.0/gtk/gtk.h:30, from /home/amigaone/src/qemu/include/ui/gtk.h:9, from ui/gtk.c:42: /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:170:20: note: declared here GdkDeviceManager * gdk_display_get_device_manager (GdkDisplay *display); ^ ui/gtk.c:1317:5: error: ‘gdk_device_manager_list_devices’ is deprecated [-Werror=deprecated-declarations] GList *devs = gdk_device_manager_list_devices(mgr, GDK_DEVICE_TYPE_MASTER); ^ In file included from /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:32:0, from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32, from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, from /usr/local/include/gtk-3.0/gdk/gdk.h:32, from /usr/local/include/gtk-3.0/gtk/gtk.h:30, from /home/amigaone/src/qemu/include/ui/gtk.h:9, from ui/gtk.c:42: /usr/local/include/gtk-3.0/gdk/gdkdevicemanager.h:41:14: note: declared here GList * gdk_device_manager_list_devices (GdkDeviceManager *device_manager, ^ ui/gtk.c:1327:13: error: ‘gdk_device_grab’ is deprecated: Use 'gdk_seat_grab' instead [-Werror=deprecated-declarations] gdk_device_grab(dev, win, GDK_OWNERSHIP_NONE, FALSE, ^ In file included from /usr/local/include/gtk-3.0/gdk/gdkdnd.h:33:0, from /usr/local/include/gtk-3.0/gdk/gdkevents.h:34, from /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:31, from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32, from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, from /usr/local/include/gtk-3.0/gdk/gdk.h:32, from /usr/local/include/gtk-3.0/gtk/gtk.h:30, from /home/amigaone/src/qemu/include/ui/gtk.h:9, from ui/gtk.c:42: /usr/local/include/gtk-3.0/gdk/gdkdevice.h:250:15: note: declared here GdkGrabStatus gdk_device_grab(GdkDevice*device, ^ ui/gtk.c:1330:13: error: ‘gdk_device_ungrab’ is deprecated: Use 'gdk_seat_ungrab' instead [-Werror=deprecated-declarations] gdk_device_ungrab(dev, GDK_CURRENT_TIME); ^ In file included from /usr/local/include/gtk-3.0/gdk/gdkdnd.h:33:0, from /usr/local/include/gtk-3.0/gdk/gdkevents.h:34,
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
** Changed in: qemu Status: New => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: Fix Released Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ec6f000) libusb-1.0.so.0 => /lib/powerpc-linux-gnu/libusb-1.0.so.0 (0x0ec2e000) librt.so.1 => /lib/powerpc-linux-gnu/librt.so.1 (0x0ebfd000) libm.so.6 => /lib/powerpc-linux-gnu/libm.so.6 (0x0eb0c000) libgcc_s.so.1 => /lib/powerpc-linux-gnu/libgcc_s.so.1 (0x0eacb000) libpthread.so.0 => /lib/powerpc-linux-gnu/libpthread.so.0 (0x0ea88000) libc.so.6 => /lib/powerpc-linux-gnu/libc.so.6 (0x0e8d4000) libdrm.so.2 =>
[Qemu-devel] [Bug 1588473] Re: Qemu Mate 16.10 and Gtk dont build
** Changed in: qemu Status: New => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1588473 Title: Qemu Mate 16.10 and Gtk dont build Status in QEMU: Fix Released Bug description: when i try to build last qemu 2.6 on 16.10 of ubuntu mate i have this. note on 16.04 was building without problem LINK i386-softmmu/qemu-system-i386 ../ui/gtk.o: In function `gd_get_pointer': /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer' ../ui/gtk.o: In function `gd_grab_update': /home/amigaone/src/qemu/ui/gtk.c:1339: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:1353: undefined reference to `gdk_seat_grab' /home/amigaone/src/qemu/ui/gtk.c:1356: undefined reference to `gdk_seat_ungrab' ../ui/gtk.o: In function `gd_get_pointer': /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer' collect2: error: ld returned 1 exit status To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1588473/+subscriptions
[Qemu-devel] [Bug 1675549] Re: tcg softmmu i386 crashes on BE hardware
** Changed in: qemu Status: New => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1675549 Title: tcg softmmu i386 crashes on BE hardware Status in QEMU: Fix Released Bug description: Hi, today i try to test qemu 2.9rc 1 with qemu-system-i386 if i set display as sdl and i push a key on keyboard qemu exit with an error translate-common.c:34:tcg_handle_interrupt: assertion failed: (qemu_mutex_iothread_locked()) This issue was not present on qemu 2.8.0 Test Machine PowerMac G5 Quad Fedora 25 Server PPC64 Qemu build with target-list=i386-softmuu --with-sdlabi=2.0 Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1675549/+subscriptions
[Qemu-devel] [Bug 1677247] [NEW] QEMU e500 kvm no video and kernel crashing in virtios modules
Public bug reported: Hi, i been attached the log of my issue on Qoriq e5500 when i start qemu-system-ppc64 -cpu e5500 -M ppce500 --enable-kvm -device virtio-gpu-pci --nodefaults -display gtk and so and so . i have crashes in virtio modules in the VM and continue traces on the host machine. If is needed more for investigating ask freely . Note: i use my selfmade kernel this machine dont have a distro kenels and official kernels. Ciao Luigi ** Affects: qemu Importance: Undecided Status: New ** Attachment added: "qemu.log" https://bugs.launchpad.net/bugs/1677247/+attachment/4849737/+files/qemu.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1677247 Title: QEMU e500 kvm no video and kernel crashing in virtios modules Status in QEMU: New Bug description: Hi, i been attached the log of my issue on Qoriq e5500 when i start qemu-system-ppc64 -cpu e5500 -M ppce500 --enable-kvm -device virtio-gpu-pci --nodefaults -display gtk and so and so . i have crashes in virtio modules in the VM and continue traces on the host machine. If is needed more for investigating ask freely . Note: i use my selfmade kernel this machine dont have a distro kenels and official kernels. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1677247/+subscriptions
Re: [Qemu-devel] [Qemu-ppc] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
Hi, now i understand . xics have to be build in kernel and is needed by qemu 2.9 with kvm. if is not present in the kernel have the issue that i been reported about xics. I make a test on ubuntu 16.10 and on 17.04. the two distro are ppc 32 and generic. i had build the stable kernel 4.10.5 two times with the same config the only parameter that i had change was the xics one was yes and the other was no. On the two ubuntu version when i run kernel without xics i had the issue reported. if i run the kernel with xics enabled qemu 2.9 is working and was gave no issue. but ... on Fedora server 25 ppc64 if xics is present in the kernel the system (fedora) not run and freeze after the kernel bootstrap. Hope all is understandable Thanks Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected Status in QEMU: New Bug description: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1674925/+subscriptions
Re: [Qemu-devel] [Qemu-ppc] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
Hi Cèdric, i had been build the kernel with the Xics option enabled and all work on G5 970MP on Mate 17.04 i will test the same kernel of Fedora server PPC64 and see if there will work too. but it is strange thing, because the option was not needed (by the kernel default) on PowerMacs and was not need to be enabled on Qemu 2.8. I suggest to add this in the user faq PowerPC. I will test it on Qoriq too if kernel build with this option enabled and if all work ok there too in case i will report as usual. I will warn all the PowerPc comunity about if the qemu devs will need to have Xics turned on as default in the kernel Thanks for your support Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected Status in QEMU: New Bug description: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1674925/+subscriptions
Re: [Qemu-devel] [Qemu-ppc] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
Hi Cèdric, first of all thanks for your relpy. >I have some difficulty sorting out what is going on and what >could be considered a regression :/ you are reporting many >issues at the same time with a home made kernel. >Could you please use the kernel shipped with the distro to >start with ? I can do it and report. > yes usually with 2.8 i boot the VM without issue on G5 Quad with the option > -M pseries from 2.1 to 2.5 with kvm-pr enabled. > i did the tests and with all pseries now on 2.9 i have the same issue. > example: > qemu-system-ppc64 --enable-kvm -cpu 970fx_v2.0 -m 1024 -M pseries-2.1 > qemu-system-ppc64: KVM and IRQ_XICS capability must be present for in-kernel > XICS >This error message is because your host kernel lacks in-kernel XICS, >but you are saying that was not an issue with QEMU-2.8. Correct ? Exactly i have the same on Qoriq too. >Here is the command line I used on a 17.04 host : >qemu-system-ppc64 -M pseries-2.[1-8],accel=kvm,kvm-type=PR -cpu 970fx_v2.0 -m >1024 -nographic I will try your same command line and see what will exit on me. I cant use qemu on 17.04 host because there is no more support for PPC32, PPC64 dead line is 16.10 and last working version of qemu on PPC is 2.6.1 i dint try 2.9 there if needed i can do i have ubuntu mate 17.04 installed too. >Did we introduce a regression in compatibility in QEMU 2.9 ? or Im facing many issue on this last update im try to help how i can before all come upstream. i like really much qemu. i can help in testing on PPC64 Be if need with my hw. >was it bogus before ? That needs a little digging. I did not work >on that part. dont worry you did much Thanks Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected Status in QEMU: New Bug description: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1674925/+subscriptions
[Qemu-devel] [Bug 1675549] [NEW] tcg softmmu i386 crashes on BE hardware
Public bug reported: Hi, today i try to test qemu 2.9rc 1 with qemu-system-i386 if i set display as sdl and i push a key on keyboard qemu exit with an error translate-common.c:34:tcg_handle_interrupt: assertion failed: (qemu_mutex_iothread_locked()) This issue was not present on qemu 2.8.0 Test Machine PowerMac G5 Quad Fedora 25 Server PPC64 Qemu build with target-list=i386-softmuu --with-sdlabi=2.0 Ciao Luigi ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1675549 Title: tcg softmmu i386 crashes on BE hardware Status in QEMU: New Bug description: Hi, today i try to test qemu 2.9rc 1 with qemu-system-i386 if i set display as sdl and i push a key on keyboard qemu exit with an error translate-common.c:34:tcg_handle_interrupt: assertion failed: (qemu_mutex_iothread_locked()) This issue was not present on qemu 2.8.0 Test Machine PowerMac G5 Quad Fedora 25 Server PPC64 Qemu build with target-list=i386-softmuu --with-sdlabi=2.0 Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1675549/+subscriptions
Re: [Qemu-devel] [Qemu-ppc] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
Hello Cédric, with your last message you made me think about and make more test. >The default machine for qemu-system-ppc64 is pseries. yes usually with 2.8 i boot the VM without issue on G5 Quad with the option -M pseries from 2.1 to 2.5 with kvm-pr enabled. i did the tests and with all pseries now on 2.9 i have the same issue. example: qemu-system-ppc64 --enable-kvm -cpu 970fx_v2.0 -m 1024 -M pseries-2.1 qemu-system-ppc64: KVM and IRQ_XICS capability must be present for in-kernel XICS but no issue if i run with -M mac99 before 2.9 was not possible use it on qemu-system-ppc64 It means it will no possible anymore in future release of qemu use open firmware on powermacs any moore? >I admit the message is not very clear, but the host kernel is >using a dev config. Im so sorry, i learn English by my self reading ml and on irc chatting is too difficult where no one speak English around. >> On Qoriq if i pass the -cpu e500 (normal thing) all is working right qemu >> 2.9rc1 >> all boot and so and so. >but you must be changing the machine right ? not on Qoriq because it is book3e and is not so flexible like the G5 Quad who is book3s machine. i can run qemu kvm only with emb hardware on Qoriq >>On G5 the -cpu variable dont fix the issue. >with which machine ? On PowerMac G5 Quad 970MP it have similar hardware configuration of IBM intellistation power 285 > >I can build a new kernel release , usually mine dont have xics enabled > >because G5 >> dont have that feature, if needed i can enable it for testing.** >Yes that would be interesting. I will do ASAP just the time to build it . Thank you really much for your time and patience. Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected Status in QEMU: New Bug description: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1674925/+subscriptions
Re: [Qemu-devel] [Qemu-ppc] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
Hi Cédric, i have the 4.11 rc1 . on fedora 25 ppc 64 on both machine Qoriq and on G5 Quad. On the 2.8 this issue isnt present but I did the test o Qoriq e5500 a book3e processor and on 2.8 if i made: qemu-system-ppc64 --enable-kvm the true result is: qemu-system-ppc64: Unable to find CPU definition: host on qemu 2.9 rc1 ./qemu-system-ppc64 --enable-kvm i have : qemu-system-ppc64: KVM and IRQ_XICS capability must be present for in-kernel XICS On Qoriq if i pass the -cpu e500 (normal thing) all is working right qemu 2.9rc1 all boot and so and so. On G5 the -cpu variable dont fix the issue. I can build a new kernel release , usually mine dont have xics enabled because G5 dont have that feature, if needed i can enable it for testing. Hope my english is understandable. ciao Luigi Da: Qemu-ppc <qemu-ppc-bounces+intermediadc=hotmail@nongnu.org> per conto di Cédric Le Goater <c...@kaod.org> Inviato: mercoledì 22 marzo 2017 18.29 A: Thomas Huth; Bug 1674925; qemu-devel@nongnu.org Cc: qemu-...@nongnu.org Oggetto: Re: [Qemu-ppc] [Qemu-devel] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected On 03/22/2017 03:15 PM, Thomas Huth wrote: > On 22.03.2017 14:35, luigiburdo wrote: >> Hi Thomas with 2.9 rc1 i have this with --enable-kvm >> >> emu-system-ppc64 --enable-kvm >> qemu-system-ppc64: KVM and IRQ_XICS capability must be present for in-kernel >> XICS >> >> and the qemu dont run. > > Does it exit, or just hang afterwards? Was this with or without --device > virtio-gpu-pci option? Do you get any output if you run QEMU with > "-nographic" instead? I guess this is an issue with the host kernel. Which one are you running ? C. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected Status in QEMU: New Bug description: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1674925/+subscriptions
Re: [Qemu-devel] [Qemu-ppc] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
Hi Thomas, just exit like it is an error with a wrong option. the output is only this qemu-system-ppc64: KVM and IRQ_XICS capability must be present for in-kernel XICS Same is if i add all the options i have the seme error. look like qemu need for run in kvm a kernel with XICS option enabled and XICS is present only from ibm power 5 to up if i remember good. After work i can test it if needed on Qoriq e5500 too for check if there is the same issue on an emb ppc64 processor. Ciao Luigi On 22.03.2017 14:35, luigiburdo wrote: > Hi Thomas with 2.9 rc1 i have this with --enable-kvm > > emu-system-ppc64 --enable-kvm > qemu-system-ppc64: KVM and IRQ_XICS capability must be present for in-kernel > XICS > > and the qemu dont run. Does it exit, or just hang afterwards? Was this with or without --device virtio-gpu-pci option? Do you get any output if you run QEMU with "-nographic" instead? Thomas -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected Status in QEMU: New Bug description: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1674925/+subscriptions
[Qemu-devel] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
Hi Thomas with 2.9 rc1 i have this with --enable-kvm emu-system-ppc64 --enable-kvm qemu-system-ppc64: KVM and IRQ_XICS capability must be present for in-kernel XICS and the qemu dont run. Ciao Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected Status in QEMU: New Bug description: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1674925/+subscriptions
[Qemu-devel] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
Hi Thomas, thanks for your reply i will test and report my experience ASAP Ciao Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected Status in QEMU: New Bug description: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1674925/+subscriptions
[Qemu-devel] [Bug 1674925] [NEW] Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
Public bug reported: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected Status in QEMU: New Bug description: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output the same issue i found is if i select: qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so i had been try to change all the -M types of all kind of pseries without any positive result. Ciao Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1674925/+subscriptions
[Qemu-devel] [Bug 1667613] [NEW] Qemu 2.8 on PPC64 issue with input
Public bug reported: Hi devs, on my PPC64 machine if i start qemu with gtk,gl=on or with sdl,gl=on i have issue with pointer and keyboard. pratically not input at all. This issue is present in tgc and in kvm without gl=on option in kvm with mate as guest i have the input device work in the beginning but after some time the usb goes "unplugged" (i see this message on the serial log of qemu usb unplugged) and the keyboard and mouse dont work. On Debian jessie kvm i dont have input working at all. my machine is a G5 quad with Fedora 25 PPC64 thanks Luigi ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1667613 Title: Qemu 2.8 on PPC64 issue with input Status in QEMU: New Bug description: Hi devs, on my PPC64 machine if i start qemu with gtk,gl=on or with sdl,gl=on i have issue with pointer and keyboard. pratically not input at all. This issue is present in tgc and in kvm without gl=on option in kvm with mate as guest i have the input device work in the beginning but after some time the usb goes "unplugged" (i see this message on the serial log of qemu usb unplugged) and the keyboard and mouse dont work. On Debian jessie kvm i dont have input working at all. my machine is a G5 quad with Fedora 25 PPC64 thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1667613/+subscriptions
[Qemu-devel] [Bug 1657538] Re: qemu 2.7.x 2.8 softmmu dont work on BE machine
Oh my gosh the great Cameron Kaiser :) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1657538 Title: qemu 2.7.x 2.8 softmmu dont work on BE machine Status in QEMU: New Bug description: Build on Be machine qemu 2.7.1 and 2.8 in pure softmmu (tgc) dont work on big endian hardware . tested with ppc-softmmu,i386-softmmu,arm-softmmu same result: with : ./qemu-system-i386 Gtk-Message: Failed to load module "overlay-scrollbar" qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. I try to add the -L option with ../pc-bios/bios.bin and have the same result. note the ppc-softmmu and ppc64-softmmu work in kvm mode only emulated mode have issue. tested on my hardware a Qriq P5040 and G5 4x970MP with Ubuntu Mate 16.10 thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1657538/+subscriptions
[Qemu-devel] [Bug 1657538] Re: qemu 2.7.x 2.8 softmmu dont work on BE machine
i386-softmmu: ./qemu-system-i386 -nographic qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: and so and so ./qemu-system-ppc -nographic nothing happen ... no exit on console . on 2.6.2 i have: qemu-system-ppc -nographic >> = >> OpenBIOS 1.1 [Apr 18 2016 08:20] >> Configuration device id QEMU version 1 machine id 2 >> CPUs: 1 >> Memory: 128M >> UUID: ---- >> CPU type PowerPC,750 milliseconds isn't unique. Welcome to OpenBIOS v1.1 built on Apr 18 2016 08:20 Trying hd:,\\:tbxi... Trying hd:,\ppc\bootinfo.txt... Trying hd:,%BOOT... note the 2.6.2 work, before on 2.6.1 i had the same issue of 2.7 and 2.8 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1657538 Title: qemu 2.7.x 2.8 softmmu dont work on BE machine Status in QEMU: New Bug description: Build on Be machine qemu 2.7.1 and 2.8 in pure softmmu (tgc) dont work on big endian hardware . tested with ppc-softmmu,i386-softmmu,arm-softmmu same result: with : ./qemu-system-i386 Gtk-Message: Failed to load module "overlay-scrollbar" qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. I try to add the -L option with ../pc-bios/bios.bin and have the same result. note the ppc-softmmu and ppc64-softmmu work in kvm mode only emulated mode have issue. tested on my hardware a Qriq P5040 and G5 4x970MP with Ubuntu Mate 16.10 thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1657538/+subscriptions
[Qemu-devel] [Bug 1657538] Re: qemu 2.7.x 2.8 softmmu dont work on BE machine
Hi Thomas, here the configure .. i made a clean one just with the target for have fastest build will report soon the result with the nographic just the time of build src/qemu$ ./configure --target-list=i386-softmmu,ppc-softmmu,ppc64-softmmu Install prefix/usr/local BIOS directory/usr/local/share/qemu binary directory /usr/local/bin library directory /usr/local/lib module directory /usr/local/lib/qemu libexec directory /usr/local/libexec include directory /usr/local/include config directory /usr/local/etc local state directory /usr/local/var Manual directory /usr/local/share/man ELF interp prefix /usr/gnemul/qemu-%M Source path /home/amigaone/src/qemu C compilercc Host C compiler cc C++ compiler c++ Objective-C compiler clang ARFLAGS rv CFLAGS-O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -g QEMU_CFLAGS -I/usr/include/pixman-1-Werror -DHAS_LIBSSH2_SFTP_FSYNC -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc-linux-gnu/glib-2.0/include -D_GNU_SOURCE -I/usr/include/ncursesw -m32 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wendif-labels -Wno-shift-negative-value -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition -Wtype-limits -fstack-protector-strong -I/usr/local/include/libpng12 -I/usr/local/include/cacard -I/usr/include/nss -I/usr/include/nspr -I/usr/include/libusb-1.0 LDFLAGS -Wl,--warn-common -m32 -g make make install install pythonpython -B smbd /usr/sbin/smbd module supportno host CPU ppc host big endian yes target list i386-softmmu ppc-softmmu ppc64-softmmu tcg debug enabled no gprof enabled no sparse enabledno strip binariesyes profiler no static build no pixmansystem SDL support yes (1.2.15) GTK support yes (2.24.30) GTK GL supportno VTE support no TLS priority NORMAL GNUTLS supportno GNUTLS rndno libgcrypt yes libgcrypt kdf yes nettleno nettle kdfno libtasn1 no curses supportyes virgl support yes curl support yes mingw32 support no Audio drivers oss Block whitelist (rw) Block whitelist (ro) VirtFS supportyes VNC support yes VNC SASL support yes VNC JPEG support yes VNC PNG support yes xen support no brlapi supportyes bluez supportyes Documentation yes PIE no vde support no netmap supportno Linux AIO support yes ATTR/XATTR support yes Install blobs yes KVM support yes COLO support yes RDMA support yes TCG interpreter no fdt support yes preadv supportyes fdatasync yes madvise yes posix_madvise yes libcap-ng support yes vhost-net support yes vhost-scsi support yes vhost-vsock support yes Trace backendslog spice support no rbd support yes xfsctl supportyes smartcard support yes libusbyes usb net redir yes OpenGL supportyes OpenGL dmabufsyes libiscsi support yes libnfs supportyes build guest agent yes QGA VSS support no QGA w32 disk info no QGA MSI support no seccomp support yes coroutine backend ucontext coroutine poolyes debug stack usage no GlusterFS support no Archipelago support no gcov gcov gcov enabled no TPM support yes libssh2 support yes TPM passthrough no QOM debugging yes lzo support yes snappy supportyes bzip2 support yes NUMA host support yes tcmalloc support no jemalloc support no avx2 optimization no replication support yes -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1657538 Title: qemu 2.7.x 2.8 softmmu dont work on BE machine Status in QEMU: New Bug description: Build on Be machine qemu 2.7.1 and 2.8 in pure softmmu (tgc) dont work on big endian hardware . tested with ppc-softmmu,i386-softmmu,arm-softmmu same result: with : ./qemu-system-i386 Gtk-Message: Failed to load module "overlay-scrollbar" qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are
[Qemu-devel] [Bug 1657538] [NEW] qemu 2.7.x 2.8 softmmu dont work on BE machine
Public bug reported: Build on Be machine qemu 2.7.1 and 2.8 in pure softmmu (tgc) dont work on big endian hardware . tested with ppc-softmmu,i386-softmmu,arm-softmmu same result: with : ./qemu-system-i386 Gtk-Message: Failed to load module "overlay-scrollbar" qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. I try to add the -L option with ../pc-bios/bios.bin and have the same result. note the ppc-softmmu and ppc64-softmmu work in kvm mode only emulated mode have issue. tested on my hardware a Qriq P5040 and G5 4x970MP with Ubuntu Mate 16.10 thanks Luigi ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1657538 Title: qemu 2.7.x 2.8 softmmu dont work on BE machine Status in QEMU: New Bug description: Build on Be machine qemu 2.7.1 and 2.8 in pure softmmu (tgc) dont work on big endian hardware . tested with ppc-softmmu,i386-softmmu,arm-softmmu same result: with : ./qemu-system-i386 Gtk-Message: Failed to load module "overlay-scrollbar" qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. I try to add the -L option with ../pc-bios/bios.bin and have the same result. note the ppc-softmmu and ppc64-softmmu work in kvm mode only emulated mode have issue. tested on my hardware a Qriq P5040 and G5 4x970MP with Ubuntu Mate 16.10 thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1657538/+subscriptions
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
Hi T, good news the 2.6.2 is working without the issue reported, but it not include your previous patches . Ciao Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: New Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ec6f000) libusb-1.0.so.0 => /lib/powerpc-linux-gnu/libusb-1.0.so.0 (0x0ec2e000) librt.so.1 => /lib/powerpc-linux-gnu/librt.so.1 (0x0ebfd000) libm.so.6 => /lib/powerpc-linux-gnu/libm.so.6 (0x0eb0c000) libgcc_s.so.1 => /lib/powerpc-linux-gnu/libgcc_s.so.1 (0x0eacb000) libpthread.so.0 => /lib/powerpc-linux-gnu/libpthread.so.0 (0x0ea88000) libc.so.6 =>
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
Hi T, bad news i had to format my partition with 16.10 and dont have the 2.6.0 src any more if there is a way to git clone it please letme know. note : 2.6.1 have the issue , 2.7.x is effected too. Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: New Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ec6f000) libusb-1.0.so.0 => /lib/powerpc-linux-gnu/libusb-1.0.so.0 (0x0ec2e000) librt.so.1 => /lib/powerpc-linux-gnu/librt.so.1 (0x0ebfd000) libm.so.6 => /lib/powerpc-linux-gnu/libm.so.6 (0x0eb0c000) libgcc_s.so.1 => /lib/powerpc-linux-gnu/libgcc_s.so.1 (0x0eacb000) libpthread.so.0 =>
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
Hi T, im checking and testing the lastest qemu and i understand the issue is present only with all softmmu system . if i open eg qemu-system-ppc64 i have the issue if i open qemu-system-ppc64 with kvm enabled the issue isnt present and all run like have to be. It means all the emulated machine not work , virtualized only run. in my case on g5 quad i cant emulate an X86 or a old world mac but i can virtualize my g5 quad with a debian. same is on p5020 machine. Hope it help -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: New Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ec6f000) libusb-1.0.so.0 =>
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
Hi t, just to notice the 2.7 is effected too :-( ./qemu-system-i386 qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. amigaone@Amigaone:~/src/pippo/qemu/i386-softmmu$ ./qemu-system-i386 -m 1024 qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. amigaone@Amigaone:~/src/pippo/qemu/i386-softmmu$ ./qemu-system-i386 --version QEMU emulator version 2.6.90 (v2.7.0-rc0-10-gf49ee63-dirty), Copyright (c) 2003-2008 Fabrice Bellard -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: New Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 =>
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
Hi t, this is what you need? 70f87e0f0aa04f764dabaeb3ed71ff195748076a is the first bad commit -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: New Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ec6f000) libusb-1.0.so.0 => /lib/powerpc-linux-gnu/libusb-1.0.so.0 (0x0ec2e000) librt.so.1 => /lib/powerpc-linux-gnu/librt.so.1 (0x0ebfd000) libm.so.6 => /lib/powerpc-linux-gnu/libm.so.6 (0x0eb0c000) libgcc_s.so.1 => /lib/powerpc-linux-gnu/libgcc_s.so.1 (0x0eacb000) libpthread.so.0 => /lib/powerpc-linux-gnu/libpthread.so.0 (0x0ea88000) libc.so.6 => /lib/powerpc-linux-gnu/libc.so.6 (0x0e8d4000)
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
Hi T, Ok. I m sorry i was thinking only this was needed i will made the other git bisect and report Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: New Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ec6f000) libusb-1.0.so.0 => /lib/powerpc-linux-gnu/libusb-1.0.so.0 (0x0ec2e000) librt.so.1 => /lib/powerpc-linux-gnu/librt.so.1 (0x0ebfd000) libm.so.6 => /lib/powerpc-linux-gnu/libm.so.6 (0x0eb0c000) libgcc_s.so.1 => /lib/powerpc-linux-gnu/libgcc_s.so.1 (0x0eacb000) libpthread.so.0 => /lib/powerpc-linux-gnu/libpthread.so.0 (0x0ea88000) libc.so.6 => /lib/powerpc-linux-gnu/libc.so.6
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
Hi T, found! this was last bad a select git bisect bad Bisecting: 101 revisions left to test after this (roughly 7 steps) [f68419eee9a966f5a915314c43cda6778f976a77] Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging this is the good git bisect good Bisecting: 58 revisions left to test after this (roughly 6 steps) [14fccfa91ecac7af36ac03dc1c2bb9a1d7fbca26] Merge remote-tracking branch 'remotes/lalrae/tags/mips-20160513' into staging Ciao Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: New Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ec6f000) libusb-1.0.so.0 =>
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
but what i see in this working there isnt your sdl2 patch. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: New Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ec6f000) libusb-1.0.so.0 => /lib/powerpc-linux-gnu/libusb-1.0.so.0 (0x0ec2e000) librt.so.1 => /lib/powerpc-linux-gnu/librt.so.1 (0x0ebfd000) libm.so.6 => /lib/powerpc-linux-gnu/libm.so.6 (0x0eb0c000) libgcc_s.so.1 => /lib/powerpc-linux-gnu/libgcc_s.so.1 (0x0eacb000) libpthread.so.0 => /lib/powerpc-linux-gnu/libpthread.so.0 (0x0ea88000) libc.so.6 => /lib/powerpc-linux-gnu/libc.so.6 (0x0e8d4000) libdrm.so.2 =>
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
Hi T, thanks for the infos i will report ASAP -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: New Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ec6f000) libusb-1.0.so.0 => /lib/powerpc-linux-gnu/libusb-1.0.so.0 (0x0ec2e000) librt.so.1 => /lib/powerpc-linux-gnu/librt.so.1 (0x0ebfd000) libm.so.6 => /lib/powerpc-linux-gnu/libm.so.6 (0x0eb0c000) libgcc_s.so.1 => /lib/powerpc-linux-gnu/libgcc_s.so.1 (0x0eacb000) libpthread.so.0 => /lib/powerpc-linux-gnu/libpthread.so.0 (0x0ea88000) libc.so.6 => /lib/powerpc-linux-gnu/libc.so.6 (0x0e8d4000) libdrm.so.2 =>
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
Hi T, i can gave a try ... i never used "git bisect" i have to use it with the executable? with "git bisect log" or somthing else? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: New Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ec6f000) libusb-1.0.so.0 => /lib/powerpc-linux-gnu/libusb-1.0.so.0 (0x0ec2e000) librt.so.1 => /lib/powerpc-linux-gnu/librt.so.1 (0x0ebfd000) libm.so.6 => /lib/powerpc-linux-gnu/libm.so.6 (0x0eb0c000) libgcc_s.so.1 => /lib/powerpc-linux-gnu/libgcc_s.so.1 (0x0eacb000) libpthread.so.0 => /lib/powerpc-linux-gnu/libpthread.so.0 (0x0ea88000) libc.so.6 =>
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
Hi T, i just make a test on My Quad G5 and Mate 15.10 and here i have the same issue ... no video on last 2.6. I think this issue is present on all ppc world -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: New Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ec6f000) libusb-1.0.so.0 => /lib/powerpc-linux-gnu/libusb-1.0.so.0 (0x0ec2e000) librt.so.1 => /lib/powerpc-linux-gnu/librt.so.1 (0x0ebfd000) libm.so.6 => /lib/powerpc-linux-gnu/libm.so.6 (0x0eb0c000) libgcc_s.so.1 => /lib/powerpc-linux-gnu/libgcc_s.so.1 (0x0eacb000) libpthread.so.0 => /lib/powerpc-linux-gnu/libpthread.so.0 (0x0ea88000)
[Qemu-devel] [Bug 1581796] Re: console-gl.c:96:surface_gl_create_texture:code should not be reached
I will send your old sdl patches? i dont like to tief code ;-) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1581796 Title: console-gl.c:96:surface_gl_create_texture:code should not be reached Status in QEMU: Fix Committed Bug description: Facing this if i enable gtk,gl option same is with sd2 gl options. PowerPc P5020 4gb ram Ubuntu Mate 16:04 tested on RadeonSi 7750HD 2gb ddr3 r600 6570 2gb ddr3 Masa 11.2.2 and 11.3 dev same issue come on swrast mode Thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1581796/+subscriptions
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
one shot of qemu-system-i386 2.6 old version, oldest was working ** Attachment added: "Screenshot from 2016-07-18 14-37-51.png" https://bugs.launchpad.net/qemu/+bug/1603636/+attachment/4702811/+files/Screenshot%20from%202016-07-18%2014-37-51.png -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: New Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ec6f000) libusb-1.0.so.0 => /lib/powerpc-linux-gnu/libusb-1.0.so.0 (0x0ec2e000) librt.so.1 => /lib/powerpc-linux-gnu/librt.so.1 (0x0ebfd000) libm.so.6 => /lib/powerpc-linux-gnu/libm.so.6 (0x0eb0c000) libgcc_s.so.1 => /lib/powerpc-linux-gnu/libgcc_s.so.1
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
Hi tony this are my configurations command i use for run the qemu-system-i386 note it is working on 2.5.1 and 2.6 old release attached a shot you can see all is working in previous versions of 2.6 Aros: qemu-system-i386 -m 2047 -drive file=/mnt/c7a1331a-6bfe-436e-b43d-fe2afead48e9/Aros.img,id=disk0,format=raw -net nic,model=rtl8139 -net user,smb=/home/amigaone/shared/ -vga vmware -balloon none -display sdl -cpu athlon -mem-prealloc -device virtio-scsi-pci,id=scsi -soundhw es1370 -cdrom /home/amigaone/emulators.iso Win98: qemu-system-i386 -m 256 -drive file=/media/amigaone/mame/vhd/win98.img,id=disk0,format=raw -vga cirrus -display sdl -balloon none -mem-prealloc -device virtio-scsi-pci,id=scsi -rtc clock=host,base=localtime -serial none -parallel none winXP: qemu-system-i386 -m 2047 -drive file=/media/amigaone/mame/vhd/xp_black,id=disk0,format=raw -net nic,model=rtl8139 -net user,smb=/home/amigaone/shared/ -vga virtio -balloon virtio -display sdl -cpu athlon -mem-prealloc but qemu is working if only i open it thru qemu-system-i386 ... i have default setting with 128mb and bios running ... with lastest git not only "Guest has not initialized the display yet " or quitting like i described before... This is my complete configure from beginning ./configure --with-sdlabi=2.0 --audio-drv-list=pa,sdl --target- list=i386-softmmu,ppc-softmmu,ppc64-softmmu,ppcemb-softmmu ERROR: DTC (libfdt) version >= 1.4.0 not present. Your options: (1) Preferred: Install the DTC (libfdt) devel package (2) Fetch the DTC submodule, using: git submodule update --init dtc amigaone@Amigaone:~/src/qemu$ git submodule update --init dtc Submodule 'dtc' (git://git.qemu-project.org/dtc.git) registered for path 'dtc' Cloning into 'dtc'... remote: Counting objects: 2778, done. remote: Compressing objects: 100% (1692/1692), done. remote: Total 2778 (delta 2058), reused 1415 (delta 1056) Receiving objects: 100% (2778/2778), 654.26 KiB | 376.00 KiB/s, done. Resolving deltas: 100% (2058/2058), done. Checking connectivity... done. Submodule path 'dtc': checked out '65cc4d2748a2c2e6f27f1cf39e07a5dbabd80ebf' amigaone@Amigaone:~/src/qemu$ ./configure --with-sdlabi=2.0 --audio-drv-list=pa,sdl --target-list=i386-softmmu,ppc-softmmu,ppc64-softmmu,ppcemb-softmmu Install prefix/usr/local BIOS directory/usr/local/share/qemu binary directory /usr/local/bin library directory /usr/local/lib module directory /usr/local/lib/qemu libexec directory /usr/local/libexec include directory /usr/local/include config directory /usr/local/etc local state directory /usr/local/var Manual directory /usr/local/share/man ELF interp prefix /usr/gnemul/qemu-%M Source path /home/amigaone/src/qemu C compilercc Host C compiler cc C++ compiler c++ Objective-C compiler clang ARFLAGS rv CFLAGS-O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc-linux-gnu/glib-2.0/include -g QEMU_CFLAGS -I/usr/include/pixman-1 -I$(SRC_PATH)/dtc/libfdt -Werror -DHAS_LIBSSH2_SFTP_FSYNC -m32 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition -Wtype-limits -fstack-protector-strong -I/usr/include/p11-kit-1 -I/usr/local/include -I/usr/include/libpng16 -I/usr/include/libusb-1.0 LDFLAGS -Wl,--warn-common -m32 -g make make install install pythonpython -B smbd /usr/sbin/smbd module supportno host CPU ppc host big endian yes target list i386-softmmu ppc-softmmu ppc64-softmmu ppcemb-softmmu tcg debug enabled no gprof enabled no sparse enabledno strip binariesyes profiler no static build no pixmansystem SDL support yes (2.0.4) GTK support yes (2.24.30) GTK GL supportno VTE support no TLS priority NORMAL GNUTLS supportyes GNUTLS rndyes libgcrypt no libgcrypt kdf no nettleyes (3.2) nettle kdfyes libtasn1 yes curses supportyes virgl support yes curl support yes mingw32 support no Audio drivers pa sdl Block whitelist (rw) Block whitelist (ro) VirtFS supportno VNC support yes VNC SASL support no VNC JPEG support yes VNC PNG support yes xen support no brlapi supportno bluez supportno Documentation yes PIE no vde support no netmap supportno Linux AIO support no ATTR/XATTR support yes Install blobs yes KVM support yes RDMA support no TCG interpreter no fdt support yes preadv supportyes fdatasync yes madvise yes
[Qemu-devel] [Bug 1581796] Re: console-gl.c:96:surface_gl_create_texture:code should not be reached
i think the best will be it included in the stable branch for have a full working qemu options -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1581796 Title: console-gl.c:96:surface_gl_create_texture:code should not be reached Status in QEMU: Fix Committed Bug description: Facing this if i enable gtk,gl option same is with sd2 gl options. PowerPc P5020 4gb ram Ubuntu Mate 16:04 tested on RadeonSi 7750HD 2gb ddr3 r600 6570 2gb ddr3 Masa 11.2.2 and 11.3 dev same issue come on swrast mode Thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1581796/+subscriptions
[Qemu-devel] [Bug 1603636] Re: Guest has not initialized the display yet on ubuntu 16.10 PPC
Hi T, yes it is the emulated i386 machine qemu-system-i386 and it was working since something change in 2.6. but issue is present in ppc machine too. dint try the kvm because on ppcemb there is not vga output. I had try the 2.5.1 and build and work and confirmed the issue is present only in 2.6 ususally i build it with this : ./configure --with-sdlabi=2.0 --audio-drv-list=pa,sdl --target-list=i386-softmmu,ppc-softmmu,ppc64-softmmu i had been try with sdlabi=1.2 and without audio and without target list but have the same issue. after work i will write my configure output probably can help? Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1603636 Title: Guest has not initialized the display yet on ubuntu 16.10 PPC Status in QEMU: New Bug description: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca)
[Qemu-devel] [Bug 1603636] [NEW] Guest has not initialized the display yet on ubuntu 16.10 PPC
Public bug reported: Hi tested with all kind of configure, with all kind of machine types but i have the same issue ... on lastest quemo 2.6 "Guest has not initialized the display yet" note with lastest git repository the situation become worst because on i386-softmmu i have the message but qemu exit alone because looklike there is not a bios this is gdb of i386-softmmu (gdb) run Starting program: /home/amigaone/src/qemu/i386-softmmu/qemu-system-i386 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xf7f78b70 (LWP 25074)] [New Thread 0xf770bb70 (LWP 25075)] [New Thread 0xf6dfdb70 (LWP 25076)] [New Thread 0xf65fdb70 (LWP 25077)] [New Thread 0xf3337b70 (LWP 25078)] [New Thread 0xe4146b70 (LWP 25087)] qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a This usually means one of the following happened: (1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine) (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end (3) Your guest kernel has a bug and crashed by jumping off into nowhere This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine. If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point. Execution cannot continue; stopping here. [Thread 0xe4146b70 (LWP 25087) exited] [Thread 0xf65fdb70 (LWP 25077) exited] [Thread 0xf6dfdb70 (LWP 25076) exited] [Thread 0xf770bb70 (LWP 25075) exited] [Thread 0xf7f78b70 (LWP 25074) exited] [Thread 0xf7f7c000 (LWP 25070) exited] [Inferior 1 (process 25070) exited with code 01] this is my ldd ldd ./qemu-system-i386 linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0fe55000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fcf2000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fcb1000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc1) libssh2.so.1 => /usr/lib/powerpc-linux-gnu/libssh2.so.1 (0x0fbbf000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fb7e000) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fadd000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0faac000) libnuma.so.1 => /usr/lib/powerpc-linux-gnu/libnuma.so.1 (0x0fa79000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fa28000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0f9d7000) libuuid.so.1 => /lib/powerpc-linux-gnu/libuuid.so.1 (0x0f9a6000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f945000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f8d4000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f77d000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f71c000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f5ca000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f0e6000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f005000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0eec3000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0ee72000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0edf1000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0eca) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ec6f000) libusb-1.0.so.0 => /lib/powerpc-linux-gnu/libusb-1.0.so.0 (0x0ec2e000) librt.so.1 => /lib/powerpc-linux-gnu/librt.so.1 (0x0ebfd000) libm.so.6 => /lib/powerpc-linux-gnu/libm.so.6 (0x0eb0c000) libgcc_s.so.1 => /lib/powerpc-linux-gnu/libgcc_s.so.1 (0x0eacb000) libpthread.so.0 => /lib/powerpc-linux-gnu/libpthread.so.0 (0x0ea88000) libc.so.6 => /lib/powerpc-linux-gnu/libc.so.6 (0x0e8d4000) libdrm.so.2 => /usr/lib/powerpc-linux-gnu/libdrm.so.2 (0x0e8a3000) libdl.so.2 => /lib/powerpc-linux-gnu/libdl.so.2 (0x0e872000) libexpat.so.1 => /lib/powerpc-linux-gnu/libexpat.so.1 (0x0e821000) libxcb.so.1 => /usr/lib/powerpc-linux-gnu/libxcb.so.1 (0x0e7e) libidn.so.11 => /lib/powerpc-linux-gnu/libidn.so.11 (0x0e77f000) librtmp.so.1 =>
[Qemu-devel] [Bug 1581796] Re: console-gl.c:96:surface_gl_create_texture:code should not be reached
Hi T.Huth, is possible add the sdl patches on BigEndian on Qemu 2.5.1 ? the lastest are not initializing the display i dont understand what appening with last qemu on Big Endian. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1581796 Title: console-gl.c:96:surface_gl_create_texture:code should not be reached Status in QEMU: Fix Committed Bug description: Facing this if i enable gtk,gl option same is with sd2 gl options. PowerPc P5020 4gb ram Ubuntu Mate 16:04 tested on RadeonSi 7750HD 2gb ddr3 r600 6570 2gb ddr3 Masa 11.2.2 and 11.3 dev same issue come on swrast mode Thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1581796/+subscriptions
[Qemu-devel] [Bug 1581796] Re: console-gl.c:96:surface_gl_create_texture:code should not be reached
Thomas, thank you very much for your fix Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1581796 Title: console-gl.c:96:surface_gl_create_texture:code should not be reached Status in QEMU: Fix Committed Bug description: Facing this if i enable gtk,gl option same is with sd2 gl options. PowerPc P5020 4gb ram Ubuntu Mate 16:04 tested on RadeonSi 7750HD 2gb ddr3 r600 6570 2gb ddr3 Masa 11.2.2 and 11.3 dev same issue come on swrast mode Thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1581796/+subscriptions
[Qemu-devel] [Bug 1581796] Re: console-gl.c:96:surface_gl_create_texture:code should not be reached
Hi T. yes the official git 2.6 from qemu.org No video come with all type of machine i had been tested: ppc, ppc64, i386, x86_64 , but this only on Ubuntu 16.10 on Fedora 24 all is working right . I think there is something broken on ubuntu 16.10. ah sorry i forgot ... on Fedora 24 qemu 2.6.0 with the patch is working Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1581796 Title: console-gl.c:96:surface_gl_create_texture:code should not be reached Status in QEMU: New Bug description: Facing this if i enable gtk,gl option same is with sd2 gl options. PowerPc P5020 4gb ram Ubuntu Mate 16:04 tested on RadeonSi 7750HD 2gb ddr3 r600 6570 2gb ddr3 Masa 11.2.2 and 11.3 dev same issue come on swrast mode Thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1581796/+subscriptions
[Qemu-devel] [Bug 1581796] Re: console-gl.c:96:surface_gl_create_texture:code should not be reached
Hi T, tested on 2.5.1 and the patch is working. it can be included in the mainstream Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1581796 Title: console-gl.c:96:surface_gl_create_texture:code should not be reached Status in QEMU: New Bug description: Facing this if i enable gtk,gl option same is with sd2 gl options. PowerPc P5020 4gb ram Ubuntu Mate 16:04 tested on RadeonSi 7750HD 2gb ddr3 r600 6570 2gb ddr3 Masa 11.2.2 and 11.3 dev same issue come on swrast mode Thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1581796/+subscriptions
[Qemu-devel] [Bug 1581796] Re: console-gl.c:96:surface_gl_create_texture:code should not be reached
Hi T. i been test and build your patch with the qemu 2.6 on mate 16.10 and look like not crashing when qemu open like before but i continue have the black display here,look like the emulated hardware have a issue someware. (check the attached image)... the strange of this issue is it was not present before and not is relative something about sdl or gtk . I try all the options available adding a bios, changing the vga the machine type, gave a cpu option but nothing... all the time the same issue. About your sdl parch: I will check your patch on qemu 2.5.1 and on fedora 24 for confirm everything working right. thanks for you parches Luigi ** Attachment added: "qemu_2.6.png" https://bugs.launchpad.net/qemu/+bug/1581796/+attachment/4678054/+files/qemu_2.6.png -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1581796 Title: console-gl.c:96:surface_gl_create_texture:code should not be reached Status in QEMU: New Bug description: Facing this if i enable gtk,gl option same is with sd2 gl options. PowerPc P5020 4gb ram Ubuntu Mate 16:04 tested on RadeonSi 7750HD 2gb ddr3 r600 6570 2gb ddr3 Masa 11.2.2 and 11.3 dev same issue come on swrast mode Thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1581796/+subscriptions
[Qemu-devel] [Bug 1588473] Re: Qemu Mate 16.10 and Gtk dont build
Hi T, tested but dont build with the patch too... gtk abi 3.0 are away for now -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1588473 Title: Qemu Mate 16.10 and Gtk dont build Status in QEMU: New Bug description: when i try to build last qemu 2.6 on 16.10 of ubuntu mate i have this. note on 16.04 was building without problem LINK i386-softmmu/qemu-system-i386 ../ui/gtk.o: In function `gd_get_pointer': /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer' ../ui/gtk.o: In function `gd_grab_update': /home/amigaone/src/qemu/ui/gtk.c:1339: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:1353: undefined reference to `gdk_seat_grab' /home/amigaone/src/qemu/ui/gtk.c:1356: undefined reference to `gdk_seat_ungrab' ../ui/gtk.o: In function `gd_get_pointer': /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer' collect2: error: ld returned 1 exit status To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1588473/+subscriptions
[Qemu-devel] [Bug 1581796] Re: console-gl.c:96:surface_gl_create_texture:code should not be reached
here is the result qemu-2.5.1.1/i386-softmmu$ ./qemu-system-i386 -display sdl,gl=on Pixel format = 0x20020888 ** ERROR:ui/console-gl.c:96:surface_gl_create_texture: code should not be reached Aborted (core dumped) In case is needed this is my ldd linux-vdso32.so.1 => (0x0010) libvirglrenderer.so.0 => /usr/local/lib/libvirglrenderer.so.0 (0x0ff8a000) libepoxy.so.0 => /usr/lib/powerpc-linux-gnu/libepoxy.so.0 (0x0fe86000) libX11.so.6 => /usr/lib/powerpc-linux-gnu/libX11.so.6 (0x0fd23000) libz.so.1 => /lib/powerpc-linux-gnu/libz.so.1 (0x0fce2000) libcurl-gnutls.so.4 => /usr/lib/powerpc-linux-gnu/libcurl-gnutls.so.4 (0x0fc41000) libbz2.so.1.0 => /lib/powerpc-linux-gnu/libbz2.so.1.0 (0x0fc0) libpixman-1.so.0 => /usr/lib/powerpc-linux-gnu/libpixman-1.so.0 (0x0fb5f000) libutil.so.1 => /lib/powerpc-linux-gnu/libutil.so.1 (0x0fb2e000) libncurses.so.5 => /lib/powerpc-linux-gnu/libncurses.so.5 (0x0fadd000) libtinfo.so.5 => /lib/powerpc-linux-gnu/libtinfo.so.5 (0x0fa8c000) libpulse.so.0 => /usr/lib/powerpc-linux-gnu/libpulse.so.0 (0x0fa1b000) libpng16.so.16 => /usr/lib/powerpc-linux-gnu/libpng16.so.16 (0x0f9ba000) libjpeg.so.8 => /usr/lib/powerpc-linux-gnu/libjpeg.so.8 (0x0f949000) libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x0f7f2000) libnettle.so.6 => /usr/lib/powerpc-linux-gnu/libnettle.so.6 (0x0f791000) libgnutls.so.30 => /usr/lib/powerpc-linux-gnu/libgnutls.so.30 (0x0f63f000) libgtk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0 (0x0f15b000) libgdk-x11-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk-x11-2.0.so.0 (0x0f07a000) libcairo.so.2 => /usr/lib/powerpc-linux-gnu/libcairo.so.2 (0x0ef38000) libgdk_pixbuf-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0eee7000) libgobject-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0 (0x0ee66000) libglib-2.0.so.0 => /lib/powerpc-linux-gnu/libglib-2.0.so.0 (0x0ed15000) libsnappy.so.1 => /usr/lib/powerpc-linux-gnu/libsnappy.so.1 (0x0ece4000) librt.so.1 => /lib/powerpc-linux-gnu/librt.so.1 (0x0ecb3000) libm.so.6 => /lib/powerpc-linux-gnu/libm.so.6 (0x0ebc2000) libgcc_s.so.1 => /lib/powerpc-linux-gnu/libgcc_s.so.1 (0x0eb81000) libpthread.so.0 => /lib/powerpc-linux-gnu/libpthread.so.0 (0x0eb3e000) libc.so.6 => /lib/powerpc-linux-gnu/libc.so.6 (0x0e98a000) libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x0e959000) libdrm.so.2 => /usr/lib/powerpc-linux-gnu/libdrm.so.2 (0x0e928000) libdl.so.2 => /lib/powerpc-linux-gnu/libdl.so.2 (0x0e8f7000) libxcb.so.1 => /usr/lib/powerpc-linux-gnu/libxcb.so.1 (0x0e8b6000) libidn.so.11 => /usr/lib/powerpc-linux-gnu/libidn.so.11 (0x0e855000) librtmp.so.1 => /usr/lib/powerpc-linux-gnu/librtmp.so.1 (0x0e814000) libgssapi_krb5.so.2 => /usr/lib/powerpc-linux-gnu/libgssapi_krb5.so.2 (0x0e7a3000) liblber-2.4.so.2 => /usr/lib/powerpc-linux-gnu/liblber-2.4.so.2 (0x0e772000) libldap_r-2.4.so.2 => /usr/lib/powerpc-linux-gnu/libldap_r-2.4.so.2 (0x0e6f) /lib/ld.so.1 (0x203e7000) libjson-c.so.3 => /lib/powerpc-linux-gnu/libjson-c.so.3 (0x0e6bf000) libpulsecommon-8.0.so => /usr/lib/powerpc-linux-gnu/pulseaudio/libpulsecommon-8.0.so (0x0e61e000) libdbus-1.so.3 => /lib/powerpc-linux-gnu/libdbus-1.so.3 (0x0e5ad000) libsndio.so.6.1 => /usr/lib/powerpc-linux-gnu/libsndio.so.6.1 (0x0e57a000) libp11-kit.so.0 => /usr/lib/powerpc-linux-gnu/libp11-kit.so.0 (0x0e4f9000) libtasn1.so.6 => /usr/lib/powerpc-linux-gnu/libtasn1.so.6 (0x0e4b8000) libhogweed.so.4 => /usr/lib/powerpc-linux-gnu/libhogweed.so.4 (0x0e457000) libgmp.so.10 => /usr/lib/powerpc-linux-gnu/libgmp.so.10 (0x0e3b6000) libgmodule-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgmodule-2.0.so.0 (0x0e385000) libpangocairo-1.0.so.0 => /usr/lib/powerpc-linux-gnu/libpangocairo-1.0.so.0 (0x0e354000) libXfixes.so.3 => /usr/lib/powerpc-linux-gnu/libXfixes.so.3 (0x0e32e000) libatk-1.0.so.0 => /usr/lib/powerpc-linux-gnu/libatk-1.0.so.0 (0x0e2dd000) libgio-2.0.so.0 => /usr/lib/powerpc-linux-gnu/libgio-2.0.so.0 (0x0e0eb000) libpangoft2-1.0.so.0 => /usr/lib/powerpc-linux-gnu/libpangoft2-1.0.so.0 (0x0e0aa000) libpango-1.0.so.0 => /usr/lib/powerpc-linux-gnu/libpango-1.0.so.0 (0x0e039000) libfontconfig.so.1 => /usr/lib/powerpc-linux-gnu/libfontconfig.so.1 (0x0dfc4000) libXrender.so.1 => /usr/lib/powerpc-linux-gnu/libXrender.so.1 (0x0df93000) libXinerama.so.1 => /usr/lib/powerpc-linux-gnu/libXinerama.so.1 (0x0df7) libXi.so.6 => /usr/lib/powerpc-linux-gnu/libXi.so.6 (0x0df2f000) libXrandr.so.2 => /usr/lib/powerpc-linux-gnu/libXrandr.so.2 (0x0defe000) libXcursor.so.1 =>
[Qemu-devel] [Bug 1581796] Re: console-gl.c:96:surface_gl_create_texture:code should not be reached
Will report soon -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1581796 Title: console-gl.c:96:surface_gl_create_texture:code should not be reached Status in QEMU: New Bug description: Facing this if i enable gtk,gl option same is with sd2 gl options. PowerPc P5020 4gb ram Ubuntu Mate 16:04 tested on RadeonSi 7750HD 2gb ddr3 r600 6570 2gb ddr3 Masa 11.2.2 and 11.3 dev same issue come on swrast mode Thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1581796/+subscriptions
[Qemu-devel] [Bug 1555076] Re: Qemu 2.5 dont start with sdl, gl=on or gtk, gl=on
Sorry T, i forget had been reported and duplicate the bug report. can merge or close this one. i will check with your suggestion and report. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1555076 Title: Qemu 2.5 dont start with sdl,gl=on or gtk,gl=on Status in QEMU: New Bug description: with this config line qemu-system-i386 -m 2047 -hda /dev/sda3 -display sdl,gl=on -sdl -vga virtio -cdrom xenial-desktop-i386.iso i have this exit ERROR:ui/console-gl.c:95:surface_gl_create_texture: code should not be reached same is i use this: qemu-system-i386 -m 2047 -hda /dev/sda3 -display gtk,gl=on -sdl -vga virtio -cdrom xenial-desktop-i386.iso ERROR:ui/console-gl.c:95:surface_gl_create_texture: code should not be reached My Os i Debian Jessie on P5020 PPC64 4GB ram GPU RadeonHD . Configure gave me gl ok, sdl ok , Virtio and Virgl OK . My Mesa are the 11.3 dev ... the same issue was found on oldest and stable release of mesa . OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TURKS (DRM 2.43.0) OpenGL version string: 2.1 Mesa 11.3.0-devel (git-3146014) OpenGL shading language version string: 1.30 OpenGL ES profile version string: OpenGL ES 2.0 Mesa 11.3.0-devel (git-3146014) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 Thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1555076/+subscriptions
[Qemu-devel] [Bug 1568356] Re: ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch:
Hi T, i can confirm the patch is working . sdl2 switch screen is fixed . i had been tested it on 2.5.1 and is ok. I think will be better add this in the qemu git next step sdl gl ;-) Many thanks Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1568356 Title: ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch: Status in QEMU: New Bug description: when display sdl is selected in display switch resolution qemu exit with a core dump with this message ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch: code should not be reached My Machine is a Cyrus+ PowerPc P5020 4gb ram Radeon 6570 2Gb This issue affected PowerMac G5 quad too . My distro is Mate 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1568356/+subscriptions
[Qemu-devel] [Bug 1568356] Re: ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch:
Hi T. I been installed the patch . note im testing the fedora 24 and the last mate 16.10 on fedora 24 qemu 2.6 all build ok but when i run the qemu i have an illegal istruction and the crash of qemu... dont worry about im sure is not a qemu issue but some unstable library on fedora because this is effecting all sdl software. On mate 16.10 qemu 2.6 is not building at all i had been reported the issue about . I cant say if the patch is working or not since the two distro will be more stable. i will check later if the oldest qemu 2.5.x with the applied patch will build on mate 16 and hope gave a positive feedback. Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1568356 Title: ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch: Status in QEMU: New Bug description: when display sdl is selected in display switch resolution qemu exit with a core dump with this message ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch: code should not be reached My Machine is a Cyrus+ PowerPc P5020 4gb ram Radeon 6570 2Gb This issue affected PowerMac G5 quad too . My distro is Mate 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1568356/+subscriptions
[Qemu-devel] [Bug 1568356] Re: ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch:
Hi T.
i had been add the code line but cc exit with error and dont buil
CCui/console-gl.o
ui/console-gl.c: In function ‘surface_gl_create_texture’:
ui/console-gl.c:96:52: error: ‘scon’ undeclared (first use in this function)
printf("Surface format is: %x\n", surface_format(scon->surface));
^
ui/console-gl.c:96:52: note: each undeclared identifier is reported only once
for each function it appears in
/home/amigaone/src/qemu/rules.mak:57: recipe for target 'ui/console-gl.o' failed
make: *** [ui/console-gl.o] Error 1
make: *** Waiting for unfinished jobs
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1568356
Title:
ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch:
Status in QEMU:
New
Bug description:
when display sdl is selected in display switch resolution qemu exit
with a core dump with this message
ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch: code should not be reached
My Machine is a Cyrus+ PowerPc P5020 4gb ram Radeon 6570 2Gb
This issue affected PowerMac G5 quad too .
My distro is Mate 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1568356/+subscriptions
[Qemu-devel] [Bug 1588473] [NEW] Qemu Mate 16.10 and Gtk dont build
Public bug reported: when i try to build last qemu 2.6 on 16.10 of ubuntu mate i have this. note on 16.04 was building without problem LINK i386-softmmu/qemu-system-i386 ../ui/gtk.o: In function `gd_get_pointer': /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer' ../ui/gtk.o: In function `gd_grab_update': /home/amigaone/src/qemu/ui/gtk.c:1339: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:1353: undefined reference to `gdk_seat_grab' /home/amigaone/src/qemu/ui/gtk.c:1356: undefined reference to `gdk_seat_ungrab' ../ui/gtk.o: In function `gd_get_pointer': /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer' collect2: error: ld returned 1 exit status ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1588473 Title: Qemu Mate 16.10 and Gtk dont build Status in QEMU: New Bug description: when i try to build last qemu 2.6 on 16.10 of ubuntu mate i have this. note on 16.04 was building without problem LINK i386-softmmu/qemu-system-i386 ../ui/gtk.o: In function `gd_get_pointer': /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer' ../ui/gtk.o: In function `gd_grab_update': /home/amigaone/src/qemu/ui/gtk.c:1339: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:1353: undefined reference to `gdk_seat_grab' /home/amigaone/src/qemu/ui/gtk.c:1356: undefined reference to `gdk_seat_ungrab' ../ui/gtk.o: In function `gd_get_pointer': /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat' /home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer' collect2: error: ld returned 1 exit status To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1588473/+subscriptions
[Qemu-devel] [Bug 1581796] [NEW] console-gl.c:96:surface_gl_create_texture:code should not be reached
Public bug reported: Facing this if i enable gtk,gl option same is with sd2 gl options. PowerPc P5020 4gb ram Ubuntu Mate 16:04 tested on RadeonSi 7750HD 2gb ddr3 r600 6570 2gb ddr3 Masa 11.2.2 and 11.3 dev same issue come on swrast mode Thanks Luigi ** Affects: qemu Importance: Undecided Status: New ** Description changed: Facing this if i enable gtk,gl option same is with sd2 gl options. PowerPc P5020 4gb ram Ubuntu Mate 16:04 - tested on + tested on RadeonSi 7750HD 2gb ddr3 r600 6570 2gb ddr3 + + Masa 12.2.2 and 12.3 dev + same issue come on swrast mode Thanks Luigi ** Description changed: Facing this if i enable gtk,gl option same is with sd2 gl options. PowerPc P5020 4gb ram Ubuntu Mate 16:04 tested on RadeonSi 7750HD 2gb ddr3 r600 6570 2gb ddr3 - Masa 12.2.2 and 12.3 dev + Masa 11.2.2 and 11.3 dev same issue come on swrast mode - Thanks Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1581796 Title: console-gl.c:96:surface_gl_create_texture:code should not be reached Status in QEMU: New Bug description: Facing this if i enable gtk,gl option same is with sd2 gl options. PowerPc P5020 4gb ram Ubuntu Mate 16:04 tested on RadeonSi 7750HD 2gb ddr3 r600 6570 2gb ddr3 Masa 11.2.2 and 11.3 dev same issue come on swrast mode Thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1581796/+subscriptions
[Qemu-devel] [Bug 1579565] Re: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
Hi Perter, probalby ... i found something wrongs inside my ppc64 library , im clearing and reinstall the glib . report it soon -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1579565 Title: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. Status in QEMU: Invalid Bug description: cont build from last 2.6 rc4 ~/Downloads/qemu-2.6.0-rc4$ ./configure ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. You probably need to set PKG_CONFIG_LIBDIR to point to the right pkg-config files for your build target Os Ubuntu Mate 16.04 PPC64 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1579565/+subscriptions
[Qemu-devel] [Bug 1579565] Re: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
Yes Fixed guys. configure reply right . can close this bug , that was not a qemu bug. ** Changed in: qemu Status: Fix Committed => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1579565 Title: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. Status in QEMU: Invalid Bug description: cont build from last 2.6 rc4 ~/Downloads/qemu-2.6.0-rc4$ ./configure ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. You probably need to set PKG_CONFIG_LIBDIR to point to the right pkg-config files for your build target Os Ubuntu Mate 16.04 PPC64 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1579565/+subscriptions
[Qemu-devel] [Bug 1579565] Re: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
rc5 same issue ./configure ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. You probably need to set PKG_CONFIG_LIBDIR to point to the right pkg-config files for your build target thanks -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1579565 Title: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. Status in QEMU: Fix Committed Bug description: cont build from last 2.6 rc4 ~/Downloads/qemu-2.6.0-rc4$ ./configure ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. You probably need to set PKG_CONFIG_LIBDIR to point to the right pkg-config files for your build target Os Ubuntu Mate 16.04 PPC64 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1579565/+subscriptions
[Qemu-devel] [Bug 1579565] Re: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
Hi Daniel i dont know from this last i have this issue other versions was building right . im affraid i deleted the rc3 i just make a test with 2.5.1 and you can see configure work, like was working in past. ** Attachment added: "qemu-configure" https://bugs.launchpad.net/qemu/+bug/1579565/+attachment/4659363/+files/qemu-configure -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1579565 Title: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. Status in QEMU: Fix Committed Bug description: cont build from last 2.6 rc4 ~/Downloads/qemu-2.6.0-rc4$ ./configure ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. You probably need to set PKG_CONFIG_LIBDIR to point to the right pkg-config files for your build target Os Ubuntu Mate 16.04 PPC64 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1579565/+subscriptions
[Qemu-devel] [Bug 1579565] Re: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
Hi guys, did the patch but same error appear. i attached the config.log. ** Attachment added: "config.log" https://bugs.launchpad.net/qemu/+bug/1579565/+attachment/4659349/+files/config.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1579565 Title: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. Status in QEMU: Fix Committed Bug description: cont build from last 2.6 rc4 ~/Downloads/qemu-2.6.0-rc4$ ./configure ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. You probably need to set PKG_CONFIG_LIBDIR to point to the right pkg-config files for your build target Os Ubuntu Mate 16.04 PPC64 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1579565/+subscriptions
[Qemu-devel] [Bug 1579565] Re: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
Ok Daniel, will check and report. note usually on PPC we use ad default compiler GCC (5.3.1 now). I been installed clang 3.8 and will check report if all will right. Thanks -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1579565 Title: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. Status in QEMU: Fix Committed Bug description: cont build from last 2.6 rc4 ~/Downloads/qemu-2.6.0-rc4$ ./configure ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. You probably need to set PKG_CONFIG_LIBDIR to point to the right pkg-config files for your build target Os Ubuntu Mate 16.04 PPC64 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1579565/+subscriptions
[Qemu-devel] [Bug 1579565] Re: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
Peter just try forcing the cpp flagas with -m32 without success. On this rc configure dont start build .. CPPFLAGS="-m32" CFLAGS="-g -O2 -mcpu=e5500 -mno-altivec -mtune=e5500" CXXFLAGS="-m32 -g -O2 -mcpu=e5500 -mno-altivec -mtune=e5500" ./configure --disable-werror ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. You probably need to set PKG_CONFIG_LIBDIR to point to the right pkg-config files for your build target will check Stefan parch if something change and reports. Thanks -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1579565 Title: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. Status in QEMU: Fix Committed Bug description: cont build from last 2.6 rc4 ~/Downloads/qemu-2.6.0-rc4$ ./configure ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. You probably need to set PKG_CONFIG_LIBDIR to point to the right pkg-config files for your build target Os Ubuntu Mate 16.04 PPC64 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1579565/+subscriptions
[Qemu-devel] [Bug 1579565] Re: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
thanks for the infos Stefan i will check tomorrow and report. Peter, yes this is an issue of the powerpc64 of ubuntu/debian the ppc64 libraries are half ported usually i fix changing in the makefile -m32 where -m64 is call i will try to force the flags on configure of qemu too. i will report if success or not. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1579565 Title: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. Status in QEMU: Fix Committed Bug description: cont build from last 2.6 rc4 ~/Downloads/qemu-2.6.0-rc4$ ./configure ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. You probably need to set PKG_CONFIG_LIBDIR to point to the right pkg-config files for your build target Os Ubuntu Mate 16.04 PPC64 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1579565/+subscriptions
[Qemu-devel] [Bug 1579565] [NEW] ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
Public bug reported: cont build from last 2.6 rc4 ~/Downloads/qemu-2.6.0-rc4$ ./configure ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. You probably need to set PKG_CONFIG_LIBDIR to point to the right pkg-config files for your build target Os Ubuntu Mate 16.04 PPC64 ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1579565 Title: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. Status in QEMU: New Bug description: cont build from last 2.6 rc4 ~/Downloads/qemu-2.6.0-rc4$ ./configure ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. You probably need to set PKG_CONFIG_LIBDIR to point to the right pkg-config files for your build target Os Ubuntu Mate 16.04 PPC64 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1579565/+subscriptions
[Qemu-devel] [Bug 1571084] [NEW] Qemu 2.x dont build on last Gtk dev 3.0+
Public bug reported: here the build exit ui/gtk.c: In function ‘gd_mouse_set’: ui/gtk.c:479:5: error: ‘gdk_display_get_device_manager’ is deprecated: Use 'gdk_display_get_default_seat' instead [-Werror=deprecated-declarations] mgr = gdk_display_get_device_manager(dpy); ^ In file included from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32:0, from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, from /usr/local/include/gtk-3.0/gdk/gdk.h:32, from /usr/local/include/gtk-3.0/gtk/gtk.h:30, from /home/amigaone/src/qemu/include/ui/gtk.h:9, from ui/gtk.c:42: /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:170:20: note: declared here GdkDeviceManager * gdk_display_get_device_manager (GdkDisplay *display); ^ ui/gtk.c:482:5: error: ‘gdk_device_manager_get_client_pointer’ is deprecated [-Werror=deprecated-declarations] gdk_device_warp(gdk_device_manager_get_client_pointer(mgr), ^ In file included from /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:32:0, from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32, from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, from /usr/local/include/gtk-3.0/gdk/gdk.h:32, from /usr/local/include/gtk-3.0/gtk/gtk.h:30, from /home/amigaone/src/qemu/include/ui/gtk.h:9, from ui/gtk.c:42: /usr/local/include/gtk-3.0/gdk/gdkdevicemanager.h:44:14: note: declared here GdkDevice * gdk_device_manager_get_client_pointer (GdkDeviceManager *device_manager); ^ ui/gtk.c: In function ‘gd_grab_devices’: ui/gtk.c:1316:5: error: ‘gdk_display_get_device_manager’ is deprecated: Use 'gdk_display_get_default_seat' instead [-Werror=deprecated-declarations] GdkDeviceManager *mgr = gdk_display_get_device_manager(display); ^ In file included from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32:0, from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, from /usr/local/include/gtk-3.0/gdk/gdk.h:32, from /usr/local/include/gtk-3.0/gtk/gtk.h:30, from /home/amigaone/src/qemu/include/ui/gtk.h:9, from ui/gtk.c:42: /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:170:20: note: declared here GdkDeviceManager * gdk_display_get_device_manager (GdkDisplay *display); ^ ui/gtk.c:1317:5: error: ‘gdk_device_manager_list_devices’ is deprecated [-Werror=deprecated-declarations] GList *devs = gdk_device_manager_list_devices(mgr, GDK_DEVICE_TYPE_MASTER); ^ In file included from /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:32:0, from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32, from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, from /usr/local/include/gtk-3.0/gdk/gdk.h:32, from /usr/local/include/gtk-3.0/gtk/gtk.h:30, from /home/amigaone/src/qemu/include/ui/gtk.h:9, from ui/gtk.c:42: /usr/local/include/gtk-3.0/gdk/gdkdevicemanager.h:41:14: note: declared here GList * gdk_device_manager_list_devices (GdkDeviceManager *device_manager, ^ ui/gtk.c:1327:13: error: ‘gdk_device_grab’ is deprecated: Use 'gdk_seat_grab' instead [-Werror=deprecated-declarations] gdk_device_grab(dev, win, GDK_OWNERSHIP_NONE, FALSE, ^ In file included from /usr/local/include/gtk-3.0/gdk/gdkdnd.h:33:0, from /usr/local/include/gtk-3.0/gdk/gdkevents.h:34, from /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:31, from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32, from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, from /usr/local/include/gtk-3.0/gdk/gdk.h:32, from /usr/local/include/gtk-3.0/gtk/gtk.h:30, from /home/amigaone/src/qemu/include/ui/gtk.h:9, from ui/gtk.c:42: /usr/local/include/gtk-3.0/gdk/gdkdevice.h:250:15: note: declared here GdkGrabStatus gdk_device_grab(GdkDevice*device, ^ ui/gtk.c:1330:13: error: ‘gdk_device_ungrab’ is deprecated: Use 'gdk_seat_ungrab' instead [-Werror=deprecated-declarations] gdk_device_ungrab(dev, GDK_CURRENT_TIME); ^ In file included from /usr/local/include/gtk-3.0/gdk/gdkdnd.h:33:0, from /usr/local/include/gtk-3.0/gdk/gdkevents.h:34, from /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:31, from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32, from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, from /usr/local/include/gtk-3.0/gdk/gdk.h:32, from /usr/local/include/gtk-3.0/gtk/gtk.h:30, from /home/amigaone/src/qemu/include/ui/gtk.h:9, from ui/gtk.c:42:
[Qemu-devel] [Bug 1569491] [NEW] qemu system i386 poor performance on e5500 core
Public bug reported: I had been tested with generic core net building or with mtune e5500 but i have the same result: performances are extremly low compared with other classes of powerpc cpu. The strange is the 5020 2ghz in all emulators been tested by me is comparable with a 970MP 2.7 ghz in speed and benchmarks but im facing the half of performance in i386-soft-mmu compared with a 2.5 ghz 970MP. ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1569491 Title: qemu system i386 poor performance on e5500 core Status in QEMU: New Bug description: I had been tested with generic core net building or with mtune e5500 but i have the same result: performances are extremly low compared with other classes of powerpc cpu. The strange is the 5020 2ghz in all emulators been tested by me is comparable with a 970MP 2.7 ghz in speed and benchmarks but im facing the half of performance in i386-soft-mmu compared with a 2.5 ghz 970MP. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1569491/+subscriptions
[Qemu-devel] [Bug 1568356] [NEW] ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch:
Public bug reported: when display sdl is selected in display switch resolution qemu exit with a core dump with this message ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch: code should not be reached My Machine is a Cyrus+ PowerPc P5020 4gb ram Radeon 6570 2Gb This issue affected PowerMac G5 quad too . My distro is Mate 16.04 ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1568356 Title: ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch: Status in QEMU: New Bug description: when display sdl is selected in display switch resolution qemu exit with a core dump with this message ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch: code should not be reached My Machine is a Cyrus+ PowerPc P5020 4gb ram Radeon 6570 2Gb This issue affected PowerMac G5 quad too . My distro is Mate 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1568356/+subscriptions
[Qemu-devel] [Bug 1555076] [NEW] Qemu 2.5 dont start with sdl, gl=on or gtk, gl=on
Public bug reported: with this config line qemu-system-i386 -m 2047 -hda /dev/sda3 -display sdl,gl=on -sdl -vga virtio -cdrom xenial-desktop-i386.iso i have this exit ERROR:ui/console-gl.c:95:surface_gl_create_texture: code should not be reached same is i use this: qemu-system-i386 -m 2047 -hda /dev/sda3 -display gtk,gl=on -sdl -vga virtio -cdrom xenial-desktop-i386.iso ERROR:ui/console-gl.c:95:surface_gl_create_texture: code should not be reached My Os i Debian Jessie on P5020 PPC64 4GB ram GPU RadeonHD . Configure gave me gl ok, sdl ok , Virtio and Virgl OK . My Mesa are the 11.3 dev ... the same issue was found on oldest and stable release of mesa . OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TURKS (DRM 2.43.0) OpenGL version string: 2.1 Mesa 11.3.0-devel (git-3146014) OpenGL shading language version string: 1.30 OpenGL ES profile version string: OpenGL ES 2.0 Mesa 11.3.0-devel (git-3146014) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 Thanks Luigi ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1555076 Title: Qemu 2.5 dont start with sdl,gl=on or gtk,gl=on Status in QEMU: New Bug description: with this config line qemu-system-i386 -m 2047 -hda /dev/sda3 -display sdl,gl=on -sdl -vga virtio -cdrom xenial-desktop-i386.iso i have this exit ERROR:ui/console-gl.c:95:surface_gl_create_texture: code should not be reached same is i use this: qemu-system-i386 -m 2047 -hda /dev/sda3 -display gtk,gl=on -sdl -vga virtio -cdrom xenial-desktop-i386.iso ERROR:ui/console-gl.c:95:surface_gl_create_texture: code should not be reached My Os i Debian Jessie on P5020 PPC64 4GB ram GPU RadeonHD . Configure gave me gl ok, sdl ok , Virtio and Virgl OK . My Mesa are the 11.3 dev ... the same issue was found on oldest and stable release of mesa . OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TURKS (DRM 2.43.0) OpenGL version string: 2.1 Mesa 11.3.0-devel (git-3146014) OpenGL shading language version string: 1.30 OpenGL ES profile version string: OpenGL ES 2.0 Mesa 11.3.0-devel (git-3146014) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 Thanks Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1555076/+subscriptions
[Qemu-devel] [Bug 1444081] Re: x86_64 heavy crash on PPC 64 host
** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1444081 Title: x86_64 heavy crash on PPC 64 host Status in QEMU: Fix Released Bug description: this appened to me with last 2.3.0 rc 2 qemu-system-x86-64 crash , with only 2047 or 1024 -m option and -hda set qemu: fatal: Trying to execute code outside RAM or ROM at 0x00181f9a000a EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=0009fff3 EFL=0046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 CCS= CCD= CCO=ADDB EFER= FCW=037f FSW= [ST=0] FTW=00 MXCSR=1f80 FPR0= FPR1= FPR2= FPR3= FPR4= FPR5= FPR6= FPR7= XMM00= XMM01= XMM02= XMM03= XMM04= XMM05= XMM06= XMM07= Annullato (core dump creato) Keep a good work My machine host G5 Quad , radeon hd 6570 2gb , 8gb ram ... host OS Lubuntu 14.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1444081/+subscriptions
[Qemu-devel] [Bug 1444081] Re: x86_64 heavy crash on PPC 64 host
Confirm the rc3 is working :) i will check other softmmu too in this last rc. small OT because i dont know where ask... One day will be possible have one emulated core for every host thread like now do WinUae with qemu core? Example: 64 power8 cpus emulate 64 x86 cpus in one virtual machine -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1444081 Title: x86_64 heavy crash on PPC 64 host Status in QEMU: New Bug description: this appened to me with last 2.3.0 rc 2 qemu-system-x86-64 crash , with only 2047 or 1024 -m option and -hda set qemu: fatal: Trying to execute code outside RAM or ROM at 0x00181f9a000a EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=0009fff3 EFL=0046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 CCS= CCD= CCO=ADDB EFER= FCW=037f FSW= [ST=0] FTW=00 MXCSR=1f80 FPR0= FPR1= FPR2= FPR3= FPR4= FPR5= FPR6= FPR7= XMM00= XMM01= XMM02= XMM03= XMM04= XMM05= XMM06= XMM07= Annullato (core dump creato) Keep a good work My machine host G5 Quad , radeon hd 6570 2gb , 8gb ram ... host OS Lubuntu 14.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1444081/+subscriptions
[Qemu-devel] [Bug 1444081] [NEW] x86_64 heavy crash on PPC 64 host
Public bug reported: this appened to me with last 2.3.0 rc 2 qemu-system-x86-64 crash , with only 2047 or 1024 -m option and -hda set qemu: fatal: Trying to execute code outside RAM or ROM at 0x00181f9a000a EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=0009fff3 EFL=0046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 CCS= CCD= CCO=ADDB EFER= FCW=037f FSW= [ST=0] FTW=00 MXCSR=1f80 FPR0= FPR1= FPR2= FPR3= FPR4= FPR5= FPR6= FPR7= XMM00= XMM01= XMM02= XMM03= XMM04= XMM05= XMM06= XMM07= Annullato (core dump creato) Keep a good work My machine host G5 Quad , radeon hd 6570 2gb , 8gb ram ... host OS Lubuntu 14.04.2 ** Affects: qemu Importance: Undecided Status: New ** Tags: crash host ppc x86 ** Description changed: this appened to me with last 2.3.0 rc 2 qemu: fatal: Trying to execute code outside RAM or ROM at 0x00181f9a000a EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=0009fff3 EFL=0046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= - DR0= DR1= DR2= DR3= + DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 - CCS= CCD= CCO=ADDB + CCS= CCD= CCO=ADDB EFER= FCW=037f FSW= [ST=0] FTW=00 MXCSR=1f80 FPR0= FPR1= FPR2= FPR3= FPR4= FPR5= FPR6= FPR7= XMM00= XMM01= XMM02= XMM03= XMM04= XMM05= XMM06= XMM07= Annullato (core dump creato) + Keep a good work - Keep a good work + My machine host + G5 Quad , radeon hd 6570 2gb , 8gb ram ... + host OS Lubuntu 14.04.2 ** Description changed: this appened to me with last 2.3.0 rc 2 + qemu-system-x86-64 crash , with only 2047 or 1024 -m option and -hda set qemu: fatal: Trying to execute code outside RAM or ROM at 0x00181f9a000a EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=0009fff3 EFL=0046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 CCS= CCD= CCO=ADDB EFER= FCW=037f FSW= [ST=0] FTW=00 MXCSR=1f80 FPR0= FPR1= FPR2= FPR3= FPR4= FPR5= FPR6= FPR7= XMM00= XMM01= XMM02=
[Qemu-devel] [Bug 1399957] Re: Strange colors on PowerMac Machine OsX
I will check on my Macbook x86 if needed ... i will first investigating why std mode on ppc have this issue with 32bit video modes on 16bit look like it is ok. wmare have this isssue too. Not the cyrrus there everything is ok. will ask some other guys to make test of qemu on other powermac machines and on linuxppc too. About a patch ..not simple for my knowledge of coding but who know will see if some coders friend can help about. In other way qemu on G5 is fast and usable . -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1399957 Title: Strange colors on PowerMac Machine OsX Status in QEMU: New Bug description: Strange colors on PowerMac Machine OsX if it used VmWare or Std i have strange color palette as result. I had benn made a grab of screen here http://i1249.photobucket.com/albums/hh511/tlosm/qyellow_zps1d2dfc18.jpg My Machine is a PowerMac G5 Quad with Nvidia 7800Gtx 512mb thankyou Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1399957/+subscriptions
[Qemu-devel] [Bug 1399957] Re: Strange colors on PowerMac Machine OsX
PMM i found the problem it is because big endian sdl and was fixed in some
other programams with this
like i write before on 8 bit std no problem when i swap to 16 bit and up i
have wrong colors.
/* The MacOS X port of SDL lies about it's default pixel format
* for high-colour display. It's always R5G5B5. */
Here a code example :
#ifdef WORDS_BIGENDIAN
if (fmt-BitsPerPixel == 24) {
if (fmt-Rmask == 0x00FF fmt-Gmask == 0xFF00 fmt-Bmask
== 0x00FF)
return RGBFB_R8G8B8;
if (fmt-Rmask == 0x00FF fmt-Gmask == 0xFF00 fmt-Bmask
== 0x00FF)
return RGBFB_B8G8R8;
} else if (fmt-BitsPerPixel == 32) {
if (fmt-Rmask == 0xFF00 fmt-Gmask == 0x00FF fmt-Bmask
== 0xFF00)
return RGBFB_R8G8B8A8;
if (fmt-Rmask == 0x00FF fmt-Gmask == 0xFF00 fmt-Bmask
== 0x00FF)
return RGBFB_A8R8G8B8;
if (fmt-Bmask == 0x00FF fmt-Gmask == 0xFF00 fmt-Rmask
== 0x00FF)
return RGBFB_A8B8G8R8;
if (fmt-Bmask == 0xFF00 fmt-Gmask == 0x00FF fmt-Rmask
== 0xFF00)
return RGBFB_B8G8R8A8;
} else if (fmt-BitsPerPixel == 16) {
if (get_sdlgfx_type () == SDLGFX_DRIVER_QUARTZ) {
/* The MacOS X port of SDL lies about it's default pixel format
* for high-colour display. It's always R5G5B5. */
return RGBFB_R5G5B5;
} else {
if (fmt-Rmask == 0xf800 fmt-Gmask == 0x07e0 fmt-Bmask ==
0x001f)
return RGBFB_R5G6B5;
if (fmt-Rmask == 0x7C00 fmt-Gmask == 0x03e0 fmt-Bmask ==
0x001f)
return RGBFB_R5G5B5;
}
} else if (fmt-BitsPerPixel == 15) {
if (fmt-Rmask == 0x7C00 fmt-Gmask == 0x03e0 fmt-Bmask ==
0x001f)
return RGBFB_R5G5B5;
}
#else
if (fmt-BitsPerPixel == 24) {
if (fmt-Rmask == 0x00FF fmt-Gmask == 0xFF00 fmt-Bmask
== 0x00FF)
return RGBFB_B8G8R8;
if (fmt-Rmask == 0x00FF fmt-Gmask == 0xFF00 fmt-Bmask
== 0x00FF)
return RGBFB_R8G8B8;
} else if (fmt-BitsPerPixel == 32) {
if (fmt-Rmask == 0xFF00 fmt-Gmask == 0x00FF fmt-Bmask
== 0xFF00)
return RGBFB_A8B8G8R8;
if (fmt-Rmask == 0x00FF fmt-Gmask == 0xFF00 fmt-Bmask
== 0x00FF)
return RGBFB_B8G8R8A8;
if (fmt-Bmask == 0x00FF fmt-Gmask == 0xFF00 fmt-Rmask
== 0x00FF)
return RGBFB_R8G8B8A8;
if (fmt-Bmask == 0xFF00 fmt-Gmask == 0x00FF fmt-Rmask
== 0xFF00)
return RGBFB_A8R8G8B8;
} else if (fmt-BitsPerPixel == 16) {
if (fmt-Rmask == 0xf800 fmt-Gmask == 0x07e0 fmt-Bmask ==
0x001f)
return RGBFB_R5G6B5PC;
if (fmt-Rmask == 0x7C00 fmt-Gmask == 0x03e0 fmt-Bmask ==
0x001f)
return RGBFB_R5G5B5PC;
} else if (fmt-BitsPerPixel == 15) {
if (fmt-Rmask == 0x7C00 fmt-Gmask == 0x03e0 fmt-Bmask ==
0x001f)
return RGBFB_R5G5B5PC;
}
#endif
return RGBFB_NONE;
}
#endif
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1399957
Title:
Strange colors on PowerMac Machine OsX
Status in QEMU:
New
Bug description:
Strange colors on PowerMac Machine OsX
if it used VmWare or Std i have strange color palette as result.
I had benn made a grab of screen here
http://i1249.photobucket.com/albums/hh511/tlosm/qyellow_zps1d2dfc18.jpg
My Machine is a PowerMac G5 Quad with Nvidia 7800Gtx 512mb
thankyou
Luigi
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1399957/+subscriptions
[Qemu-devel] [Bug 1399957] Re: Strange colors on PowerMac Machine OsX
Peter no problem , if you need the code where i had been found that code ask i can share it without problem. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1399957 Title: Strange colors on PowerMac Machine OsX Status in QEMU: New Bug description: Strange colors on PowerMac Machine OsX if it used VmWare or Std i have strange color palette as result. I had benn made a grab of screen here http://i1249.photobucket.com/albums/hh511/tlosm/qyellow_zps1d2dfc18.jpg My Machine is a PowerMac G5 Quad with Nvidia 7800Gtx 512mb thankyou Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1399957/+subscriptions
[Qemu-devel] [Bug 1399939] Re: Qemu build with -faltivec and maltivec support in
Will check it , i had been made my personal build modding the Makefile with altivec commands in CPPFLAGS. i dont know if it was a placebo effect but look like everything is more faster. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1399939 Title: Qemu build with -faltivec and maltivec support in Status in QEMU: New Bug description: if is possible add the build support for qemu for have the -faltivec -maltivec in CPPFLAGS for make the emulation more faster on PPC equiped machine . Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1399939/+subscriptions
[Qemu-devel] [Bug 1399939] [NEW] Qemu build with -faltivec and maltivec support in
Public bug reported: if is possible add the build support for qemu for have the -faltivec -maltivec in CPPFLAGS for make the emulation more faster on PPC equiped machine . Thank you ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1399939 Title: Qemu build with -faltivec and maltivec support in Status in QEMU: New Bug description: if is possible add the build support for qemu for have the -faltivec -maltivec in CPPFLAGS for make the emulation more faster on PPC equiped machine . Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1399939/+subscriptions
[Qemu-devel] [Bug 1399957] [NEW] Strange colors on PowerMac Machine OsX
Public bug reported: Strange colors on PowerMac Machine OsX if it used VmWare or Std i have strange color palette as result. I had benn made a grab of screen here http://i1249.photobucket.com/albums/hh511/tlosm/qyellow_zps1d2dfc18.jpg My Machine is a PowerMac G5 Quad with Nvidia 7800Gtx 512mb thankyou Luigi ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1399957 Title: Strange colors on PowerMac Machine OsX Status in QEMU: New Bug description: Strange colors on PowerMac Machine OsX if it used VmWare or Std i have strange color palette as result. I had benn made a grab of screen here http://i1249.photobucket.com/albums/hh511/tlosm/qyellow_zps1d2dfc18.jpg My Machine is a PowerMac G5 Quad with Nvidia 7800Gtx 512mb thankyou Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1399957/+subscriptions
