You can also use nicscan.exe ( http://www.georgpotthast.de/sioux/packet.htm) or pcinic.com ( http://dunfield.classiccmp.org/dos/index.htm) to verify the nic is correctly configured in the VM.
On Thu, May 26, 2022 at 6:07 AM Louis Santillan <lpsan...@gmail.com> wrote: > You also need to provide a ‘model’ on the ‘network’ parameter. e1000 or > rtl8139 have DOS packet drivers available. > > On Thu, May 26, 2022 at 4:29 AM <c...@crg.eti.br> wrote: > >> Hello everybody. Thanks for the help so far, sorry for the delay in >> responding. >> >> The simplest way for me to create a FreeDOS VM on my server was to >> install it on a local VM and copy the disk image to the server, once there >> I created the VM with the following command. >> >> virt-install \ >> --name DOS01 \ >> --network bridge=br0 \ >> --ram 32 \ >> --disk /kvm/disk/dos01.img \ >> --graphics=vnc,password=cadeafaca,listen=0.0.0.0,port=5913 \ >> --hvm \ >> --import >> >> Almost everything worked. >> The other VMs (Debian) are happy with the bridge interface but FreeDOS >> returned the following error. >> >> QEMU network detected. >> Physical hardware networking is not supported at this time. >> >> I've tried a few variations trying to use tap interface but still no >> success. Any idea what to do? >> Like the other VMs, I want this one to be directly exposed to my internal >> network, not using NAT. >> >> The point with all this is to try to rebuild the old BBS and DOS is not >> exactly an environment I expect to see networking in. Perhaps a simpler way >> is to simulate a serial interface and then try to export it to the network. >> >> Thanks everyone for the help! >> >> Cesar >> >> _______________________________________________ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> >
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
