When the installation program asked for information about network configuration, as a
first step, I chose DHCP configuration and, as usualy, the network has been set
If I recall correctly qemu has a built-in DHCP server.
That's the one that served you, not a "real" DHCP server
running on your LAN, that is, you are not in any way connected
to the "real" network.
#qemu -L /usr/local/share/qemu -localtime -net nic,macaddr=00:15:f2:44:2d:01 -net
socket,mcast=126.96.36.199:1234 -hda pc01.img -cdrom /dev/acd0 &
but the network in the guest system does not work.
It makes sense, that the multicast option will work
between virtual hosts only. That is, it uses multicast
to provide a virtual broadcast domain, which appears to
the host operating system as a ethernet device.
ifconfig in the guest system tells:
ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
media: Ethernet 10baseT/UTP <full-duplex>
If I try:
#ping 10.0.2.2 (the gateway)
all packets are lost. For this reason, I've tryed a static IP configuration
but the gateway does not respond. So it is useless to try with a second guest
No, infact it's the exact opposite. This type of device
will work *only* if you add another virtual system.
To get connected to the "real" network, you must use tap
Browsing the qemu's wiki I found out that there is a newer
and simpler approach that I am not familiar with:
So, if you do want internet access, just remove all network
associated options and it will work automagically. If you just
want to connect guest systems together use multicast or socket
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"