Re: QEMU and tap problems
On Thu, September 20, 2007 20:47, RW wrote: On Thu, 20 Sep 2007 06:21:20 -0500 Doug Poland [EMAIL PROTECTED] wrote: I've been following the various instructions I've found on the web in an attempt to get tap networking with qemu-devel-0.9.0s.20070802 Are you actually sure that you actually need tap? Good question. My reason for running Win2K server under QEMU is I'm working on a java app that speaks to SQLServer. Initially, all I need is to communicate with the host/guest on the same machine. After that, I'll need the QEMU guest to be on the network so I can connect to the java app from other computers. A lot of the how-tos are out of date I've noticed that :( - recent versions of Qemu can give a guest network access without it. When I started QEMU with the -net nic -net user switches, then Windows gets a 10. address and the guest can see the network. However, I cannot see open ports I'm interested in, 1433 and 3389, from the host. Windows thinks it has connectivity, but I cannot ping the default gateway from the guest and I cannot ping the IP of the guest from the host. This suggest you are accessing the net without tap, ping is a setuid binary so pings generated in the guest can't be passed on by qemu. The guest definitely could not see the hosts network with tap set up the way I described. I was using ping as a basic diagnostic tool and did not know the limitation you described. -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU and tap problems
On Fri, 21 Sep 2007 07:08:41 -0500 (CDT) Doug Poland [EMAIL PROTECTED] wrote: On Thu, September 20, 2007 20:47, RW wrote: On Thu, 20 Sep 2007 06:21:20 -0500 Doug Poland [EMAIL PROTECTED] wrote: I've been following the various instructions I've found on the web in an attempt to get tap networking with qemu-devel-0.9.0s.20070802 Are you actually sure that you actually need tap? Good question. My reason for running Win2K server under QEMU is I'm working on a java app that speaks to SQLServer. Initially, all I need is to communicate with the host/guest on the same machine. After that, I'll need the QEMU guest to be on the network so I can connect to the java app from other computers. A lot of the how-tos are out of date I've noticed that :( - recent versions of Qemu can give a guest network access without it. When I started QEMU with the -net nic -net user switches, then Windows gets a 10. address and the guest can see the network. However, I cannot see open ports I'm interested in, 1433 and 3389, from the host. I understand it when you run a guest without any networking switches, it sees an emulated ethernet interface that behaves as if it's connected to a basic NAT router. This emulation is running as an ordinary user in the host, so it can't do anything that requires root access - which is why you can't ping out. And because of the NAT you can't make incoming connections to the guest (which prevents incoming pings). IIRC there is some kind of redirection switch that will allow you to connect to guest ports via ports on the host (analogous to the port forwarding on a NAT router). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU and tap problems
Have a look at this article: http://sysnotes.hia.no/2007/09/21/how-to-fix-network-bridging-for-qemu/ It may give you some ideas although it is for Linux. The basic premise is to make qemu emulate the guest host so it appears as any other physical host on the network. It may work better. Regards Oz RW wrote: On Fri, 21 Sep 2007 07:08:41 -0500 (CDT) Doug Poland [EMAIL PROTECTED] wrote: On Thu, September 20, 2007 20:47, RW wrote: On Thu, 20 Sep 2007 06:21:20 -0500 Doug Poland [EMAIL PROTECTED] wrote: I've been following the various instructions I've found on the web in an attempt to get tap networking with qemu-devel-0.9.0s.20070802 Are you actually sure that you actually need tap? Good question. My reason for running Win2K server under QEMU is I'm working on a java app that speaks to SQLServer. Initially, all I need is to communicate with the host/guest on the same machine. After that, I'll need the QEMU guest to be on the network so I can connect to the java app from other computers. A lot of the how-tos are out of date I've noticed that :( - recent versions of Qemu can give a guest network access without it. When I started QEMU with the -net nic -net user switches, then Windows gets a 10. address and the guest can see the network. However, I cannot see open ports I'm interested in, 1433 and 3389, from the host. I understand it when you run a guest without any networking switches, it sees an emulated ethernet interface that behaves as if it's connected to a basic NAT router. This emulation is running as an ordinary user in the host, so it can't do anything that requires root access - which is why you can't ping out. And because of the NAT you can't make incoming connections to the guest (which prevents incoming pings). IIRC there is some kind of redirection switch that will allow you to connect to guest ports via ports on the host (analogous to the port forwarding on a NAT router). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
QEMU and tap problems
Hello,
I've been following the various instructions I've found on the web in an
attempt to get tap networking with qemu-devel-0.9.0s.20070802 and
kqemu-kmod-1.3.0.p11_2 on 6.2-STABLE.
qemu was compiled with:
_OPTIONS_READ=qemu-devel-0.9.0s.20070802
WITH_KQEMU=true
WITHOUT_HACKS_CIRRUS=true
WITHOUT_RTL8139_TIMER=true
WITHOUT_SAMBA=true
WITH_SDL=true
WITH_CDROM_DMA=true
The kernel modules are loaded:
if_tap, bridge, aio, kqemu
The sysctls are changed:
sysctl net.link.ether.bridge_cfg=ath0,tap0
sysctl net.link.ether.bridge.enable=1
The tap device exists:
crw--- 1 root wheel0, 134 Sep 19 22:42 /dev/tap0
tap0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 0.0.0.0 netmask 0xff00 broadcast 0.255.255.255
ether 00:bd:01:3c:01:00
Opened by PID 1317
The qemu-ifup script exists:
cat /etc/qemu-ifup
#!/bin/sh
ifconfig ${1} 0.0.0.0
I launch qemu like this:
qemu -m 512 -localtime -hda VMs/w2k3.img -net nic -net tap
Windows Server 2003 comes up. If I attempt to use DHCP to configure the
interface in W2K3, I get a several minute pause while it attempts to
contact a DHCP server, finally it fails with the message:
This connection has limited or no connectivity
and windows assigns itself the 169.254.244.101 address.
If I try to manually configure the windows interface, i.e.,
IP: 172.16.1.15
NM: 255.255.255.0
DG: 172.16.1.1
NS: 172.16.1.17
NS: 172.16.1.21
Windows thinks it has connectivity, but I cannot ping the default
gateway from the guest and I cannot ping the IP of the guest from the
host.
So at this point, I have no networking from the guest OS. About the
only thing that I haven't seen on the web is people using wireless NICs
in the host. In my case, I have an atheros chipset connected via WPA2
to my WAP.
All help is appreciated...
--
Regards,
Doug
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU and tap problems
On 9/20/07, Doug Poland [EMAIL PROTECTED] wrote:
Hello,
I've been following the various instructions I've found on the web in an
attempt to get tap networking with qemu-devel-0.9.0s.20070802 and
kqemu-kmod-1.3.0.p11_2 on 6.2-STABLE.
qemu was compiled with:
_OPTIONS_READ=qemu-devel-0.9.0s.20070802
WITH_KQEMU=true
WITHOUT_HACKS_CIRRUS=true
WITHOUT_RTL8139_TIMER=true
WITHOUT_SAMBA=true
WITH_SDL=true
WITH_CDROM_DMA=true
The kernel modules are loaded:
if_tap, bridge, aio, kqemu
The sysctls are changed:
sysctl net.link.ether.bridge_cfg=ath0,tap0
sysctl net.link.ether.bridge.enable=1
The tap device exists:
crw--- 1 root wheel0, 134 Sep 19 22:42 /dev/tap0
tap0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 0.0.0.0 netmask 0xff00 broadcast 0.255.255.255
ether 00:bd:01:3c:01:00
Opened by PID 1317
The qemu-ifup script exists:
cat /etc/qemu-ifup
#!/bin/sh
ifconfig ${1} 0.0.0.0
I launch qemu like this:
qemu -m 512 -localtime -hda VMs/w2k3.img -net nic -net tap
Windows Server 2003 comes up. If I attempt to use DHCP to configure the
interface in W2K3, I get a several minute pause while it attempts to
contact a DHCP server, finally it fails with the message:
This connection has limited or no connectivity
and windows assigns itself the 169.254.244.101 address.
If I try to manually configure the windows interface, i.e.,
IP: 172.16.1.15
NM: 255.255.255.0
DG: 172.16.1.1
NS: 172.16.1.17
NS: 172.16.1.21
Windows thinks it has connectivity, but I cannot ping the default
gateway from the guest and I cannot ping the IP of the guest from the
host.
So at this point, I have no networking from the guest OS. About the
only thing that I haven't seen on the web is people using wireless NICs
in the host. In my case, I have an atheros chipset connected via WPA2
to my WAP.
All help is appreciated...
I just got tap working with an earlier build of qemu using clues from this site:
http://forums.bsdnexus.com/viewtopic.php?id=1563
Also, I can only get it working when I run it with sudo at the moment
and I have only tried with a wired nic. I have read in some places
that encryption causes problems with tap, but I don't have a link to
where I read it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU and tap problems
On Thu, 20 Sep 2007 06:21:20 -0500 Doug Poland [EMAIL PROTECTED] wrote: Hello, I've been following the various instructions I've found on the web in an attempt to get tap networking with qemu-devel-0.9.0s.20070802 and Are you actually sure that you actually need tap? A lot of the how-tos are out of date - recent versions of Qemu can give a guest network access without it. Windows thinks it has connectivity, but I cannot ping the default gateway from the guest and I cannot ping the IP of the guest from the host. This suggest you are accessing the net without tap, ping is a setuid binary so pings generated in the guest can't be passed on by qemu. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
