| |
| |
| |
|
Page: 1 2 3
Comments:
<0> and the simulated hardware will be different from that of real install so there is no point in trying that :)
<1> i don't know how to make a disk image
<2> You really want a fresh install.
<1> like a ghost CD?
<2> use qemu-img
<2> If you really wanted to be convoluted you could.
<1> gemu-img mount-location
<1> then burn that to a cd?
<0> JerryMcFarts: have you tried the docs? :) qemu-img create mydisk.image 16G
<2> 1. create a suitably large disk image
<2> 2.
<2> oops
<2> 2. ghost the partition to an image
<1> lol i don't have that extra room
<1> im down to my last 8 gigs
<0> JerryMcFarts: isn't 4G enough for XP?
<2> 3. Ghost XP onto the virtual image (not sure ghost works under qemu)
<2> 4. Repair the XP install under qemu
<2> 5. Profit.
<1> i 35 gigs of stuff installed on windows right now
<2> Maybe you should run linux under qemu in XP! ;0)
<1> ?
<1> lol thats funny
<1> i run linux most of the time
<1> I just can't get Guitar Pro 5 to run the best
<2> hehe
<1> it plays fine if only i do nothing else
<1> but it errors out here and there
<1> guitar pro 5 under wine
<1> but since i do come over here, i slowly install things lol
<1> Video games etc.
<3> is there a prebuilt kqemu module for ubuntu?
<0> anyone wants to test a simple patch for windows networking with rtl8139 driver? :)
<2> a patch to what?
<0> WaxDragon: to the hw/rtl8139.c
<2> sire
<2> uh
<2> sure
<0> testing requires having windows install and CVS version of qemu; grab at http://pastebin.ca/75824, build, run with -net user -net nic,model=rtl8139
<0> that should not work except for DHCP (if enabled) :)
<0> but try to disable "task offloading" in driver properties under windows and then it should work OK
<0> I need that to test modifications for win64/vista
<0> and I do not have either one
<2> hmm
<2> it doesn't want to patch...
<2> very odd
<2> must I use -net user? I typically use bridging
<0> WaxDragon: http://pastebin.ca/raw/75824 raw download
<0> WaxDragon: you just need to override the -nic option
<0> WaxDragon: that is -net nic,model=ne2000 is the default so override with rtl8139
<2> k
<2> I was already using rtl8139 ;0)
<0> :) actually that was -net nic,model=ne2k_pci is the default
<0> :)
<0> WaxDragon: how comes? :)
<2> playing around
<0> WaxDragon: seriously that should not work without some patching if you have latest realtek drivers installed
<2> I wasn't using the offical realtek drivers.
<0> WaxDragon: I found a couple of errors from my side reading the docs; packet re***embly does not work, old drivers are not using that feature
<0> WaxDragon: so you can test if patch does not change your happy living?
<0> :)
<2> Well, I just ftped a 8.4M file from the LAN ftp server, so it seems to work ;0)
<2> and it's printing debug messages to stdout, so I know the patch applied. ;0)
<2> want me to try the oem drivers?
<4> okay.. same old thing.. loading the mandrake image stops saying enter init= fresh download of the image, md5 verified etc.
<0> WaxDragon: would be nice of you :)
<0> WaxDragon: are you seeing RTL8139C+ DTCCR ... lines in debug?
<2> It's kinda flying by
<2> I see things like
<2> RTL8139: TSAD read val=0xf00f
<0> WaxDragon: ah, that's the rtl8139 common C mode; I patched the C+ mode (seems that is picked by later windows drivers)
<0> someone please enlighten me if it is OK to use functions from slirp sources in network driver emulator
<2> Well, I forced XP to load the 8139C+ oem driver, lets see what happens
<2> RTL8139C+ DTCCR write offset=0x0 val=0x010dda08 descriptor=0
<2> hmm
<2> ftp is not working, on the LAN.
<2> I was able to get out to ftp.redhat.com though, odd.
<2> spoke too soon I guess.
<2> oh, wait. tcp offloading
<2> Now it works.
<2> I wonder if this is the same problem I see when using the oem drivers under ReactOS.
<2> If I only knew where it toggles the offloading in the registry.
<0> WaxDragon: nope :)
<0> WaxDragon: the reactos thing seems plausible
<2> Well, it gives me a place to start looking.
<2> ftp telnet smb all seem to work with offloading turned off. anything else?
<0> WaxDragon: good to see that thing works; now I need to either pull cksum() from slirp code or do something different :)
<0> WaxDragon: enough :)
<2> k
<2> hmm
<2> hold on
<2> nevermind. ;0)
<0> WaxDragon: what?
<2> I thought I was using the wrong binary, but I wasn't
<2> the debug messages. ;)
<2> so without your patch, qemu emulates a 8139/a/b?
<0> no that 8139c+
<0> but still without task offloading; working on that now
<0> WaxDragon: oh that a/b/c/d thing; these are backward-compatible, but some OS's look further and find C+ mode enabled that's why later windows won't work
<6> ...
<0> scrolling
<0> WaxDragon: you scrolled back :)
<2> ?
<2> I've lost contact with my primary machine.
<2> ah, better
<7> WaxDragon: so, you're a reactos developer?
<0> WaxDragon: you seem to be reactos man
<0> :)
<2> Somewhat
<2> I'm the lead tester. I commit code when I can.
<7> WaxDragon: why is the audit stalled at 92.1% ?
<0> WaxDragon: do you know if reactos rtl8139 driver is using ip/tcp/udp checksum offloading?
<2> It's not stalled, it's just moving very slowly now.
<2> garrison: we don't have a native 8139 driver.
<2> I use either the XP or the oem one.
<0> WaxDragon: ok
<2> kbrooks: basically we are into the ntoskrnl audit, and there are few that know that code really well. Contacting old devs is taking time.
<2> I removed your patch, then tried to force the oem 8139C+ into windows. That was the last I heard from my primary machine.
<2> I'm ***uming it crashed.
<0> WaxDragon: mind posting the debug log if you collected it?
<0> WaxDragon: or it was native run crashed? :)
<2> I didn't get anything. I was running XP under qemu and it *took out the host*
<0> mmm
<2> If I'm lucky, it just busted networking.
<2> My guess is I oopsed the kernel someone.
<2> *somehow
<0> WaxDragon: there *may* be a memory leak in rtl8139 emulation, not sure
<2> I'll find out when I get home.
<0> WaxDragon: 'll wait
<7> how do i enable internet in qemu?
<0> kbrooks: which one?
<7> garrison: ?
<0> kbrooks: there are many internets; the www looking is enabled by default
<2> lol
<2> slirp is enabled by default
<2> just don't try to ping off subnet.
<0> WaxDragon: no the slirp is too low level
<2> ;0)
<2> ?
<0> WaxDragon: people frequently want internet; they open a browser and take a look
<0> WaxDragon: a few know what the slirp is :)
<2> Well, i normally refer to it as "usermode networking"
<2> lol
<2> One of our senior devs claimed networking under qemu has never worked for him.
<2> he was trying to ping off subnet. ;0)
<0> kbrooks: seriously, which feature does not work for you?
<0> WaxDragon: that once was a channel topic :)
Return to
#qemu
or
Go to some related
logs:
fedora 2 reinstalling option
#nvidia
Ubuntu+remove programm
#math
awk get hostname
bnv_qt_test dapper
#mysql
could not create dbus message SuSE
tomboy backport
#php
|
|