https://bugzilla.novell.com/show_bug.cgi?id=458967 Jason Douglas changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lbendixs@novell.com, jdouglas@novell.com AssignedTo|cgriffin@novell.com |jfehlig@novell.com QAContact|qa@suse.de |jdouglas@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User terje@nordland-teknikk.no added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c3 Terje J. Hanssen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|terje@nordland-teknikk.no | --- Comment #3 from Terje J. Hanssen 2008-12-15 12:30:15 MST --- First, as information, the network was configured automatic with NetworkManager during my installation. After login I used YaST>Virtualization>Install Hypervisor to install Xen. I will suggest and would expect (as surely normal users also) that the network(bridge) also was configured, so that it works directly after installing a winxp vm. (The same issue looks to be repeated currently on sled11 beta6 also). Re: comment #2, to reply this first: ------------------------------------ # cat /etc/sysconfig/network/ifcfg-pan0 cat: /etc/sysconfig/network/ifcfg-pan0: No such file or directory # ls /etc/sysconfig/network/ config ifcfg-eth0 ifcfg.template if-down.d if-up.d scripts dhcp ifcfg-lo ifcfg-wlan0 ifroute-lo providers That is no ifcfg-pan0 found. Regarding 'tap1.0', the only related I remember is my OpenVPN config file which uses 'dev tun' (while 'tap tap' is commented out) Though another issue, NetworkManager doesn't look to work to import my OpenVPN configuration. I thought this was fixed upstreams so also for openSUSE 11.1-RC1 (as on sled11 beta). Re: comment #1 --------------- # /etc/xen/script/network-bridge stop bridge=pan0 bash: /etc/xen/script/network-bridge: No such file or directory # ls /etc/xen/script/ ls: cannot access /etc/xen/script/: No such file or directory # service network restart Shutting down the NetworkManager done Shutting down network interfaces: eth0 device: Intel Corporation 82566MM Gigabit Network Connection (rev 03) ls: cannot access /sys/class/net/eth0/brif/: No such file or directory done pan0 No configuration found for pan0 Nevertheless the interface will be shut down. done tap1.0 No configuration found for tap1.0 Nevertheless the interface will be shut down. ls: cannot access /sys/class/net/tap1.0/brif/: No such file or directory could not find configuration file ifcfg-tap1.0 tap1.0 tunctl not available -- install tunctl or uml-utilities done vif1.0 No configuration found for vif1.0 Nevertheless the interface will be shut down. ls: cannot access /sys/class/net/vif1.0/brif/: No such file or directory done wlan0 device: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) ls: cannot access /sys/class/net/wlan0/brif/: No such file or directory done Shutting down service network . . . . . . . . . done Starting the NetworkManager done # brctl show bridge name bridge id STP enabled interfaces Question: Which config file to set vif? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User terje@nordland-teknikk.no added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c5 Terje J. Hanssen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|terje@nordland-teknikk.no | --- Comment #5 from Terje J. Hanssen 2008-12-15 13:59:14 MST ---

Try using "Tradition Method: ifup" instead of NetworkManager. You'll probably have to configure a bridge manually though, but this is easy using yast2-network.

I have now run YaST | NetworkDevices with "ifub", which installed a package from the dvd media. A normal Internet connection works with eth0 However, trying to open and run the VM Manager | winxp vm guest, it didn't work and the following error message box arised: Error starting domain: POST-operasjon feilet: xend_post: error from xen daemon: (xend.err 'Device 0 (vif) could not be connected. Could not find bridge device pan0') Details: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 485, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 379, in startup self.vm.create() File "/usr/lib64/python2.6/site-packages/libvirt.py", line 262, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: POST-operasjon feilet: xend_post: error from xen daemon: (xend.err 'Device 0 (vif) could not be connected. Could not find bridge device pan0') -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User terje@nordland-teknikk.no added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c7 Terje J. Hanssen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|terje@nordland-teknikk.no | --- Comment #7 from Terje J. Hanssen 2008-12-15 15:10:54 MST ---

Change that to be br0, or whatever you have called your bridge.

I havent't called the bridge anything, the installation has ;) yes, it was: linux-2689:/etc/xen/vm # cat windowsxp-1 | grep vif vif=[ 'mac=00:16:3e:1b:c4:a9,bridge=pan0,model=rtl8139', ] now after change: linux-2689:/etc/xen/vm # cat windowsxp-1 |grep vif vif=[ 'mac=00:16:3e:1b:c4:a9,bridge=br0,model=rtl8139', ] Now the winxp vm can be opened and run again. But it still doesn't look to receive a real ip_adr, first 0.0.0.0 and lastly a fake one after timeout(?) terje@linux-2689:~> ping 169.254.213.16 PING 169.254.213.16 (169.254.213.16) 56(84) bytes of data.

From 192.xx.xx.105: icmp_seq=1 Destination Host Unreachable

What is output of 'brctl show' after configuring "Traditional Networking" and your bridge device?

linux-2689:/etc/xen/vm # brctl show bridge name bridge id STP enabled interfaces pan0 8000.be5adc7c2e44 no tap1.0 vif1.0 # ifconfig -a eth0 Link encap:Ethernet HWaddr 00:1E:EC:24:DA:60 inet addr:192........... lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 ...... pan0 Link encap:Ethernet HWaddr BE:5A:DC:7C:2E:44 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) tap1.0 Link encap:Ethernet HWaddr BE:5A:DC:7C:2E:44 inet6 addr: fe80::bc5a:dcff:fe7c:2e44/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:68 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:12767 (12.4 Kb) TX bytes:468 (468.0 b) vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:6 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) wlan0 Link encap:Ethernet HWaddr 00:1F:3B:15:1E:D5 inet6 addr: fe80::21f:3bff:fe15:1ed5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:940 errors:0 dropped:0 overruns:0 frame:0 TX packets:307 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:340131 (332.1 Kb) TX bytes:108936 (106.3 Kb) wmaster0 Link encap:UNSPEC HWaddr 00-1F-3B-15-1E-D5-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User terje@nordland-teknikk.no added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c9 Terje J. Hanssen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|terje@nordland-teknikk.no | --- Comment #9 from Terje J. Hanssen 2008-12-16 02:46:06 MST --- Sorry, I think this looks "too manual" and beyond my experience and knowledge. Maybe I could have followed a detailed howto step by step. What I can do, is to wait two days for the final 11.1 release and create a new installation and configure the network with traditional YaST method from the beginning, and go from there with Xen. In the current case, 11.1-RC1 is done using a vanilla new installation and automatic network configuration with NM as mentioned previously. (I have also SLED11/xen beta6 installed in multiboot on the same machine (hp8710w mobil workstation), and the network issue behaviour looks indentical in a corresponding winxp vm there, though I haven't looked on every detail) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User jdouglas@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c11 --- Comment #11 from Jason Douglas 2008-12-16 16:13:11 MST --- Please note that if you install the XEN pattern during the installation of the OS, then your networking should be setup properly by default. Of course, even then, it's still a good idea to make sure that NetworkManager hasn't been selected and that a bridged network configuration is the default. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User jfehlig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c13 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |claudiu@virtuamagic.com --- Comment #13 from James Fehlig 2009-01-05 16:45:22 MST --- (In reply to comment #12 from Claudiu Cismaru)

I have a similar problem. I upgraded from openSUSE 11.0 (where EVERYTHING worked fined) to openSUSE 11.1 (boot with net x64 disk, choose upgrade etc) and now I don't have network for hvm machines :( .. WindowsXP1 it's the only hvm machine. xpower:~# brctl show bridge name bridge id STP enabled interfaces eth0 8000.001d0905cb77 no peth0 vif1.0 vif17.0 vif3.0 vif8.0 vif9.0

There should be a tap device associated with that vm, e.g. tap9.0. Is that vm using pv drivers? Also can you provide the configuration file for the vm and output of 'ip route list'. Finally, /var/log/xen/qemu-dm-.log would be useful as well. Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User jfehlig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c15 --- Comment #15 from James Fehlig 2009-01-06 08:29:02 MST --- (In reply to comment #14 from Claudiu Cismaru)

But the interesting part is that the paravirtualized machines WORK with "bridghe=xenbr0"!!! That's why I didn't knew where to start to debug my problem...

The vif script used for PV guests can access xenstore and read bridge info from there. vif script for HVM guests do not have this luxury and use the device with default route (assuming it is a bridge device) when bridge is not specified. In your case, bridge was specified - but one that does not exist. This used to work because HVM vif script would try ethX when xenbrX was specified but non-existent. The script was changed in openSUSE11.1/SLES11 since we no longer use network-bridge by default.

I want to try to configure in xend-config a bridge name and use it in all domU configuration files...

I would suggest not using network-bridge and use YaST to configure bridge instead. Then set bridge name in all domU config files to the bridge name you used in YaST. network-bridge can be disabled in xend-config.sxp with (network-script ) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User jfehlig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c17 --- Comment #17 from James Fehlig 2009-01-06 16:17:56 MST --- (In reply to comment #16 from Claudiu Cismaru)

...

network-bridge can be disabled in xend-config.sxp with (network-script )

Why? It detects the bridge from network configuration? Or why have to disable it?

The network-bridge script manipulates the network configuration unbeknownst to sysconfig, which causes several problems. E.g. try doing 'rcnetwork restart' when using network-bridge. You'll find that your network is trashed afterwards. When creating bridges via YaST, a proper /etc/sysconfig/network/ifcfg- is created and thus integrated with rest of sysconfig scripts. Things like 'rcnetwork start|stop|restart' will work, even when vms are running. It's a much better setup than the hacky network-bridge script. So I suggest creating/manipulating your bridges in YaST, allowing sysconfig to properly control them. Does this make sense? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User claudiu@virtuamagic.com added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c19 --- Comment #19 from Claudiu Cismaru 2009-01-08 14:35:28 MST --- I just finished to reconfigure the system and now it's OK. For me, this bug it's closed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User terje@nordland-teknikk.no added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c21 --- Comment #21 from Terje J. Hanssen 2009-01-09 17:12:30 MST --- Created an attachment (id=264263) --> (https://bugzilla.novell.com/attachment.cgi?id=264263) YaST2 Network setting overview -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User terje@nordland-teknikk.no added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c23 --- Comment #23 from Terje J. Hanssen 2009-01-09 17:15:37 MST --- Created an attachment (id=264265) --> (https://bugzilla.novell.com/attachment.cgi?id=264265) 'brcrl show' and 'service network restart' outputs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 Jason Douglas changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #264265|application/octet-stream |text/plain mime type| | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User terje@nordland-teknikk.no added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c25 Terje J. Hanssen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|terje@nordland-teknikk.no | --- Comment #25 from Terje J. Hanssen 2009-01-09 22:30:57 MST --- Thanks, that solved my wired network problem. And it's stupid, that was myself who had configured eth0 with DHCP in YaST. As far as I can see, bridge 'br0' is assosiated with device 'wlan0' and 'br1' with 'eth0'. To prepare also wireless access for both suse11.1 dom0 and winxp vm, should I similar delete the DHCP configuration for wlan0? I got also wired network access for both suse11.1 dom0 and winxp vm, got replies on ping both ways and was able to get winxp login screen using rdesktop. (Although remote access already was enabled on winxp's Mycomputer, user login was refused due to some account restriction. One single user (also admin) without password was created on winxp. Althoug this obviously is another, follow-up issue, any idea what is wrong here?) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User jfehlig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c27 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |terje@nordland-teknikk.no --- Comment #27 from James Fehlig 2009-01-12 13:13:47 MST --- So do you have any more issues with *this* bug (Network issue in winxp vm)? Sounds like your problems are resolved. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=458967 User jfehlig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=458967#c29 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #29 from James Fehlig 2009-01-12 22:40:56 MST --- Closing. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.