Re: QEMU on dual core WinXP

> Since version 0.8.2, QEMU includes the processor affinity 
> fix. Did you try with this version ?

No, I branched off at 0.8.0.  Is my assumtion correct that the problem
lies in the way asynchronous events (interrupts) are signaled to the
interpreter loop?

Regards,

Konrad

QEMU Windows port & kqemu

I have a 40 GB hard disk in a USB2 enclosure and I had the idea to set
up some virtual machines along with qemu binaries for various operating
systems (linux, windows, mac os) to have a portable environment for use
on different computers. If possible, I'd like to also have available the
kqemu .sys and .inf installer for Windows 2000/XP. Do the binaries
available at the QEMU Windows page linked to off of the QEMU home page
support kqemu if it is available?
--

-- 
Andrew Barr | http://www.oakcourt.dyndns.org/~andrew/

"Buzzword detected (core dumped)"
  -- seen on linux-kernel <at> vger.kernel.org

Kernel panic while executing "exit" in MIPS Linux target on I32 Linux host

hi,

I am running qemu (latest version from CVS) on my I32 Linux desktop to 
emulate the MIPS arch. While running the mips-test-0.1.tar.gz 
<http://www.qemu.org/mips-test-0.1.tar.gz>, everything works fine except 
executing the "exit" command. I got the following information.

BusyBox v1.01 (Debian 1:1.01-4) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ # help

Built-in commands:
-------------------
        . : break cd chdir command continue eval exec exit export false
        hash help let local pwd read readonly return set shift times
        trap true type ulimit umask unset wait

~ # exit
Kernel panic - not syncing: Attempted to kill init!

Is it a bug or not?

Thanks,
Neo

--

-- 
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!

Re: Re: QEMU on dual core WinXP

Schwarz, Konrad wrote:
>>Since version 0.8.2, QEMU includes the processor affinity 
>>fix. Did you try with this version ?
> 
> 
> No, I branched off at 0.8.0.  Is my assumtion correct that the problem
> lies in the way asynchronous events (interrupts) are signaled to the
> interpreter loop?

Yes, and it is not easy to solve...

Fabrice.

Re: esd audio output patch and debuging.

Leonardo E. Reiter <lreiter <at> win4lin.com> writes:

> 
> malc,
> 
> Other than the lack of error handling and blocking mode, what is the 
> problem with using QEMU's VM clock as the audio clock source?  In my 
> experience from older projects using esd (not related to QEMU), it is 
> almost impossible to get reliable timing from ESD, especially if you are 
> transporting over a network.  The timing will certainly not be accurate 
> enough for example for Windows guests using Windows Media Player, etc. 
> Plus, you have to factor in socket buffering and underruns due to 
> network latency if you expect anything synchronous on the socket.  So 
> what is the reason for objecting to the QEMU vm clock, much like the 
> mute audio driver uses?  I just want to know your reasoning for it just 
> to further my own understanding.

Mute/wav rendering works by the virtue of having one clock source, i.e.
vm clock, furthermore the writes are non-blocking and instantaneous[1].
With esd one has to deal with two clock sources - one is vm clock other
is esds ability to consume the data. If vm clock is a bit lower w.r.t.
the audio clock esd uses - you will always starve the esd and in turn
audio subsystem it uses.

All in all real-time(in a loose sense) audio will only work if your
only constraint is the receivers ability to consume data. Given esds
interface the only safe way to do that is by emulating of a blocking
write, this in trun (given all other things into consideration) means
threads and interaction with QEMUs audio/main loop a'la sdlaudio or
coreaudio.

Re: Kernel panic while executing "exit" in MIPS Linux target on I32 Linux host

Neo schrieb:
> hi,
>
> I am running qemu (latest version from CVS) on my I32 Linux desktop to
> emulate the MIPS arch. While running the mips-test-0.1.tar.gz
> <http://www.qemu.org/mips-test-0.1.tar.gz>, everything works fine
> except executing the "exit" command. I got the following information.
>
> BusyBox v1.01 (Debian 1:1.01-4) Built-in shell (ash)
> Enter 'help' for a list of built-in commands.
>
> ~ # help
>
> Built-in commands:
> -------------------
>        . : break cd chdir command continue eval exec exit export false
>        hash help let local pwd read readonly return set shift times
>        trap true type ulimit umask unset wait
>
> ~ # exit
> Kernel panic - not syncing: Attempted to kill init!
>
> Is it a bug or not?
>
> Thanks,
> Neo
>
No bug. With exit, you terminate the shell (/bin/sh).
In this test, /bin/sh is the init process which normally
never terminates while your OS is running. If it does,

Re: Kernel panic while executing "exit" in MIPS Linux target on I32 Linux host

Stefan Weil wrote:
> Neo schrieb:
>   
>> hi,
>>
>> I am running qemu (latest version from CVS) on my I32 Linux desktop to
>> emulate the MIPS arch. While running the mips-test-0.1.tar.gz
>> <http://www.qemu.org/mips-test-0.1.tar.gz>, everything works fine
>> except executing the "exit" command. I got the following information.
>>
>> BusyBox v1.01 (Debian 1:1.01-4) Built-in shell (ash)
>> Enter 'help' for a list of built-in commands.
>>
>> ~ # help
>>
>> Built-in commands:
>> -------------------
>>        . : break cd chdir command continue eval exec exit export false
>>        hash help let local pwd read readonly return set shift times
>>        trap true type ulimit umask unset wait
>>
>> ~ # exit
>> Kernel panic - not syncing: Attempted to kill init!
>>
>> Is it a bug or not?
>>
>> Thanks,
>> Neo
>>
>>     

Re: Kernel panic while executing "exit" in MIPS Linux target on I32 Linux host

On Saturday, September 2, 2006, 0:01:21, Neo wrote:

> Thank you for your explanation. But why there is no kernel panic when 
> the target host is PC?

Specify init=/bin/sh on the kernel command line, and type exit when you get
the shell - you'll also get a kernel panic.

--

-- 
< Jernej Simonèiè ><><><><>< http://deepthought.ena.si/ >

When you need towns, they are very far apart.
       -- Steinbeck's Law

[PATCH] Additional serial and parallel device

Hello,

well, the subject line is not exactly true: my patch does not
add a new device, but allows to disable a device.

"-serial none" disables the default serial device,
"-parallel none" disables the default parallel device.

It is also possible to skip a device:
"-serial none -serial vc" adds serial 1 without serial 0.

Many new PC platforms do not provide a serial device - now
QEMU can emulate these platforms better 

Regards
Stefan

Index: vl.c
===================================================================
RCS file: /sources/qemu/qemu/vl.c,v
retrieving revision 1.210
diff -u -b -B -r1.210 vl.c
--- vl.c	19 Aug 2006 12:37:52 -0000	1.210
+++ vl.c	1 Sep 2006 15:13:30 -0000
 <at>  <at>  -6844,27 +6844,29  <at>  <at> 
     monitor_init(monitor_hd, !nographic);

     for(i = 0; i < MAX_SERIAL_PORTS; i++) {

OpenSPARC OBP source code available

  This may be useful for the openbios/qemu SPARC64 project.
On the latest release (1.3), SUN has included the source code
for the OpenBios for the Niagara (sunv)

  http://opensparc-t1.sunsource.net/download_hw.html

--
  Testing never proves the absence of faults, it only shows their 
presence.
  - Dijkstra