[Qemu-devel] Cirrus VGA

[Qemu-devel] Cirrus VGA

[Fabrice Bellard]

Hi,

The initial version of the Cirrus VGA support is now commited. It is 
currently not enabled as they are some pending issues to solve. gcc 3.x 
is required to compile it as I use the anonymous structure extension of 
gcc to ease the merge.

During the merge, I modified the VGA emulation so that it is easier to 
add new VGA compatible cards.

Fabrice.

Re: [Qemu-devel] Cirrus VGA

[Karel Gardas]

Fabrice,

just one question: which chip exactly does it emulate? i.e. I still have
crashing issues with Solaris9 X11 on top of emulated VGA, so I would like
to use something better...

Thanks a lot,

Karel

On Sat, 5 Jun 2004, Fabrice Bellard wrote:

> Hi,
>
> The initial version of the Cirrus VGA support is now commited. It is
> currently not enabled as they are some pending issues to solve. gcc 3.x
> is required to compile it as I use the anonymous structure extension of
> gcc to ease the merge.
>
> During the merge, I modified the VGA emulation so that it is easier to
> add new VGA compatible cards.
>
> Fabrice.
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>

--
Karel Gardas                  kgardas@objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com

[Qemu-devel] WINE with QEMU on non-86x processor?

[Sander Nagtegaal]

Did anybody succeed in running WINE with QEMU on a PPC or other non 86x 
proccesor? I'd like to run QEMU in user mode and then start up WINE but so 
far I have no idea how to do it.......
Any tips?

Re: [Qemu-devel] WINE with QEMU on non-86x processor?

[John R. Hogerhuis]

Don't know how PPC would be different, but you didn't say whether you
saw this...

http://fabrice.bellard.free.fr/qemu/qemu-doc.html#SEC31

On Sat, 2004-06-05 at 05:55, Sander Nagtegaal wrote:
> Did anybody succeed in running WINE with QEMU on a PPC or other non 86x 
> proccesor? I'd like to run QEMU in user mode and then start up WINE but so 
> far I have no idea how to do it.......
> Any tips?
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 
> 

Re: [Qemu-devel] WINE with QEMU on non-86x processor?

[Sander Nagtegaal]

Yes , I read it...............about 6 times over and over..........
On non x86 CPUs, you need first to download at least an x86 glibc 
(`qemu-runtime-i386-XXX-.tar.gz' on the QEMU web page). Ensure that 
LD_LIBRARY_PATH is not set: 
unset LD_LIBRARY_PATH 

 Then you can launch the precompiled `ls' x86 executable: 

x86 glibc? I have really no idea how to pull this off. Is somebody able to 
make a bit noob friendly manual of this? I'm not exactly a qeeky but not very 
stupid either but have no idea how to do this. I can't find a x86 glibc and 
have no idea what to do with it.
I compiled QEMU and running windows 98 and that works. But I want to run WINE 
with QEMU in user mode since that gives more speed......

Op zaterdag 5 juni 2004 20:50, schreef John R. Hogerhuis:
> Don't know how PPC would be different, but you didn't say whether you
> saw this...
>
> http://fabrice.bellard.free.fr/qemu/qemu-doc.html#SEC31
>
> On Sat, 2004-06-05 at 05:55, Sander Nagtegaal wrote:
> > Did anybody succeed in running WINE with QEMU on a PPC or other non 86x
> > proccesor? I'd like to run QEMU in user mode and then start up WINE but
> > so far I have no idea how to do it.......
> > Any tips?
> >
> >
> > _______________________________________________
> > Qemu-devel mailing list
> > Qemu-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] WINE with QEMU on non-86x processor?

[John R. Hogerhuis]

Well I don't have a PPC but maybe if you say where you are getting stuck
that would help.

Given that Fabrice has already put together that zip file on the front
page of the qemu web site which has the supporting binaries you need, as
well as a known working WINE, I'm not sure what else you need...

The more info you give as to what you have tried the more likely someone
here will have a solution for you. Once you get the problem solved the
hard way then you can write the good HOWTO on it, which could go on the
web site.

-- John.

On Sat, 2004-06-05 at 12:09, Sander Nagtegaal wrote:
> Yes , I read it...............about 6 times over and over..........
> On non x86 CPUs, you need first to download at least an x86 glibc 
> (`qemu-runtime-i386-XXX-.tar.gz' on the QEMU web page). Ensure that 
> LD_LIBRARY_PATH is not set: 
> unset LD_LIBRARY_PATH 
> 
>  Then you can launch the precompiled `ls' x86 executable: 
> 
> x86 glibc? I have really no idea how to pull this off. Is somebody able to 
> make a bit noob friendly manual of this? I'm not exactly a qeeky but not very 
> stupid either but have no idea how to do this. I can't find a x86 glibc and 
> have no idea what to do with it.
> I compiled QEMU and running windows 98 and that works. But I want to run WINE 
> with QEMU in user mode since that gives more speed......
> 
> Op zaterdag 5 juni 2004 20:50, schreef John R. Hogerhuis:
> > Don't know how PPC would be different, but you didn't say whether you
> > saw this...
> >
> > http://fabrice.bellard.free.fr/qemu/qemu-doc.html#SEC31
> >
> > On Sat, 2004-06-05 at 05:55, Sander Nagtegaal wrote:
> > > Did anybody succeed in running WINE with QEMU on a PPC or other non 86x
> > > proccesor? I'd like to run QEMU in user mode and then start up WINE but
> > > so far I have no idea how to do it.......
> > > Any tips?
> > >
> > >
> > > _______________________________________________
> > > Qemu-devel mailing list
> > > Qemu-devel@nongnu.org
> > > http://lists.nongnu.org/mailman/listinfo/qemu-devel
> >
> > _______________________________________________
> > Qemu-devel mailing list
> > Qemu-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 
> 
> 

Re: [Qemu-devel] WINE with QEMU on non-86x processor?

[Sander Nagtegaal]

Also one thing. According to the manual I should be able to launch "ls" but I 
get a BIOS kernel panic.
With "qemu ls" it gave the panic. With qemu-i386 I got "error loading ls" wich 
means that probably QEMU isn't really installed correctly....... 

Op zondag 6 juni 2004 13:58, schreef u:
> Just been playing around a bit again. It seems that the manual is indeed
> wrong. Most of the pathnames are incorrect. After some time I got those
> damn pathnames correct but now when I execute WINE I get "could not exec
> wineserver".
> I think the pathnames are now correct although I'm not sure.
> Also the site says"
>
> # Configure Wine on your account. Look at the provided script
> `/usr/local/qemu-i386/bin/wine-conf.sh'. Your previous ${HOME}/.wine
> directory is saved to ${HOME}/.wine.org.
>
> I can't execute the script. How to configure WINE? I think that's why he
> can't execute wineserver.
> Thnx in advance.......
>
> Op zondag 6 juni 2004 02:52, schreef u:
> > Ah, it looks like the doco needs update.
> >
> > This is on the main page. I think this is what you need:
> >
> > http://fabrice.bellard.free.fr/qemu/qemu-gnemul-0.5.1.tar.gz
> >
> > I guess you need the x86 libraries out of this...
> >
> > And there's a vintage of WINE there too:
> >
> > http://fabrice.bellard.free.fr/qemu/wine-20020411.tar.gz
> >
> >
> > -- John.
> >
> > On Sat, 2004-06-05 at 13:49, Sander Nagtegaal wrote:
> > > But that's the things.............I can't find the zip file anywhere.
> > > The manual says it's there but it's not............that's my problem.
> > > If I'd had the file it would be piece of cake just follow the
> > > instructions........... Sorry if I wasn't clear........
> > >
> > > Op zaterdag 5 juni 2004 22:32, schreef u:
> > > > Well I don't have a PPC but maybe if you say where you are getting
> > > > stuck that would help.
> > > >
> > > > Given that Fabrice has already put together that zip file on the
> > > > front page of the qemu web site which has the supporting binaries you
> > > > need, as well as a known working WINE, I'm not sure what else you
> > > > need...
> > > >
> > > > The more info you give as to what you have tried the more likely
> > > > someone here will have a solution for you. Once you get the problem
> > > > solved the hard way then you can write the good HOWTO on it, which
> > > > could go on the web site.
> > > >
> > > > -- John.
> > > >
> > > > On Sat, 2004-06-05 at 12:09, Sander Nagtegaal wrote:
> > > > > Yes , I read it...............about 6 times over and over..........
> > > > > On non x86 CPUs, you need first to download at least an x86 glibc
> > > > > (`qemu-runtime-i386-XXX-.tar.gz' on the QEMU web page). Ensure that
> > > > > LD_LIBRARY_PATH is not set:
> > > > > unset LD_LIBRARY_PATH
> > > > >
> > > > >  Then you can launch the precompiled `ls' x86 executable:
> > > > >
> > > > > x86 glibc? I have really no idea how to pull this off. Is somebody
> > > > > able to make a bit noob friendly manual of this? I'm not exactly a
> > > > > qeeky but not very stupid either but have no idea how to do this. I
> > > > > can't find a x86 glibc and have no idea what to do with it.
> > > > > I compiled QEMU and running windows 98 and that works. But I want
> > > > > to run WINE with QEMU in user mode since that gives more
> > > > > speed......
> > > > >
> > > > > Op zaterdag 5 juni 2004 20:50, schreef John R. Hogerhuis:
> > > > > > Don't know how PPC would be different, but you didn't say whether
> > > > > > you saw this...
> > > > > >
> > > > > > http://fabrice.bellard.free.fr/qemu/qemu-doc.html#SEC31
> > > > > >
> > > > > > On Sat, 2004-06-05 at 05:55, Sander Nagtegaal wrote:
> > > > > > > Did anybody succeed in running WINE with QEMU on a PPC or other
> > > > > > > non 86x proccesor? I'd like to run QEMU in user mode and then
> > > > > > > start up WINE but so far I have no idea how to do it.......
> > > > > > > Any tips?
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Qemu-devel mailing list
> > > > > > > Qemu-devel@nongnu.org
> > > > > > > http://lists.nongnu.org/mailman/listinfo/qemu-devel
> > > > > >
> > > > > > _______________________________________________
> > > > > > Qemu-devel mailing list
> > > > > > Qemu-devel@nongnu.org
> > > > > > http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] WINE with QEMU on non-86x processor?

[John R. Hogerhuis]

The first thing you need to accomplish is get x86  ls to work. WINE is
really complex, so at best it should be the second thing you run.

QEMU doesn't require much in the way of installation. I'd guess it is
more likely that your x86 libraries are not being found.

Did you try these instructions from the web page?


        On non x86 CPUs, you need first to download at least an x86
        glibc (`qemu-runtime-i386-XXX-.tar.gz' [FILENAME IS DIFFERENT]
        on the QEMU web page). Ensure that LD_LIBRARY_PATH is not set: 
        unset LD_LIBRARY_PATH 
        
         Then you can launch the precompiled `ls' x86 executable: 
        qemu-i386 tests/i386/ls

Now the previous command shows a -L /   option for X86 which is how you
tell QEMU where to look for libraries. You probably should unset the
library path as above, and when you invoke QEMU give an -L command but
with the path to your x86 libraries. I'm not sure why this is not shown
in the documentation, I could be wrong or it could be an oversight.

Someone experienced with qemu AND has a PPC (or actually any non x86
arch), please help Sander out by trying this... and then post to the
list exactly what you did so that the doco can be updated.

-- John.

Re: [Qemu-devel] WINE with QEMU on non-86x processor?

[Sander Nagtegaal]

Too bad........WINE still says couldn't exec WINE server. But that's normal 
since I didn't configure it yet. Don't know what to do with this text
"> # Configure Wine on your account. Look at the provided script
> `/usr/local/qemu-i386/bin/wine-conf.sh'. Your previous ${HOME}/.wine
> directory is saved to ${HOME}/.wine.org."

How to configure WINE? I'm almost there......my QEMU works with the ls 
file....pretty damn cool.......

Op zondag 6 juni 2004 18:57, schreef u:
> The first thing you need to accomplish is get x86  ls to work. WINE is
> really complex, so at best it should be the second thing you run.
>
> QEMU doesn't require much in the way of installation. I'd guess it is
> more likely that your x86 libraries are not being found.
>
> Did you try these instructions from the web page?
>
>
>         On non x86 CPUs, you need first to download at least an x86
>         glibc (`qemu-runtime-i386-XXX-.tar.gz' [FILENAME IS DIFFERENT]
>         on the QEMU web page). Ensure that LD_LIBRARY_PATH is not set:
>         unset LD_LIBRARY_PATH
>
>          Then you can launch the precompiled `ls' x86 executable:
>         qemu-i386 tests/i386/ls
>
> Now the previous command shows a -L /   option for X86 which is how you
> tell QEMU where to look for libraries. You probably should unset the
> library path as above, and when you invoke QEMU give an -L command but
> with the path to your x86 libraries. I'm not sure why this is not shown
> in the documentation, I could be wrong or it could be an oversight.
>
> Someone experienced with qemu AND has a PPC (or actually any non x86
> arch), please help Sander out by trying this... and then post to the
> list exactly what you did so that the doco can be updated.
>
> -- John.

Re: [Qemu-devel] WINE with QEMU on non-86x processor?

[Sander Nagtegaal]

No........I did nothing special.......the unset thing I didn't do.......
I just moved the stuff to the standard directory it should be.
The documentation is not really incomplete but just a bit to vague for a 
stupid noob like me.......
I didn't put the files from the /usr directory that you get when you unpack 
the files in the normal /usr directory. It unpacked a /usr in my home 
directory but didn't think about the fact that I should move it to my normal 
/usr directory. The manual didn't say it and since I'm still learning about 
Linux that didn't cross my mind. After I moved the "local" dir files to my 
normal "local" dir and the "usr" dir files to my normal "usr" dir it worked.
So it's just because I'm too nooby that it didn't work. However it would be 
nice to say in the docu that people should move the unpacked files to their 
normal system locations. That might help alot of "noobs" like me.
Now only I need to figure out how to configure WINE.
Any help what to with the script or what else to do with it?
The script contents are..............

# wine config for qemu
WINE_PATH=/usr/local/wine-i386

export PATH=$PATH:$WINE_PATH/bin

# only create new config if none is present
if [ '!' -d $HOME/.wine ] ; then
    mkdir $HOME/.wine
    cp $WINE_PATH/etc/* $HOME/.wine
fi

# only create wine c: drive if none exists
if [ '!' -d $HOME/wine ] ; then
    cp -r $WINE_PATH/wine $HOME
fi

if [ '!' -d "$HOME/wine/Program Files/qemu" ] ; then
    cp -r "$WINE_PATH/wine/Program Files/qemu" "$HOME/wine/Program Files"
fi


Thnx!

Op zondag 6 juni 2004 19:28, schreef u:
> Hi Sander,
>
> While it is still fresh in your mind, please post to the list what gaps
> you had to fill in the documentation so that it can be fixed. I suppose
> you had to do the unset. What was the command line you finally used? Did
> you need to put the -L option with a path?
>
> Thanks
>
> -- John.
>
> On Sun, 2004-06-06 at 10:10, Sander Nagtegaal wrote:
> > THNX MAN! I did it..........(well with a bit of help ;-))
> > My ls x86 file now works. Gonna try WINE..........i'll keep you informed.
> > They should really write a new manual................
> >
> > Op zondag 6 juni 2004 18:57, schreef u:
> > > The first thing you need to accomplish is get x86  ls to work. WINE is
> > > really complex, so at best it should be the second thing you run.
> > >
> > > QEMU doesn't require much in the way of installation. I'd guess it is
> > > more likely that your x86 libraries are not being found.
> > >
> > > Did you try these instructions from the web page?
> > >
> > >
> > >         On non x86 CPUs, you need first to download at least an x86
> > >         glibc (`qemu-runtime-i386-XXX-.tar.gz' [FILENAME IS DIFFERENT]
> > >         on the QEMU web page). Ensure that LD_LIBRARY_PATH is not set:
> > >         unset LD_LIBRARY_PATH
> > >
> > >          Then you can launch the precompiled `ls' x86 executable:
> > >         qemu-i386 tests/i386/ls
> > >
> > > Now the previous command shows a -L /   option for X86 which is how you
> > > tell QEMU where to look for libraries. You probably should unset the
> > > library path as above, and when you invoke QEMU give an -L command but
> > > with the path to your x86 libraries. I'm not sure why this is not shown
> > > in the documentation, I could be wrong or it could be an oversight.
> > >
> > > Someone experienced with qemu AND has a PPC (or actually any non x86
> > > arch), please help Sander out by trying this... and then post to the
> > > list exactly what you did so that the doco can be updated.
> > >
> > > -- John.

Re: [Qemu-devel] WINE with QEMU on non-86x processor?

[Sander Nagtegaal]

Also one thing....................the WINE version that is on the QEMU site is 
indeed vintage. Can I run a new version of WINE with QEMU? How should I 
compile it then? Just compile it on my mac and run it with QEMU or should I 
compile it on a windows box or can I get a binary version of WINE ( new one ) 
somewhere?

Op zondag 6 juni 2004 19:37, schreef Sander Nagtegaal:
> No........I did nothing special.......the unset thing I didn't do.......
> I just moved the stuff to the standard directory it should be.
> The documentation is not really incomplete but just a bit to vague for a
> stupid noob like me.......
> I didn't put the files from the /usr directory that you get when you unpack
> the files in the normal /usr directory. It unpacked a /usr in my home
> directory but didn't think about the fact that I should move it to my
> normal /usr directory. The manual didn't say it and since I'm still
> learning about Linux that didn't cross my mind. After I moved the "local"
> dir files to my normal "local" dir and the "usr" dir files to my normal
> "usr" dir it worked. So it's just because I'm too nooby that it didn't
> work. However it would be nice to say in the docu that people should move
> the unpacked files to their normal system locations. That might help alot
> of "noobs" like me.
> Now only I need to figure out how to configure WINE.
> Any help what to with the script or what else to do with it?
> The script contents are..............
>
> # wine config for qemu
> WINE_PATH=/usr/local/wine-i386
>
> export PATH=$PATH:$WINE_PATH/bin
>
> # only create new config if none is present
> if [ '!' -d $HOME/.wine ] ; then
>     mkdir $HOME/.wine
>     cp $WINE_PATH/etc/* $HOME/.wine
> fi
>
> # only create wine c: drive if none exists
> if [ '!' -d $HOME/wine ] ; then
>     cp -r $WINE_PATH/wine $HOME
> fi
>
> if [ '!' -d "$HOME/wine/Program Files/qemu" ] ; then
>     cp -r "$WINE_PATH/wine/Program Files/qemu" "$HOME/wine/Program Files"
> fi
>
>
> Thnx!
>
> Op zondag 6 juni 2004 19:28, schreef u:
> > Hi Sander,
> >
> > While it is still fresh in your mind, please post to the list what gaps
> > you had to fill in the documentation so that it can be fixed. I suppose
> > you had to do the unset. What was the command line you finally used? Did
> > you need to put the -L option with a path?
> >
> > Thanks
> >
> > -- John.
> >
> > On Sun, 2004-06-06 at 10:10, Sander Nagtegaal wrote:
> > > THNX MAN! I did it..........(well with a bit of help ;-))
> > > My ls x86 file now works. Gonna try WINE..........i'll keep you
> > > informed. They should really write a new manual................
> > >
> > > Op zondag 6 juni 2004 18:57, schreef u:
> > > > The first thing you need to accomplish is get x86  ls to work. WINE
> > > > is really complex, so at best it should be the second thing you run.
> > > >
> > > > QEMU doesn't require much in the way of installation. I'd guess it is
> > > > more likely that your x86 libraries are not being found.
> > > >
> > > > Did you try these instructions from the web page?
> > > >
> > > >
> > > >         On non x86 CPUs, you need first to download at least an x86
> > > >         glibc (`qemu-runtime-i386-XXX-.tar.gz' [FILENAME IS
> > > > DIFFERENT] on the QEMU web page). Ensure that LD_LIBRARY_PATH is not
> > > > set: unset LD_LIBRARY_PATH
> > > >
> > > >          Then you can launch the precompiled `ls' x86 executable:
> > > >         qemu-i386 tests/i386/ls
> > > >
> > > > Now the previous command shows a -L /   option for X86 which is how
> > > > you tell QEMU where to look for libraries. You probably should unset
> > > > the library path as above, and when you invoke QEMU give an -L
> > > > command but with the path to your x86 libraries. I'm not sure why
> > > > this is not shown in the documentation, I could be wrong or it could
> > > > be an oversight.
> > > >
> > > > Someone experienced with qemu AND has a PPC (or actually any non x86
> > > > arch), please help Sander out by trying this... and then post to the
> > > > list exactly what you did so that the doco can be updated.
> > > >
> > > > -- John.
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] Cirrus VGA

[Antony T Curtis]

On Sat, 2004-06-05 at 11:41, Fabrice Bellard wrote:
> Hi,
> 
> The initial version of the Cirrus VGA support is now commited. It is 
> currently not enabled as they are some pending issues to solve. gcc 3.x 
> is required to compile it as I use the anonymous structure extension of 
> gcc to ease the merge.
> 
> During the merge, I modified the VGA emulation so that it is easier to 
> add new VGA compatible cards.

I've checked out a copy from cvs ... and have found FreeBSD 5-CURRENT's
gcc doesn't like the anonymous structure use.

Anyways, I compiled it, tweeked pc.c to use the cirrus driver and
downloaded a CL-GD543x bios from http://www.linuks.mine.nu/ree/video/

So far, looks good... FreeBSD happily changes text modes including the
VESA extended text modes. Haven't tested graphics modes yet.

-- 
Antony T Curtis <antony.t.curtis@ntlworld.com>

Re: [Qemu-devel] Cirrus VGA

[Juergen Lock]

In article <1086440144.6650.353.camel@pcgem.rdg.cyberkinetica.com> you write:
>On Sat, 2004-06-05 at 11:41, Fabrice Bellard wrote:
>> Hi,
>> 
>> The initial version of the Cirrus VGA support is now commited. It is 
>> currently not enabled as they are some pending issues to solve. gcc 3.x 
>> is required to compile it as I use the anonymous structure extension of 
>> gcc to ease the merge.
>> 
>> During the merge, I modified the VGA emulation so that it is easier to 
>> add new VGA compatible cards.
>
>I've checked out a copy from cvs ... and have found FreeBSD 5-CURRENT's
>gcc doesn't like the anonymous structure use.
>
gcc (GCC) 3.3.3 (Debian 20040422) also doesnt like it...
Maybe it should be taken out of the default build until FreeBSD
and debian get an updated gcc version?

>Anyways, I compiled it,

 Does the lang/gcc33 port work?  or what compiler did you use?

> tweeked pc.c to use the cirrus driver and
>downloaded a CL-GD543x bios from http://www.linuks.mine.nu/ree/video/
>
>So far, looks good... FreeBSD happily changes text modes including the
>VESA extended text modes. Haven't tested graphics modes yet.
>
 X would be interesting as with the default vga driver it doesnt work...

	Juergen

Re: [Qemu-devel] Cirrus VGA

[Juergen Lock]

In article <1086448947.6650.358.camel@pcgem.rdg.cyberkinetica.com> you write:
>-=-=-=-=-=-
>
>On Sat, 2004-06-05 at 15:16, Juergen Lock wrote:
>
>Maybe good if I actually attach my diff...

 :)
>-- 
>Antony T Curtis <antony.t.curtis@ntlworld.com>
>
>-=-=-=-=-=-
>
>diff -bur ../cvs/qemu/configure qemu/configure
>--- ../cvs/qemu/configure	Sat Jun  5 13:25:07 2004
>+++ qemu/configure	Sat Jun  5 14:33:58 2004
>@@ -418,8 +418,13 @@
> echo "TARGET_DIRS=$target_list" >> $config_mak
> 
> if [ "$bsd" = "yes" ] ; then
>+  echo "#define HAVE_TERMIOS_H" >> $config_h
>+  echo "#define HAVE_SYS_IOCTL_H" >> $config_h
>+  echo "#define HAVE_SYS_FILIO_H" >> $config_h
>   echo "#define O_LARGEFILE 0" >> $config_h
>+  echo "#define off64_t off_t" >> $config_h
>   echo "#define lseek64 lseek" >> $config_h
>+  echo "#define mkstemp64 mkstemp" >> $config_h
>   echo "#define ftruncate64 ftruncate" >> $config_h
>   echo "#define MAP_ANONYMOUS MAP_ANON" >> $config_h
>   echo "#define _BSD 1" >> $config_h

 These are fixed in the port btw.

>...
>diff -bur ../cvs/qemu/vl.c qemu/vl.c
>--- ../cvs/qemu/vl.c	Sat Jun  5 13:25:07 2004
>+++ qemu/vl.c	Sat Jun  5 13:50:36 2004
>...

>@@ -1051,10 +1064,18 @@
> #ifdef _BSD
> static int tun_open(char *ifname, int ifname_size)
> {
>-    int fd;
>+    int fd = -1, i;
>     char *dev;
>     struct stat s;
> 
>+    for (i = 0; fd < 0 && i < 4; i++) {
>+        char vnname[16];
>+        snprintf(vnname,16,"/dev/vmnet%d",i);
>+        fd = open(vnname, O_RDWR);
>+    }
>+
>+
>+    if (fd < 0)
>     fd = open("/dev/tap", O_RDWR);
>     if (fd < 0) {
>         fprintf(stderr, "warning: could not open /dev/tap: no virtual
>network emulation\n");

 Huh?  Is the vmware networking module compatible to if_tap somehow?
And is there a description of its features somewhere?

 Curious,
	Juergen