Re: [Freedos-user] qemu networking and wattcp.cfg
Hi, I'm glad you figured this out! I wasn't aware of the "-net user" parameter, always used qemu the 'hard' way, by wiring the whole beast myself :) it's quite nice, looks like Qemu provides the same level of user-friendliness than virtualbox now, by hiding all the complex networking from the user, and providing some minimalistic embedded dhcp/dns/routing/nat capabilities. Thanks for sharing this easy solution. Btw, I see you use '&' to daemonize the qemu process, it might be 'cleaner' to use the '-daemonize' parameter instead (at least then qemu knows that it has to detach itself, not sure if it makes any difference in real life, though). Nonetheless, I still believe you will want to switch over to DOSemu at some point - my experience with FreeDOS + Qemu hasn't been great.. Poor performances, and erratic behavior of the keyboard (key presses that get repeated without reasons, caps lock that get stuck in one position, cursors not working in some CLI applications...). Definitely not useable for any work. But YMMV of course. cheers, Mateusz On 06/20/2013 09:07 PM, sakura kinomoto wrote: > Monsieur Mateusz Viste, thank you for link! Near it, I find: > > > http://en.wikibooks.org/wiki/QEMU/Networking: > > " > The following two command lines are equivalent: > qemu ... & > qemu ... -net nic -net user & > " > > I just forgot to use "-net user" parametre > > > Now I have network works > (and gpxe was find network, because I was run it in qemu without parametres = > with parametre "-net nic -net user". > Thank you vey much! ^^ > -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] qemu networking and wattcp.cfg
Monsieur Mateusz Viste, thank you for link! Near it, I find: http://en.wikibooks.org/wiki/QEMU/Networking: " The following two command lines are equivalent: qemu ... & qemu ... -net nic -net user & " I just forgot to use "-net user" parametre Now I have network works (and gpxe was find network, because I was run it in qemu without parametres = with parametre "-net nic -net user". Thank you vey much! ^^ -- sakura kinomoto -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] qemu networking and wattcp.cfg
Hi, I'm not sure whether your packet driver works fine with the ne2k_pci qemu interface or not, but I suppose it's okay. What I'm pretty sure however is that you use qemu networking in a wrong way. It appears that you hook up a PCI network card into your virtualmachine, but without binding it anywhere. It's like you'd put an ethernet card into your PC, but without connecting it to a switch. The idea is therefore to emulate a fake switch, and connect both your virtual machine and host PC to it. Since you use Linux, it's quite easy - you just have to use the excellent linux bridge driver. It would go something like this: # Create an empty bridge brctl addbr mybridge # Create a virtual TAP interface tunctl -t fdos # Configure both your physical and virtual interfaces into promiscuous mode. ifconfig eth0 0.0.0.0 promisc up ifconfig fdos 0.0.0.0 promisc up # Add both your physical and virtual interfaces into the bridge brctl addif mybridge eth0 brctl addif mybridge fdos # Configure your networking (it's held by the bridge now, not by the eth interface anymore!) ifconfig mybridge 192.168.0.2/24 up ip route add default via 192.168.0.1 # Finally, start your FreeDOS virtual machine qemu /dev/sda -soundhw sb16 -net nic,vlan=0,model=ne2k_pci -net tap,vlan=0,ifname=fdos,script=no,downscript=no Note, that the 'vlan' stuff above is not a real vlan (like in 802.1q), but an internal identifier for qemu layer 2 bindings. Just in case you were wondering. There is no reason why this wouldn't work, but if you ask me, I'd rather go with DOSemu. You would get much better performances (unless you have VT-x and use it via KVM already), and exchanging files between the host and the "guest" would be trivial, since both would share the same filesystem. Also, with DOSemu you can run several parallel instances of FreeDOS (although only one will have network access). Actually, qemu could be a nice tool if we'd want to roll a 'universal' FreeDOS distro that works on any modern PC - just installing a bare linux kernel + Qemu, and launching FreeDOS fullscreen as a qemu VM, with old hardware emulation (SB16, NE2000...) done basing on the real hardware, and the Linux kernel would deal with the real hardware and its drivers. cheers, Mateusz On 06/20/2013 11:58 AM, sakura kinomoto wrote: > Hi all! > > I use Debian Squeeze as my main system; > > I try to run Qemu: > > root@109:/home/kitty# qemu /dev/sda -soundhw sb16 -net nic,model=ne2k_pci & > > here is my Autoexec.bat: > > set path=c:\free > cd free > set BLASTER=A220 I5 D1 H5 T6 > set WATTCP.CFG=c:\free > > I try to run pcipkt.com; maybe, it works (?) - it not say any error, it give > me to see MAC-address > > pcipkt 0x60 > > > > > but any wattcp - software (dillodos, elinks) can not connect network; - > neither by dhcp, no by bootp, no by rarp > > Please, tell me - > what "virtual network card" I need to use in Qemu? > what packet driver I need to use? > what lines I need to write in "wattcp.cfg"? > > > Thank you very much, for any answer! > -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] qemu networking and wattcp.cfg
Hi all! I use Debian Squeeze as my main system; I try to run Qemu: root@109:/home/kitty# qemu /dev/sda -soundhw sb16 -net nic,model=ne2k_pci & here is my Autoexec.bat: set path=c:\free cd free set BLASTER=A220 I5 D1 H5 T6 set WATTCP.CFG=c:\free I try to run pcipkt.com; maybe, it works (?) - it not say any error, it give me to see MAC-address pcipkt 0x60 but any wattcp - software (dillodos, elinks) can not connect network; - neither by dhcp, no by bootp, no by rarp Please, tell me - what "virtual network card" I need to use in Qemu? what packet driver I need to use? what lines I need to write in "wattcp.cfg"? Thank you very much, for any answer! -- sakura kinomoto -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
