James Supancic | 1 Jun 03:00 2006
Picon

qemu-i386 segfaults when running wine on a x86 CPU?

When I run
qemu-i386 /usr/bin/wine
I get
qemu: uncaught target signal 11 (Segmentation fault) - exiting

I am using the wine version I compiled and installed for my x86 host, not the one from the qemu website. Do I have to compile my wine version with some special options to use it with qemu-i386 or set some special configuration settings?

I know I don't need qemu-i386 to run wine compiled for x86 CPUs on an x86 CPU. I am trying to figure out how to make a version of wine that will work with qemu-i386, after I figure this out I intend to move the wine installation over to a sparc CPU.

Thank you for your time,
James Supancic
_______________________________________________
Qemu-devel mailing list
Qemu-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Tieu Ma Dau | 1 Jun 16:49 2006
Picon

Qemu on Windows to simulate ARM processor?

Hi all,
I've compiled qemu 8.0 using msys 1.0.11 + MinGW 5.0.0 + zlib + SDL 1.2.8 and when executing qemu (on msys console and also on Windows console) without graphic (option "-nographic"), I've got the error: "qemu: could not open device monitor 'stdio'". But when I use graphic, the new window is opened but nothing is displayed on this window!
Furthermore, I've also tried QemuManager 2.2 and I've got the same result. And when installing Qemu 0.7 for Windows (binary file .exe, not compiled from source!), I can not find the file qemu-system-arm which is normally used to simulate the processor ARM
So I don't know the problem arrives because Qemu can not simulate ARM when running on Windows or because I've took the mistakes?
Thank you so much for your replies
Thanh-Tung

Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.
_______________________________________________
Qemu-devel mailing list
Qemu-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Paul Brook | 1 Jun 16:53 2006

Re: Qemu on Windows to simulate ARM processor?

On Thursday 01 June 2006 15:49, Tieu Ma Dau wrote:
> Hi all,
>   I've compiled qemu 8.0

qemu 0.8.0 is old, and doesn't implement the ARM LCD controller, so I wouldn't 
expect to see any output.

Paul
Marius Groeger | 1 Jun 17:35 2006

Linux 2.6.15 hangs with QEMU 0.8.0

Hi,

with my qemu-0.8.0 I noticed that Linux 2.6.15 runs only with the 
appended patch. Apparently a few nops are missing to get the irq 
enable/disable work properly. Without having looked too deeply into 
the issue -- is this a known issue and I can save my time or is more 
investigation required?

Thiemo, is any of your recently posted patches addressing this issue 
in any way?

Thanks,
Marius

--

-- 
Marius Groeger <mgroeger <at> sysgo.com>
SYSGO AG                      Embedded and Real-Time Software
Voice: +49 6136 9948 0                  FAX: +49 6136 9948 10
www.sysgo.com | www.elinos.com | www.osek.de | www.pikeos.com
s[e]th & h[o]lth | 1 Jun 18:08 2006
Picon

block device loopback

Hello,

I'm a qemu user and I'm looking for a way to use my virtual target drive inside my host computer.
I've created a file that I'll call hda.disk like this : "dd if=/dev/zer of=hda.disk count=1 bs=1M seek=1023" and i use it like "qemu -hda hda.disk "
The problem i meet is that i can't use this file outside the virtual machine and I'm trying to program a block device driver to read this file as a IDE drive.
The aim of this driver is quite similar to the loop driver but instead of "emulating" a partition, it emulates a IDE Hard Drive and give an access to it via /dev/vdX and it's partition via /dev/vdXpY.
Perhaps you will wonder why i use the qemu's mailing-list for this problem :
- i don't know exactly where i can find a way to achieve this project ;
- i wonder how you read your hda.disk without using qemu ;
- i would like to know how qemu fix the virtual drive property inside the virtual machine (cylinders, sectors, etc...) ;
- i don't know anyone interested by this problem and quite good enough linux driver developer to help me.

Thank you very much and have a nice day !
_______________________________________________
Qemu-devel mailing list
Qemu-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Johannes Schindelin | 1 Jun 18:17 2006
Picon
Picon

Re: Linux 2.6.15 hangs with QEMU 0.8.0

Hi,

On Thu, 1 Jun 2006, Marius Groeger wrote:

> with my qemu-0.8.0 I noticed that Linux 2.6.15 runs only with the appended
> patch.

Which patch?

Ciao,
Dscho
Paul Brook | 1 Jun 18:31 2006

Re: block device loopback

> The aim of this driver is quite similar to the loop driver but instead of
> "emulating" a partition, it emulates a IDE Hard Drive and give an access to
> it via /dev/vdX and it's partition via /dev/vdXpY.
> Perhaps you will wonder why i use the qemu's mailing-list for this problem
> : - i don't know exactly where i can find a way to achieve this project ; -
> i wonder how you read your hda.disk without using qemu ;

I'd be surprised if this problem wasn't already fixed by the kernel 
device-mapper infrastructure.

I also think this list is the wrong place to discuss this. There's nothing 
qemu specific about it.

> - i would like to know how qemu fix the virtual drive property inside the
> virtual machine (cylinders, sectors, etc...) ;

qemu doesn't know or care about the contents of the image. It's entirely up to 
the guest OS.

Paul
Jim C. Brown | 1 Jun 18:50 2006
Picon

Re: block device loopback

I'm working on something that does just this. I'm calling it vda (its based
on lomount), and it provides access to vda, vda1, vda2, etc.

I don't see why you are unable to use the disk image as is though. lomount and
similar tools should be able to handle the job quite easily.

On Thu, Jun 01, 2006 at 06:08:56PM +0200, s[e]th & h[o]lth wrote:
> Hello,
> 
> I'm a qemu user and I'm looking for a way to use my virtual target drive
> inside my host computer.
> I've created a file that I'll call hda.disk like this : "dd if=/dev/zer of=
> hda.disk count=1 bs=1M seek=1023" and i use it like "qemu -hda hda.disk"
> The problem i meet is that i can't use this file outside the virtual machine
> and I'm trying to program a block device driver to read this file as a IDE
> drive.
> The aim of this driver is quite similar to the loop driver but instead of
> "emulating" a partition, it emulates a IDE Hard Drive and give an access to
> it via /dev/vdX and it's partition via /dev/vdXpY.
> Perhaps you will wonder why i use the qemu's mailing-list for this problem :
> - i don't know exactly where i can find a way to achieve this project ;
> - i wonder how you read your hda.disk without using qemu ;
> - i would like to know how qemu fix the virtual drive property inside the
> virtual machine (cylinders, sectors, etc...) ;
> - i don't know anyone interested by this problem and quite good enough linux
> driver developer to help me.
> 
> Thank you very much and have a nice day !

> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel <at> nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

--

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
Sylvain Petreolle | 1 Jun 19:01 2006
Picon

RE: Linux 2.6.15 hangs with QEMU 0.8.0

Hi Marius,
better update and try again with qemu 0.8.1 ?

--- Marius Groeger <mgroeger <at> sysgo.com> a écrit :

> Hi,
> 
> with my qemu-0.8.0 I noticed that Linux 2.6.15 runs only with the 

Kind regards,
Sylvain Petreolle (aka Usurp)
--- --- --- --- --- --- --- --- --- --- --- --- ---
Listen to free Music: http://www.jamendo.com
Windows is proprietary, use free ReactOS instead : http://www.reactos.org
Marius Groeger | 1 Jun 21:12 2006

Re: Linux 2.6.15 hangs with QEMU 0.8.0

On Thu, 1 Jun 2006, Johannes Schindelin wrote:

>> with my qemu-0.8.0 I noticed that Linux 2.6.15 runs only with the appended
>> patch.
>
> Which patch?

Brilliant me. Sorry, I forgot the patch. I don't have it handy here at 
home, but it's easily described: in <asm-mips/hazards.h>, it made 
irq_enable_hazard emit 3 NOPs just as irq_disable_hazard. I stumbeled 
over this as my kernel hung im sched.c:wait_for_completionn(). Turned 
out that schedule() wasn't called properly which went away with the 
NOPs.

Again, I didn't really investigate too much, but I reckoned if the 
NOPS are needed upon irq_disable_hazard, they're needed for 
irq_enable_hazard as well, since CP0 status is write modified in both 
situations.

--

-- 
Marius Groeger <mgroeger <at> sysgo.com>
SYSGO AG                      Embedded and Real-Time Software
Voice: +49 6136 9948 0                  FAX: +49 6136 9948 10
www.sysgo.com | www.elinos.com | www.osek.de | www.pikeos.com

Gmane