Hi, Thomas. Yes! Of course I had it working beautifully before, with
only a minor issue executing a small number of XCOFF binaries, that is
why I specified the QEMU version (2.11.2) AIX last worked with in the
title of this bug.
Check it out:
kens@LAPTOP-JN77KAC2$ qemu-system-ppc64 -version
QEMU
I tried removing the H_HOME_NODE_ASSOCIATIVITY H-call from QEMU 4.2.0
and git 5.0.50v5.0.0-997-g9e7f1469b9-dirty, but AIX 7.2 TL4 SP1 still
won't boot for me. The last version of QEMU I got it to boot up
completely in was 2.11.2 (the version I was able to install AIX).
ERROR:/home/kens/tmp/qemu/cp
Public bug reported:
kens@LAPTOP-JN77KAC2$ qemu-system-ppc64 -version
QEMU emulator version 4.2.93 (v5.0.0-rc3-8-g3119154db0-dirty)
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
qemu-system-ppc64 \
-name "IBM AIX - IBM POWER9" \
-M pseries \
-cpu POWER9 \
-smp 8
Hi, you can close this bug.
Ken
Sent from Yahoo Mail on Android
On Tue, Jan 2, 2018 at 11:19 AM, Thomas Huth<1158...@bugs.launchpad.net>
wrote: Triaging old bug tickets... can you still reproduce this issue with the
latest version of QEMU? Or could we close this ticket nowadays?
** Change
Hi, you can close this ticket. I can't remember what I did to get it
working.
Sent from Yahoo Mail on Android
On Thu, Jul 20, 2017 at 8:16 AM, Thomas Huth<1196...@bugs.launchpad.net>
wrote: Triaging old bug tickets ... can you still reproduce this problem with
the latest version of QEMU (c
I confirmed it wasn't my host, I successfully ran a test on the same
host with a 32-bit QEMU build and SLIRP works fine, for 1.6.0-rc3 as
well.
It could be my x86_64-w64-mingw32-gcc compiler version, I tested 4.8 and
4.7, maybe they're too new? Is there a specific gcc version known to
work? I can
Public bug reported:
Version: 1.5.1 and tried latest in Git, compiled for x86_64 Windows 64-bit
Host: Windows 7 64-bit
Guest: FreeBSD 9.1 i386, RHEL 6.4 x86_64, SLES 11.2 x86_64, OpenSUSE 12.3
ppc64, Fedora 18 ppc64
libiconv: 1.14
glib: 2.28.8
gettext: 0.18.1.1
pixman: 0.30.0
Sorry for the confusion, I was impatient for the first bisect run to
complete - this time I figured out how to automate the testing portion
of the git bisect run script so I could walk away and let it run until
full completion.
Here is the result:
acbb090b2400f627a801074c4e3e006c7501bb26 is the f
Result of git bisect:
commit 837d1f978224f7e7b020c71ffb10b291952cc596
Merge: a6fc23e 2b35e93
Author: Blue Swirl
Date: Sat Jan 12 12:46:57 2013 +
Merge branch 's390-reorg' of git://repo.or.cz/qemu/rth
* 's390-reorg' of git://repo.or.cz/qemu/rth: (149 commits)
target-s390:
** Attachment added: "GDB log to match strace log"
https://bugs.launchpad.net/qemu/+bug/1158912/+attachment/3596881/+files/debug-qemu-20130325-1050.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bug
Public bug reported:
(Note: problem is not present in version 1.3.0)
Stacktrace: please see attached gdb log file.
Steps to reproduce:
1. gdb -x debug-qemu.gdb testing/qemu-1.4.0/ppc64-softmmu/qemu-system-
ppc64
Contents of debug-qemu.gdb:
run -L ./testing/qemu-1.4.0/pc-bios -name "[DEBUG] S
This started to work in version 1.2, 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/1034980
Title:
pseries machine: vscsi scsi qemu cd-rom does not work in win32
Status in QEMU:
New
Bug
I'm probably the only person in the world who has this setup (ppc full
emu on win32) but if anyone else out there was following this it was
fixed in qemu.org git and the solution was another __attribute__
((packed)) versus __attribute__ ((gcc_struct, packed)) -mms-bitfield
issue in spapr_pci.c. You
Public bug reported:
On Win32, the cd-rom device is not detected at all in the pseries machine
(SLOF):
qemu-system-ppc64 -M pseries -m 512 -cdrom img.iso
etc.
VSCSI: Looking for disks
Populating /pci@8002001,0
On Linux however, the scsi qemu cd-rom device is detec
The changelog for 1.1.0-1 states "Pseries handles PCI, allowing for
virtio devices with -M pseries" while this bug report here still stands
as an issue I'm having where SLOF detects my virtio-block device but
QEMU does not create a virtio-pci device that the Linux kernel can
recognize. I would at l
you are correct, can we switch the parameter from "--static-libs" to "--
libs --static" ?
diff --git a/configure b/configure
index 2d62d12..b0cedd2 100755
--- a/configure
+++ b/configure
@@ -1548,7 +1548,7 @@ int main( void ) { return SDL_Init (SDL_INIT_VIDEO); }
EOF
sdl_cflags=`$sdlconfig --c
Public bug reported:
In the configure script when a user wants to compile a static QEMU and
enable SDL support (i.e. ./configure --static --enable-sdl):
pkg-config does not have an option "--static-libs". For correct results
(to find the static archive libSDL.a) you need to use sdl-config
--stati
Sorry, I stripped out the "2>/dev/null" when I was debugging and forgot
to add it back in:
diff --git a/configure b/configure
index 2d62d12..3de4c9b 100755
--- a/configure
+++ b/configure
@@ -1548,7 +1548,7 @@ int main( void ) { return SDL_Init (SDL_INIT_VIDEO); }
EOF
sdl_cflags=`$sdlconfig -
This might be easier to read and understand:
GOOD
Populating /pci@0,0
Adapters on
00 (D) : 1af4 1000 virtio [ net ]
00 0800 (D) : 1af4 1001 virtio [ block ]
...
PCI host bridge /pci@0,0 ranges:
IO 0x01008000.
SLIRP is now currently WORKING for win32 in qemu.org git master as of
Apr 13 2012 10:20 Eastern. The last time I checked unsuccessfully with
things still broken was earlier in the week, probably April 9th, I don't
remember exactly, but the fix was definitely committed this week.
Thanks!!!
--
You
>From the latest QEMU from git:
haddr = 17f
hport = 11555
laddr = 502000a
lport = 5632
flags = 1000
ip_slowtimo...
tcp_slowtimo...
if_start...
if_start...
if_start...
if_start...
[ if_start... repeats forever ]
command-line used:
./testing/qemu/i386-softmmu/qemu-system-i386
Confirmed this effects all network communication, such as gdb TCP listen
socket from guest.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/935945
Title:
SLIRP still not working for win32
Status in
Here is a slirp debug log from the latest development version as of
2012-02-19 (last git commit logged 2012-02-15):
tcp_listen...
haddr = 17f
hport = 11555
laddr = 502000a
lport = 5632
flags = 1000
ip_slowtimo...
tcp_slowtimo...
ip_slowtimo...
tcp_slowtimo...
ip_slowtimo...
tcp_slowtimo..
Public bug reported:
SLIRP has not worked since 0.14.1 (broken since the move to gthread/gio
from the glib library which inherited -mms-bitfields on MinGW32 breaking
bit padding on TCP/UDP packets). Patches attempting to reverse effects
of GCC's -mms-bitfields do not seem to fix SLIRP.
Here is an
Hello,
The VERSION file in stable release qemu-1.0.1 has what I believe might be a
typo: "1.0,1" rather than "1.0.1". This is causing a parsing issue for
windres.exe in Win32 which chokes on:
#define CONFIG_FILEVERSION 1,0,1,0,1,0
#define CONFIG_PRODUCTVERSION 1,0,1,0,1,0
when it should b
past 0.14.1) having issues
> with SLIRP on Windows XP host
> To: "Anthony Liguori" , "Jan Kiszka"
>
> Cc: "TeLeMan" , "Kenneth Salerno"
> , qemu-devel@nongnu.org
> Date: Saturday, August 6, 2011, 10:35 AM
> On Sat, Aug 6, 2011 at 1:33 PM
I think one of the ppc memory API changes today broke something:
warning: subregion collision 8000/1000 vs 0/4
Assertion failed: !subregion->parent, file /home/kens/cross-compile/qemu/testing
/qemu/memory.c, line 1083
This application has requested the Runtime to terminate it in an unusual w
--- On Fri, 8/5/11, Jan Kiszka wrote:
> From: Jan Kiszka
> Subject: Re: 0.15.0-rc2 (any version past 0.14.1) having issues with SLIRP on
> Windows XP host
> To: "Blue Swirl" , "Kenneth Salerno"
>
> Cc: qemu-devel@nongnu.org
> Date: Friday, August 5,
Hi,
I'm not sure if any defaults (build or runtime) have changed since 0.14.1, but
I can no longer get the following to work anymore for QEMU versions 0.15.0-rc2
or recent development builds:
-device e1000,netdev=mynet0 -netdev type=user,id=mynet0 ...
Works great in 0.14.1 however.
>From th
--- On Wed, 7/27/11, Stefan Weil wrote:
> From: Stefan Weil
> Subject: Re: [Qemu-devel] [PATCH] MinGW compilation shouldn't include
> -lglib-2.0 etc.
> To: "Kenneth Salerno"
> Cc: qemu-devel@nongnu.org
> Date: Wednesday, July 27, 2011, 5:13 PM
> Am 27.07.2
--- On Wed, 7/27/11, Daniel P. Berrange wrote:
> From: Daniel P. Berrange
> Subject: Re: [Qemu-devel] [PATCH] MinGW compilation shouldn't include
> -lglib-2.0 etc.
> To: "Kenneth Salerno"
> Cc: qemu-devel@nongnu.org
> Date: Wednesday, July 27, 2011, 11:56 A
Should check first if using a mingw compiler before forcing the addition of
-lglib-2.0, -liconv, and -lintl to $LIBS of config-target.mak.
Signed-off-by: Kenneth Salerno
--- configure.ORIG 2011-07-27 11:28:16.859375000 -0400
+++ configure 2011-07-27 11:43:59.859375000 -0400
@@ -1824,9
--- On Tue, 7/26/11, Kenneth Salerno wrote:
> From: Kenneth Salerno
> Subject: Re: [Qemu-devel] [PATCH v5 01/18] Add hard build dependency on glib
> To: qemu-devel@nongnu.org
> Date: Tuesday, July 26, 2011, 10:02 AM
> From: Michael
> Roth
> Subject: [Qemu-devel] [
From: Michael Roth
Subject:[Qemu-devel] [PATCH v5 01/18] Add hard build dependency on glib
Date: Tue, 5 Jul 2011 08:02:28 -0500
> From: Anthony Liguori
>
> GLib is an extremely common library that has a portable thread implementation
> along with tons of other goodies.
>
> GLib and GO
--- On Sun, 4/3/11, Kenneth Salerno wrote:
> From: Kenneth Salerno
> Subject: Re: [Qemu-devel] Help Debugging AIX boot on qemu-system-ppc (it
> reads bootfile.exe now)
> To: "malc"
> Cc: qemu-devel@nongnu.org
> Date: Sunday, April 3, 2011, 6:52 PM
> ---
--- On Sun, 4/3/11, Kenneth Salerno wrote:
> From: Kenneth Salerno
> Subject: Re: [Qemu-devel] Help Debugging AIX boot on qemu-system-ppc (it
> reads bootfile.exe now)
> To: "malc"
> Cc: qemu-devel@nongnu.org
> Date: Sunday, April 3, 2011, 11:29 AM
> --
--- On Sun, 4/3/11, malc wrote:
> From: malc
> Subject: Re: [Qemu-devel] Help Debugging AIX boot on qemu-system-ppc (it
> reads bootfile.exe now)
> To: "Kenneth Salerno"
> Cc: qemu-devel@nongnu.org
> Date: Sunday, April 3, 2011, 12:13 AM
> On Sat, 2 Ap
Hi,
I have been using QEMU for a few years and periodically tested AIX V6.1 with
qemu-system-ppc and read the various threads in the mailing list knowing not to
expect it to work just yet. However, with OpenBIOS v1.0 I was surprised to find
how far it gets now. Please see below and I would appr
38 matches
Mail list logo
