Re: [Qemu-discuss] no network connection in a windows xp guest

[Mike Lovell]

On 01/25/2012 07:31 AM, Thilo Rießner wrote:
> Dear Ekkard,
> as I'm using qemu-kvm with -net user, I don't think the requested information
> helps, but here it is nevertheless:
>
> ifconfig
> eth0      Link encap:Ethernet  Hardware Adresse 00:21:70:B8:75:A0
>            inet Adresse:192.168.0.122  Bcast:192.168.0.255  Maske:255.255.255.0
>            inet6 Adresse: fe80::221:70ff:feb8:75a0/64
> Gültigkeitsbereich:Verbindung
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:2170214 errors:0 dropped:1 overruns:0 frame:0
>            TX packets:2037648 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 Sendewarteschlangenlänge:1000
>            RX bytes:942125992 (898.4 Mb)  TX bytes:358010369 (341.4 Mb)
>            Interrupt:22 Speicher:f6fe0000-f7000000
>
> lo        Link encap:Lokale Schleife
>            inet Adresse:127.0.0.1  Maske:255.0.0.0
>            inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
>            UP LOOPBACK RUNNING  MTU:16436  Metric:1
>            RX packets:7288 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:7288 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 Sendewarteschlangenlänge:0
>            RX bytes:491569 (480.0 Kb)  TX bytes:491569 (480.0 Kb)
>
> wlan0     Link encap:Ethernet  Hardware Adresse 00:22:FB:26:A3:8C
>            inet Adresse:192.168.0.167  Bcast:192.168.0.255  Maske:255.255.255.0
>            inet6 Adresse: fe80::222:fbff:fe26:a38c/64
> Gültigkeitsbereich:Verbindung
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:431230 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:75236 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 Sendewarteschlangenlänge:1000
>            RX bytes:66980499 (63.8 Mb)  TX bytes:14490126 (13.8 Mb)
>
> ping 10.2.0.15
> PING 10.2.0.15 (10.2.0.15) 56(84) bytes of data.
> ^C
> --- 10.2.0.15 ping statistics ---
> 271 packets transmitted, 0 received, 100% packet loss, time 270145ms
>
> arp -a
> mailalt (192.168.0.33) auf 00:20:af:06:4b:c6 [ether] auf eth0
> ? (192.168.0.21) auf<unvollständig>  auf eth0
> ? (192.168.0.22) auf 00:50:56:94:7e:df [ether] auf eth0
> ? (192.168.0.53) auf 00:1d:73:19:69:ab [ether] auf eth0
> ? (192.168.0.208) auf 00:50:56:94:7e:c3 [ether] auf eth0
>
>
>
> Some more details about my setup: I'm using qemu-kvm Version 0.15.1-1.5.1,
> linux kernel 3.1.0-1.2 on a x86_64 hardware.
> Some tests with ReactOS give me the hint, that using qemu instead of qemu-kvm
> could solve my problem, but when I change the "machine" to qemu, I can't log
> in any more due to activation problems!
> On the qemu-kvm console I get the following information about the  virtual
> network (does the line "Devices not on any VLAN:" mean anything?):
>
> (qemu) info network
> LAN 0 devices:
> user.0: type=user,net=10.0.2.0,restrict=off
> user.1: type=user,net=10.0.2.0,restrict=off
> pcnet.0: type=nic,model=pcnet,macaddr=52:54:00:12:34:56
> Devices not on any VLAN:
>
> (qemu) info usernet
> LAN 0 (user.0):
> Protocol[State]   FD  Source Address  Port  Dest. Address  Port RecuQ SendQ
> UDP[99 sec]      27      10.0.2.2   67 255.255.255.255   68    0    0
> UDP[13 sec]      24 169.254.244.101  138 169.254.255.255  138    0    0
> LAN 0 (user.1):
> Protocol[State]   FD  Source Address  Port  Dest. Address  Port RecuQ SendQ
> UDP[99 sec]      26      10.0.2.2   67 255.255.255.255   68    0    0
> UDP[13 sec]      25 169.254.244.101  138 169.254.255.255  138    0    0

can you also provide the command you're using to invoke qemu/qemu-kvm? 
also, do you have -net user in there twice? i see two usermode 
networking devices in your info commands from the qemu monitor. that 
seems a little weird and i wonder if things are conflicting somehow.

mike