RE: [Qemu-devel] Linux 2.6.15 hangs with QEMU 0.8.0

2006-06-02 Thread Marius Groeger

On Thu, 1 Jun 2006, Sylvain Petreolle wrote:


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


Tried that, and succeeded.

Turned out that Thiemo's patch labeled "[Qemu-devel] [PATCH 3/8] Mips 
improvements" did not just clean up the code as its description said, 
but removed a call to do_raise_exception(EXCP_EXT_INTERRUPT); That 
made my Linux boot, finally,


Sorry for the noise.

Thanks,
Marius

--
Marius Groeger <[EMAIL PROTECTED]>
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



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] block device loopback

2006-06-02 Thread NyOS
On Thu, 01 Jun 2006 18:08:56 +0200, s[e]th & h[o]lth  
<[EMAIL PROTECTED]> 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 !


Hi!

how many partitions do you have on that virtual disc image? maybe 1 is  
enough in most cases..

once i've read on a forum the next 'trick':

[EMAIL PROTECTED]:~$ /sbin/fdisk $HOME/image/qemu-win98.img
You must set cylinders.
You can do this from the extra functions menu.

Command (m for help): p

Disk /home/nyos/image/qemu-win98.img: 0 MB, 0 bytes
128 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 8064 * 512 = 4128768 bytes

  Device Boot  Start End  Blocks
Id  System
/home/nyos/image/qemu-win98.img1   *   1 520  
2096608+   c  W95 FAT32 (LBA)

Partition 1 has different physical/logical endings:
 phys=(518, 127, 63) logical=(519, 127, 63)

Command (m for help): q

so, there are 63 sectors/track, one track is 512 bytes long, and the 1st  
partition starts at 1th track

63*512*1=32256

so the following command:
sudo mount $HOME/image/qemu-win98.img $HOME/win98loop -o loop,offset=32256  
-t vfat
will mount the 1st partition in that image into the apropriate directory  
by ignoring the first 32256 bytes of the image leaving only the partition  
in it..


hope it helps


Light thinks it travels faster than anything but it is wrong. No matter  
how fast light travels it finds the darkness has always got there first,  
and is waiting for it. - Terry Pratchett



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] ESP fixed

2006-06-02 Thread Blue Swirl
I got the ESP Set ATN & Stop command working. Linux uses it only for probing 
disk sizes, but of course if that fails, the zero sized disks will not be 
very useful. Now all distro installers I tried detected the disks correctly.


Some distros didn't detect ESP or Lance automatically when using Proll, but 
OpenBIOS didn't have this problem.


_
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


qemu-sparc.patch-57b.bz2
Description: Binary data
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] qemu-i386 segfaults when running wine on a x86 CPU?

2006-06-02 Thread James Supancic
But, I am using a version of wine on Linux compiled for Linux? wine is a Linux program is it not?

I got the segfault when I ran 

qemu-i386 /usr/bin/wine

when I run file /usr/bin/wine I get
/usr/bin/wine: ELF 32-bit LSB executable, Intel 80386, version 1
(SYSV), for GNU/Linux 2.4.1, dynamically linked (uses shared libs),
stripped.

I should be able to run 32-bit ELF executable compiled for Intel 80386 CPUs with qemu-i386, shouldn't I?

Note that, I didn't even try to run a Win32 executable with wine, I
just tried to run "wine", it should have printed its command line
options/help and exited without doing anything strange...

Thank you for your time,
James SupancicOn 5/31/06, Joshua Root <[EMAIL PROTECTED]> wrote:
James Supancic wrote:> When I run> qemu-i386 /usr/bin/wine> I get> qemu: uncaught target signal 11 (Segmentation fault) - exiting>> 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.Qemu's user mode emulation only works for Linux -> Linux at the moment,
i.e. programs compiled for Linux can be run on a Linux host. (The usefulpart is of course that programs compiled for a different CPUarchitecture than the host's can be run.)However, encouraging progress has been made on qemu-darwin-user, which
will do what you want to do. See here:http://wiki.opendarwin.org/index.php/Darwine:qemu-darwin-user- Josh
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel