Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I downloaded the respective iso-file and the installation went well.
In principle FreeDOS works fine with the exception of networking. I simply canīt get qemu to let FreeDOS connect to the internet.
After a reboot FreeDOS says: "Error: Your ethernet card reported an error for every packet we sent."
And with "-net nic,model=ne2l_isa" in command-line: "Your DHCP server never responded and no packets were seen on the wire."
My terminal says: " Warning: vlan 0 is not connected to host network". qemu montitor says:
Code:
info network
hub 0
\hub0port0: ne2k_pci.0: index=0,type=nic,model=ne2k_pci,macaddr=52:54:00:12:34:56
I have not used QEMU with FreeDOS. I have used other tools, just not QEMU. If I get a chance I will try to replicate the behavior and post what I discover.
Not tonight, the wife and I are enjoying "international Talk Like a Pirate Day".
thanks for the reply.
In the meantime I subscribed to the qemu mailing list and discussed the problem there.
I seems I could come up with a solution.
Quote:
Warning: vlan 0 is not connected to host network
means the following:
Quote:
This means you have given QEMU a command line which defines a
network card but no network backend, so you get a virtual bit
of ethernet that's not connected to anything. If you're using
old-style "-net nic,..." then you must also pass "-net user" or
some other -net option specifying the backend. Similarly if
you're using new-style -device to specify the network adaptor
type then you must also pass a -netdev option to specify the backend.
(If you specify no -net/netdev options at all then you get a
default which is -net user and some network adaptor which
depends on the machine type; but if you specify any -net options
then you get no defaults provided by QEMU and you have to
specify all of the relevant options yourself.)
Further suggestion:
Quote:
Try a different NIC, eg with
-net nic,model=ne2k_isa -net user
So I typed "qemu-system-i386 drivec.img -net nic,model=help" into the terminal.
That gave me as valid options:
Code:
qemu: Supported NIC models:
ne2k_pci,i82551,i82557b,i82559er,rtl8139,e1000,pcnet,virtio"
I finally came up with a command line that worked for me:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.