During several tests with Qemu / Kqemu it seems that Qemu
has problems with x86_64 host systems. My system is an
AMD 64 X2 (Dual Core), running openSUSE 10.2, 2GB memory.
Various versions of Qemu/Kqemu available and under test:
0.8.2, 0.9.0, and CVS. Kqemu 1.3.0pre9, 1.3.0pre11
When building Qemu
Blue Swirl a écrit :
> Hi,
>
> The updated Sparc32 image supports Sparcstation 10 machine. The
> changes that disable interpose operation also make NetBSD CDs
> unbootable, but on the other hand OpenBSD CDs start to show progress:
> Boot loader is loaded, it loads kernel which then panics. SunOS
>
i had build a linux(2.6.16) with arm corss-build.The kernel config is the
def config(arch/arm/ mach-integrator/Kconfig),but when i use this kernel
image to run in pemu,it did not work after the message " done, booting the
kernel."
i found it in function decompress_kernel, and it was called by he
Thanks for the links, Jure.
Now for a bug report:
I am trying to run Webconverger in the qemu VM.
firefox3.iso and MorphixLiveKiosk_0.03.iso worked fine, but
wc-2.4.img, wc-2.4.img, wc-1.8.iso all drop to the busybox prompt, but no
definitive reason why.
[EMAIL PROTECTED]:~/qemu$ qemu -cdrom
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 07/04/16 01:35:30
Modified files:
target-mips: translate.c
Log message:
Simplify branch likely handling.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/target-mips/translate.c?cvsroo
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Paul Brook 07/04/15 23:54:20
Modified files:
hw : acpi.c
Log message:
Remove unused variable.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/acpi.c?cvsroot=qemu&r1=1.9&r2=1.10
On Sun, Apr 15, 2007 at 10:37:08PM +0300, Blue Swirl wrote:
> On 4/15/07, Paul Brook <[EMAIL PROTECTED]> wrote:
> > On Sunday 15 April 2007 20:11, Blue Swirl wrote:
> > > > Probably the linker is making sure the file offset and VMA are the same
> > > > modulo the page size.
> > >
> > > But that wou
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 07/04/15 21:26:37
Modified files:
target-mips: op.c translate.c
Log message:
Don't use T2 for INS, it conflicts with branch delay slot handling.
CVSWeb URLs:
http://cvs.savannah.gnu.org/vie
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 07/04/15 21:21:33
Modified files:
target-mips: exec.h op.c op_helper.c
Log message:
Fix qemu SIGFPE caused by division-by-zero due to underflow.
CVSWeb URLs:
http://cvs.savannah.gnu.org/vie
> But nevertheless, sometimes it happens that I "do that",
> and then I'm always happy when I get a clear error
> message. Or even better, when something works as
> expected even when I did something unexpected.
> You are lucky if you never experienced such situations.
>
> In my case, even a simple
Official OS Support list working again.
No spam (who knows how much time will that be real lol).
A little of rework.
Now details for each tested OS opens in a separate window (it is not the
best way but solves the problems with javascript and comments containing
quotes)
http://www.claunia.com/qemu
Yes but...
Currently no protected mode 286 guest OS runs under qemu.
El dom, 15-04-2007 a las 14:46 +0100, Nigel Horne escribió:
> Let me approach this in a different way in the hope that I'll get an answer
> to my
> question: will Qemu run a 286 guest O/S?
>
> -Nige
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 07/04/15 19:52:12
Modified files:
target-mips: translate.c
Log message:
Small code generation optimization.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/target-mips/translate.c?cvs
On 4/15/07, Paul Brook <[EMAIL PROTECTED]> wrote:
On Sunday 15 April 2007 20:11, Blue Swirl wrote:
> > Probably the linker is making sure the file offset and VMA are the same
> > modulo the page size.
>
> But that would be one huge file, as the VMA is near 2TB:
I said *modulo the pace size* :-)
On Sunday 15 April 2007 20:11, Blue Swirl wrote:
> > Probably the linker is making sure the file offset and VMA are the same
> > modulo the page size.
>
> But that would be one huge file, as the VMA is near 2TB:
I said *modulo the pace size* :-)
Lets say ld thinks the page size for your system is
Probably the linker is making sure the file offset and VMA are the same modulo
the page size.
But that would be one huge file, as the VMA is near 2TB:
pc-bios/openbios-sparc64: file format elf64-sparc
pc-bios/openbios-sparc64
architecture: sparc:v9, flags 0x0102:
EXEC_P, D_PAGED
start a
On Sunday 15 April 2007 16:03, Blue Swirl wrote:
> On 4/15/07, Stefan Weil <[EMAIL PROTECTED]> wrote:
> > The Sparc64 image is much larger than the Sparc32 image,
> > but the size command displays a much smaller text and data size
> > (about the same size as for the Sparc32 image).
> >
> > Maybe it
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 07/04/15 17:27:07
Modified files:
target-mips: op_helper.c
Log message:
Delete unused define.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/target-mips/op_helper.c?cvsroot=qemu&r1=1
Nigel Horne wrote:
> Thiemo Seufer wrote:
> >Nigel Horne wrote:
> >>Folks,
> >>
> >>Thanks for qemu. I thought you may like to know that from a Linux x86 host
> >>I have 3 linux guests: sparc, arm and mips. The first 2 work a treat, the
> >>mips keeps core dumping in libc6 when called from Perl, I
Thanks. Now QEMU/Malta works better than ever :-)
Below is a small change which is needed for your patch.
Regards
Stefan
Aurelien Jarno schrieb:
> Index: hw/mips_malta.c
> ===
> RCS file: /sources/qemu/qemu/hw/mips_malta.c,v
> retrie
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 07/04/15 15:15:10
Modified files:
hw : gt64xxx.c
Log message:
Gallileo fixes, by Stefan Weil.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/gt64xxx.c?cvsroot=qemu&r1=1.7&
On 4/15/07, Stefan Weil <[EMAIL PROTECTED]> wrote:
The Sparc64 image is much larger than the Sparc32 image,
but the size command displays a much smaller text and data size
(about the same size as for the Sparc32 image).
Maybe it contains some unneeded parts?
Thanks for the report. There is ind
Hi Paul,
of course it is always good practice to avoid errors.
But nevertheless, sometimes it happens that I "do that",
and then I'm always happy when I get a clear error
message. Or even better, when something works as
expected even when I did something unexpected.
You are lucky if you never exp
I find it useful occasionally to play with the guests' notion of time,
for example to see if a program copes sanely with daylight savings
time transitions. The following patches allow this, at least on
FreeBSD, which is the only system I tested them on. Share and enjoy.
John
--- qemu-doc.texi.o
On Sun, Apr 15, 2007 at 03:07:38PM +0200, Stefan Weil wrote:
> Hi,
>
> here are some more patches for the GT64120 PCI:
>
> * Fix the device id (byte order was swapped for mips and mipsel).
> Now lspci shows the correct device name (for any endianess).
>
> * Fix the byte order for GT64120 PCI c
QEMU only emulates a serial interface without FIFO,
so Linux gets one interrupt per character sent or received.
And the emulation does not emulate the original speed
of the serial interface, but runs at fastest speed possible.
I get this log message every time when a program writes
more than a few
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Paul Brook 07/04/15 14:13:11
Modified files:
linux-user : flatload.c
Log message:
bFLT loader alignment fix.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/linux-user/flatload.c?cvsroot=qemu&r1=1.
Thiemo Seufer wrote:
Nigel Horne wrote:
Folks,
Thanks for qemu. I thought you may like to know that from a Linux x86 host
I have 3 linux guests: sparc, arm and mips. The first 2 work a treat, the
mips keeps core dumping in libc6 when called from Perl, I don't know if
the problem lies in libc6,
In the mips emulator I often see "serial8250: too much work for irq4",
particularity when running vi etc. Is that to be expected, and known about?
If so, please ignore this ;-), if not, I thought you may like to know.
-Nigel
begin:vcard
fn:Nigel Horne
n:Horne;Nigel
org:NJH Music
email;internet:[E
On Sunday 15 April 2007 14:57, Stefan Weil wrote:
> This small patch for Makefile.target fixes a very special build issue:
>
> make distclean # (only needed to remove files left from earlier builds)
> ./configure
> make -C i386-softmmu # (or any other system emulation)
>
> will try to build the mis
This small patch for Makefile.target fixes a very special build issue:
make distclean # (only needed to remove files left from earlier builds)
./configure
make -C i386-softmmu # (or any other system emulation)
will try to build the missing dyngen and fail because dyngen is
normally build by the r
Paul Brook wrote:
On Sunday 15 April 2007 14:46, Nigel Horne wrote:
Let me approach this in a different way in the hope that I'll get an answer
to my question: will Qemu run a 286 guest O/S?
Yes.
Good.
Followup question, if the guest O/S is multi-architecture, will it run in 386
mode (which
On Sunday 15 April 2007 14:46, Nigel Horne wrote:
> Let me approach this in a different way in the hope that I'll get an answer
> to my question: will Qemu run a 286 guest O/S?
Yes.
Paul
Let me approach this in a different way in the hope that I'll get an answer to
my
question: will Qemu run a 286 guest O/S?
-Nige
begin:vcard
fn:Nigel Horne
n:Horne;Nigel
org:NJH Music
email;internet:[EMAIL PROTECTED]
tel;fax:+44 870 705 9334
note:Skype: nigelhorne
x-mozilla-html:FALSE
version:2.
> > My point is that pretty much anything that runs on a 286 should also run
> > on any subsequent x86 processor. If you want to test 16-bit x86
> > software/systems you don't need an actual 286. A 386 is just as good for
> > almost all purposes.
>
> How does that address my issue?
You wanted a 28
Nigel Horne <[EMAIL PROTECTED]> writes:
> Andreas Schwab wrote:
>> Nigel Horne <[EMAIL PROTECTED]> writes:
>>
>>> I can't remember now what sizeof(int) and sizeof(char *) were on m68k
>>> machines.
>>
>> It depends. Try -mshort.
>
> That's not much help, I'm sorry to say, because you need an m68
Hi,
here are some more patches for the GT64120 PCI:
* Fix the device id (byte order was swapped for mips and mipsel).
Now lspci shows the correct device name (for any endianess).
* Fix the byte order for GT64120 PCI configuration (was swapped
for mips). Now lspci shows the GT64120 device for
Paul Brook wrote:
Modern x86 are backwards compatible[*], so you should be able to do that
anyway.
Care to share with us how I do that? Is it an option to gcc?
gcc does not support 16-bit mode.
My point is that pretty much anything that runs on a 286 should also run on
any subsequent x86 pro
> > Modern x86 are backwards compatible[*], so you should be able to do that
> > anyway.
>
> Care to share with us how I do that? Is it an option to gcc?
gcc does not support 16-bit mode.
My point is that pretty much anything that runs on a 286 should also run on
any subsequent x86 processor. If
Nigel Horne wrote:
> Folks,
>
> Thanks for qemu. I thought you may like to know that from a Linux x86 host
> I have 3 linux guests: sparc, arm and mips. The first 2 work a treat, the
> mips keeps core dumping in libc6 when called from Perl, I don't know if
> the problem lies in libc6, perl or qemu
Andreas Schwab wrote:
Nigel Horne <[EMAIL PROTECTED]> writes:
I can't remember now what sizeof(int) and sizeof(char *) were on m68k machines.
It depends. Try -mshort.
That's not much help, I'm sorry to say, because you need an m68k machine to use
it on, and there's no qemu-system-m68k, onl
Paul Brook wrote:
On Sunday 15 April 2007 13:08, Nigel Horne wrote:
Stuart Brady wrote:
On Sun, Apr 15, 2007 at 11:08:56AM +0100, Nigel Horne wrote:
Can qemu emulate 16-bit machines (286?)?
None that I'm aware of. Is there any particular need for 286 emulation?
To test my code on machines w
The Sparc64 image is much larger than the Sparc32 image,
but the size command displays a much smaller text and data size
(about the same size as for the Sparc32 image).
Maybe it contains some unneeded parts?
Stefan
Blue Swirl schrieb:
> CVSROOT: /cvsroot/qemu
> Module name: qemu
> Changes
Nigel Horne <[EMAIL PROTECTED]> writes:
> I can't remember now what sizeof(int) and sizeof(char *) were on m68k
> machines.
It depends. Try -mshort.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint
On Sunday 15 April 2007 13:08, Nigel Horne wrote:
> Stuart Brady wrote:
> > On Sun, Apr 15, 2007 at 11:08:56AM +0100, Nigel Horne wrote:
> >> Can qemu emulate 16-bit machines (286?)?
> >
> > None that I'm aware of. Is there any particular need for 286 emulation?
>
> To test my code on machines whe
Stuart Brady wrote:
On Sun, Apr 15, 2007 at 11:08:56AM +0100, Nigel Horne wrote:
Can qemu emulate 16-bit machines (286?)?
None that I'm aware of. Is there any particular need for 286 emulation?
To test my code on machines where sizeof(int) == sizeof(short), and
sizeof(int) != sizeof(long).
On Sunday 15 April 2007 12:33, Stuart Brady wrote:
> On Sun, Apr 15, 2007 at 11:08:56AM +0100, Nigel Horne wrote:
> > Can qemu emulate 16-bit machines (286?)?
>
> None that I'm aware of. Is there any particular need for 286 emulation?
> OTOH, it might be interesting to see some m68k system emulati
On Sun, Apr 15, 2007 at 11:08:56AM +0100, Nigel Horne wrote:
> Can qemu emulate 16-bit machines (286?)?
None that I'm aware of. Is there any particular need for 286 emulation?
OTOH, it might be interesting to see some m68k system emulation.
I've been working on an 8-bit machine, with some succes
Folks,
Thanks for qemu. I thought you may like to know that from a Linux x86 host
I have 3 linux guests: sparc, arm and mips. The first 2 work a treat, the
mips keeps core dumping in libc6 when called from Perl, I don't know if
the problem lies in libc6, perl or qemu.
Can qemu emulate 16-bit mac
Hi,
The updated Sparc32 image supports Sparcstation 10 machine. The
changes that disable interpose operation also make NetBSD CDs
unbootable, but on the other hand OpenBSD CDs start to show progress:
Boot loader is loaded, it loads kernel which then panics. SunOS
booting can be tried with this ve
50 matches
Mail list logo
