| |
| |
| |
|
Page: 1 2 3 4
Comments:
<0> bye
<1> i'm just curious, is there any speed diff. between installing win xp as a guest OS on linux using the cd-rom or an iso?
<2> hello
<1> if networking doesn't work in the guest OS (win xp), am i supposed to use tuntap networking?
<3> what isn't working?
<1> nm i'm an idiot
<1> i thought i could ***ign it a static ip on my reg. lan
<1> setting it to dhcp fixed it
<3> it's possible with tun/tap - by default qemu will use user-mode network.
<1> my mouse is a little funky though
<3> more info on that: http://qemu.org/qemu-doc.html#SEC23
<1> thanks
<3> the mouse wall is a pretty annoying bug ;/
<3> should be fixed when 0.8.2 is released
<3> (a fix is in cvs)
<1> i'm too noob to use cvs :-/
<1> is pptp support there?
<3> you'd probably need some client in the guest to get that working.
<3> looks like you'll need port redirection though - see '-redir' option in the doc linked above.
<1> thanks dignome
<1> how do you add a patch in qemu?
<4> j00d: do you have a build environment? (gcc etc)
<1> yeah i added that in the centos install
<4> is that your main OS or the one in qemu?
<1> that's the main os, the guest OS is win xp
<4> ok
<4> normally just go in the qemu source dir
<4> and patch -p1 < /path/to/patch
<1> ok does it matter that i already did ./configure make make install in the source dir?
<4> shouldn't
<4> but you can do make distclean if you want
<1> i got:
<1> (Stripping trailing CRs from patch.)
<1> patching file sdl.c
<1> do i do make install again?
<4> configure first
<1> ok ./configure make make install, right?
<4> yeah
<4> add a make clean to the beginning
<1> thanks, i'm testing out my mouse patch now
<4> oh cool
<4> do you still have the url?
<1> this is the patch i used
<1> http://www.h7.dion.ne.jp/~qemu-win/
<1> qemu-0.8.1-mouse.patch
<1> Fix mouse invisible wall problem by A. Liguori from
<4> nice
<1> so far so good
<1> thanks for your help punk-***
<4> I hadn't looked into it and just ran 0.8.0
<4> no problem
<1> so qemu has its own drivers that are in a layer separate from the hardware?
<1> so i shouldn't do anything like update drivers?
<4> not sure what you mean exactly
<4> update drivers in the qemu host or guest?
<1> in the guest OS
<1> i can't get pptp client to work in windows so i was wondering if updating the realtek drivers might do something
<4> are you using the user networking?
<4> instead of tun/tap
<1> yeah -net user you mean?
<4> yeah
<1> that's in my command line
<1> should i explore tun/tap?
<3> you only have -net user ?
<1> yeah that's it
<4> i think pptp is a lot like ipsec
<4> where it has its own protocol
<4> other than tcp/udp
<4> which is all net user supports
<1> hmmm ok, well i've done enough for tonight
<1> this was a lot of fun
<1> i haven't installed linux for years
<4> so your mouse works right now?
<1> i've been fooling around for a while and i'm not hitting that invisible wall so far
<4> cool, i'll probably try it tomorrow
<1> hope it works for you
<4> im going to sleep now too
<4> or soon
<4> night
<1> heh me too
<1> night punk-***
<5> hi everyone
<5> I have searche the mailing lists and haven't found a hint for special qemu windows drivers, as vmware does it. has this been discussed somewhere? is anyone attempting to build an optimized windows video driver for qemu like vmware does? I have been impressed by the ability of vmware to even deal with direct3d, I presume they map it onto opengl. it would be totally cool if that would also be seen in a free software dress
<3> someone was working on an opengl proxy of some sorts (linux host - windows guest). nothing has been published yet.
<6> hi all
<6> trying to port qemu to OS/2 and having some probs
<6> op.o gives:
<6> ***embler messages:
<6> Error: unknown pseudo-op: `.section'
<6> Error: unknown pseudo-op: `.previous'
<6> Error: unknown pseudo-op: `.section'
<6> Error: unknown pseudo-op: `.previous'
<6> using GCC 3.3.5
<6> as 2.14
<6> any ideas?
<7> anyone know why vm on freebsd 6 running debian sarge would crash and burn whenever doing file operations, for example wgetting a 20 meg file?
<8> IceShaman: where does it crash? backtrace?
<7> it doesn't segfault crash, I mean it just takes up 90% CPU and promptly sits there until it's killed
<7> which is as good as, as either way it isn't working
<9> we are actually in 0.8.2 or just going to that?
<9> hint, !!!!!!!!!!!!!!!!!!!
<9> iamlost, annotate: I will kill hint
<9> /kick hint wake uuuuuuuuup!!!!!!!!!!! I'm requesting your presence NOW!
<9> xD
<10> Claunia: Be patient. Some people actually have jobs they have to go to, and sleep occasionally, stuff like that.
<9> pbrook, was just kidding
<11> lol
<11> :D
<9> TLF, shut up big piece of ****
<9> xD
<11> :D
<9> pbrook, we are currently in 0.8.2 or just preparing for it?
<10> yes
<0> hi
<9> pbrook, late, but, my calls work xD
<11> by the way, when will QVM86 updated?
<10> When someone writes some code worth updating it with.
<11> well, in dad-answers forum someone is trying to implement 16 bit code
<9> iamlost, better not to ask
<9> pbrook afraids me
<12> does it make a big performance difference if you have a -386 kernel or a -686 kernel?
<12> (in the host)
<13> hi hint.
<13> I just made a new mux patch with the time stamping fully abstracted.
<13> Along with the monitor.
<13> The time stamping was cool and I wanted it for the telnet server :-)
<0> hi jwessel
<0> if you can separate the mux patch from the syntax change, I can merge at least the mux
<13> Is there a prefered syntax you want?
<0> maybe it is better to wait until I decide if the syntax is OK
<13> Right now it can be fully hidden.
<13> Meaning if you don't use the mux stuff you don't know it is there, since the abstraction implements backward compatibility.
<13> I can change it so you cannot specify it from the command line and that it is only used internally.
<14> moin
<13> moin nox-
<15> moin nox-
<14> moin jwessel iamlost
<0> jwessel: no need to change in fact. But I am not sure I will commit before the 0.8.2 release
<13> hint that is not a problem.
<13> :-)
<13> Just want to get it to a state where it will ulimately be accepted.
<13> hint, did you already change qemu-doc.texi?
<13> Else I was going to add in about the time stamp feature.
<0> I did not mentionned the timestamp feature - you can add it
<9> jwessel, hi
<9> hint, wont you say me who is your friend xD?
<13> Hi Claunia
Return to
#qemu
or
Go to some related
logs:
gleam CHARSET = latin1
#gaim
framebuffer vmplayer
#math
Starting OpenLDAP: (db4.2_recover not found), slapd.
#lisp
#linuxhelp
install xmms on ubunti
lib expat gentoo
chrish Camwithher
|
|