Re: [CentOS] CentOS 6 bridging problem.
The setup works well for different kernel. So it is not a problem with the configuration ;) Thanks for all help. Best regards, R. 2012/7/4 Gordon Messmer yiny...@eburg.com: On 06/25/2012 05:22 AM, Rafał Radecki wrote: Do you see an error in my configuration? Why is 10.20.0.108 not available? I don't have a lot of managed switches around to do extensive testing. The closest test I can do is on 5.8 with VLAN 2 and different IPs. Based on that, everything seems like it should work. Since you're able to set up the addresses on the interface without a bridge, the likelihood of a driver problem seems fairly low. Did you ever send the output of brctl show? You should definitely be able to run tcpdump on eth0.20 and see any traffic on that interface. You said that you saw none when you tried to ping the Linux host from the network. What about the reverse? Do you see data go out eth0.20 when you try to ping an address in the attached subnet from the Linux host? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 bridging problem.
Yes, it works well, no problems then. Best regards, Rafal, 2012/6/26 Gordon Messmer yiny...@eburg.com: On 06/26/2012 08:51 AM, Gordon Messmer wrote: Are you absolutely sure that the switch port connected to eth0 is configured to deliver tagged packets for VLAN 20 (and that the ping source is also on that VLAN)? ...and I should follow that up with: If you create a tagged ethernet interface on this system, with NO BRIDGES AT ALL, does the tagged interface work as expected? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 bridging problem.
ip route show 192.168.2.0/24 dev vmbr0 proto kernel scope link src 192.168.2.203 193.218.152.0/24 dev vmbr0 proto kernel scope link src 193.218.152.219 10.20.0.0/16 dev vmbr20 proto kernel scope link src 10.20.0.108 169.254.0.0/16 dev vmbr0 scope link metric 1003 169.254.0.0/16 dev vmbr20 scope link metric 1006 default via 193.218.152.1 dev vmbr0 ip addr show 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:25:22:0d:c2:2a brd ff:ff:ff:ff:ff:ff inet6 fe80::225:22ff:fe0d:c22a/64 scope link valid_lft forever preferred_lft forever 3: vmbr0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether 00:25:22:0d:c2:2a brd ff:ff:ff:ff:ff:ff inet 193.218.152.219/24 brd 193.218.152.255 scope global vmbr0 inet 192.168.2.203/24 brd 192.168.2.255 scope global vmbr0:1 inet6 fe80::225:22ff:fe0d:c22a/64 scope link valid_lft forever preferred_lft forever 4: venet0: BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/void inet6 fe80::1/128 scope link valid_lft forever preferred_lft forever 5: eth0.20@eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UP link/ether 00:25:22:0d:c2:2a brd ff:ff:ff:ff:ff:ff inet6 fe80::225:22ff:fe0d:c22a/64 scope link valid_lft forever preferred_lft forever 6: vmbr20: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether 00:25:22:0d:c2:2a brd ff:ff:ff:ff:ff:ff inet 10.20.0.108/16 brd 10.20.255.255 scope global vmbr20 inet6 fe80::225:22ff:fe0d:c22a/64 scope link valid_lft forever preferred_lft forever Any clue? Best regards, Rafal Radecki. 2012/6/25 Gordon Messmer yiny...@eburg.com: On 06/25/2012 05:22 AM, Rafał Radecki wrote: Do you see an error in my configuration? Why is 10.20.0.108 not available? Not immediately, but check the output of the 'ip' tools. ifconfig and route are deprecated: ip route show ip addr show Finally, see if there's any incoming traffic on the tagged interface: tcpdump -n -i eth0.20 ... while you ping the assigned address. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 bridging problem.
tcpdump -n -i eth0.20 shows that there is no traffic when I try to ping 10.20.0.108. Best regards, R. 2012/6/26 Rafał Radecki radecki.ra...@gmail.com: ip route show 192.168.2.0/24 dev vmbr0 proto kernel scope link src 192.168.2.203 193.218.152.0/24 dev vmbr0 proto kernel scope link src 193.218.152.219 10.20.0.0/16 dev vmbr20 proto kernel scope link src 10.20.0.108 169.254.0.0/16 dev vmbr0 scope link metric 1003 169.254.0.0/16 dev vmbr20 scope link metric 1006 default via 193.218.152.1 dev vmbr0 ip addr show 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:25:22:0d:c2:2a brd ff:ff:ff:ff:ff:ff inet6 fe80::225:22ff:fe0d:c22a/64 scope link valid_lft forever preferred_lft forever 3: vmbr0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether 00:25:22:0d:c2:2a brd ff:ff:ff:ff:ff:ff inet 193.218.152.219/24 brd 193.218.152.255 scope global vmbr0 inet 192.168.2.203/24 brd 192.168.2.255 scope global vmbr0:1 inet6 fe80::225:22ff:fe0d:c22a/64 scope link valid_lft forever preferred_lft forever 4: venet0: BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/void inet6 fe80::1/128 scope link valid_lft forever preferred_lft forever 5: eth0.20@eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UP link/ether 00:25:22:0d:c2:2a brd ff:ff:ff:ff:ff:ff inet6 fe80::225:22ff:fe0d:c22a/64 scope link valid_lft forever preferred_lft forever 6: vmbr20: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether 00:25:22:0d:c2:2a brd ff:ff:ff:ff:ff:ff inet 10.20.0.108/16 brd 10.20.255.255 scope global vmbr20 inet6 fe80::225:22ff:fe0d:c22a/64 scope link valid_lft forever preferred_lft forever Any clue? Best regards, Rafal Radecki. 2012/6/25 Gordon Messmer yiny...@eburg.com: On 06/25/2012 05:22 AM, Rafał Radecki wrote: Do you see an error in my configuration? Why is 10.20.0.108 not available? Not immediately, but check the output of the 'ip' tools. ifconfig and route are deprecated: ip route show ip addr show Finally, see if there's any incoming traffic on the tagged interface: tcpdump -n -i eth0.20 ... while you ping the assigned address. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 bridging problem.
On 06/26/12 12:47 AM, Rafał Radecki wrote: tcpdump -n -i eth0.20 shows that there is no traffic when I try to ping 10.20.0.108. try just tcpdump -n -i eth0 I am not sure you can packet sniff a virtual interface, more likely you can only sniff an actual physical interface. -- john r pierceN 37, W 122 santa cruz ca mid-left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 bridging problem.
tcpdump -n -i eth0 icmp and src host 10.20.0.98 does not give any results when ping is invoked. 2012/6/26 John R Pierce pie...@hogranch.com: On 06/26/12 12:47 AM, Rafał Radecki wrote: tcpdump -n -i eth0.20 shows that there is no traffic when I try to ping 10.20.0.108. try just tcpdump -n -i eth0 I am not sure you can packet sniff a virtual interface, more likely you can only sniff an actual physical interface. -- john r pierce N 37, W 122 santa cruz ca mid-left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 bridging problem.
On 06/26/2012 12:02 AM, Rafał Radecki wrote: Any clue? Are you absolutely sure that the switch port connected to eth0 is configured to deliver tagged packets for VLAN 20 (and that the ping source is also on that VLAN)? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 bridging problem.
On 06/26/2012 08:51 AM, Gordon Messmer wrote: Are you absolutely sure that the switch port connected to eth0 is configured to deliver tagged packets for VLAN 20 (and that the ping source is also on that VLAN)? ...and I should follow that up with: If you create a tagged ethernet interface on this system, with NO BRIDGES AT ALL, does the tagged interface work as expected? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 bridging problem. - semi-unrelated
Rafał Radecki wrote: Hi all. I have currently an OpenVZ server: uname -a Linux vader8.superhost.pl 2.6.32-042stab055.16 #1 SMP Fri Jun 8 19:22:28 MSD 2012 x86_64 x86_64 x86_64 GNU/Linux cat /etc/redhat-release CentOS release 6.2 (Final) snip I don't even remember that kernel for 6.2. The last five or six are all 2.6.32-220.x; before that was a 32-118, and I *think* it started with -76 (correct me if I'm wrong, folks.) mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 bridging problem.
On 06/25/2012 05:22 AM, Rafał Radecki wrote: Do you see an error in my configuration? Why is 10.20.0.108 not available? Not immediately, but check the output of the 'ip' tools. ifconfig and route are deprecated: ip route show ip addr show Finally, see if there's any incoming traffic on the tagged interface: tcpdump -n -i eth0.20 ... while you ping the assigned address. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos and Bridging
On Sat, Nov 27, 2010 at 6:23 AM, Nico Kadel-Garcia nka...@gmail.com wrote: On Fri, Nov 26, 2010 at 3:00 PM, Alan Hodgson ahodg...@simkin.ca wrote: On November 26, 2010 11:25:06 am Nico Kadel-Garcia wrote: KVM, itself, was unusable in my testing due to the bridged network mishandling and its complete lack of a concept of failover for network issues, particularly pair bonding for the server itself. PXE for the clients was unusable, and it ran like a dyslexic on too many opiates, slow, twitchy, and unpredicatable. The UI in RHEL 5/CentOS 5 is definitely very limited, but KVM does work with all these things under the hood. In particular KVM seems to run fine on top of a simple host bridge, which can in turn rely on a bonded interface. I have had no problems with boot support, although I confess I don't use PXE - DHCP and kickstart over the LAN work fine, though. It is not merely limited. PXE is very common for server installations of brand new hardware, or for remote KVM managed hardware, to avoid having to pop a CD in it. It's well undertood, and I got nowhere, even with it for KVM. (VMWare and Xen worked fine.) interesting. I have a working home lab with KVM and I bootstrap all my vm's from pxe, both win and lin. So I know it works fine. Not managed from the virtual machine manager, though. Next year I will be evaluating it, and it has better support pxe :) -- natxo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos and Bridging
On Friday 26 November 2010 21:47, Scott Robbins wrote: http://wiki.centos.org/HowTos/KVM It has couple of points the OP may need to know. One is that NetworkManager needs to be disabled. The other is how to handle iptables (OP disable it while troubleshooting). Ah, aikawarazu, good point. Not using NetworkManager--to be honest, I find it causes more problems than it solves, I was't aware of that. Nor do I. I prefer to configure my system for the CLI. (The wiki article does mention additions to iptables.) Nice. Will have to take a look at this one too. Oh, thnx for your input. -- Regards Robert Linux The adventure of a life time. Linux User #296285 Get Counted http://counter.li.org/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos and Bridging
On Fri, Nov 26, 2010 at 2:15 PM, Robert Spangler mli...@zoominternet.net wrote: Hello, Presently I am running CentOS release 5.5 (Final). I am looking to setup bridging as I would like to setup some KVM virtual hosts on my system as a Time to test if ping works: ~ $ ping -c3 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted Did you remember to brctl addif the regular interfaces? -- Eduardo Grosclaude Universidad Nacional del Comahue Neuquen, Argentina ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos and Bridging
On Fri, Nov 26, 2010 at 9:15 AM, Robert Spangler mli...@zoominternet.net wrote: Hello, Presently I am running CentOS release 5.5 (Final). I am looking to setup bridging as I would like to setup some KVM virtual hosts on my system as a test lab. I am following the the instruction at this site http://tldp.org/HOWTO/BRIDGE-STP-HOWTO/index.html (snip) Everything is back to normal. I cannot figure out what am I missing here? Interfaces and routing look to be setup correctly. Is there something else I need to be looking at? I recommend you look at the documentaion available from docs.redhat.com. For setting up bridged networking, see: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html-single/Virtualization/index.html#sect-Virtualization-Network_Configuration-Bridged_networking_with_libvirt Akemi ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos and Bridging
At Fri, 26 Nov 2010 12:15:51 -0500 CentOS mailing list centos@centos.org wrote: Hello, Presently I am running CentOS release 5.5 (Final). I am looking to setup bridging as I would like to setup some KVM virtual hosts on my system as a test lab. I am following the the instruction at this site http://tldp.org/HOWTO/BRIDGE-STP-HOWTO/index.html but I cannot figure out where I am going wrong and would be thankful if someone could point me in the right direction. Here is what I have done: Check bridge information with the following: ~ $ modprobe -v bridge No issues or errors ~ $ cat /proc/modules | grep bridge bidge 91889 0 - Live 0x89247000 Check to ensure forwarding is turned on: ~ $ cat /proc/sys/net/ipv4/ip_forward 1 Checked that my interface are up and running (Was sure of this but did the check anyway): ~ $ ifconfig eth0 Link encap:Ethernet HWaddr 48:5B:39:2A:07:D5 inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::4a5b:39ff:fe2a:7d5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1059 errors:0 dropped:0 overruns:0 frame:0 TX packets:1080 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:454226 (443.5 KiB) TX bytes:120584 (117.7 KiB) Interrupt:90 Base address:0x8400 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:92 errors:0 dropped:0 overruns:0 frame:0 TX packets:92 errors:0 dropped:0 overruns:0 carrier:0[Thu Nov 25 So now I begin to create the bridge form CLI as I want to make sure everything works before committing it to the config: brctl addbr br0 ifconfig eth0 down ifconfig br0 192.168.1.100 up ifconfig eth0 0.0.0.0 up brctl addif br0 eth0 You need to add the physical interface(s) to the bridge interface. You can set this up to go automagically like this: sauron.deepsoft.com% cat /etc/sysconfig/network-scripts/ifcfg-eth0 # nVidia Corporation MCP77 Ethernet DEVICE=eth0 BOOTPROTO=static HWADDR=00:19:66:D6:ED:93 ONBOOT=yes BRIDGE=br0 sauron.deepsoft.com% cat /etc/sysconfig/network-scripts/ifcfg-br0 DEVICE=br0 TYPE=Bridge BOOTPROTO=static BROADCAST=192.168.250.255 IPADDR=192.168.250.1 NETMASK=255.255.255.0 NETWORK=192.168.250.0 ONBOOT=yes (change as needed to match your interaces and ipaddresses, etc.) route add default gw 192.168.1.254 I check my interfaces and routing: ~ $ ifconfig br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:398 (398.0 b) eth0 Link encap:Ethernet HWaddr 48:5B:39:2A:07:D5 inet6 addr: fe80::4a5b:39ff:fe2a:7d5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:64662 errors:0 dropped:0 overruns:0 frame:0 TX packets:63301 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:17699194 (16.8 MiB) TX bytes:7958063 (7.5 MiB) Interrupt:90 Base address:0x8400 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:211 errors:0 dropped:0 overruns:0 frame:0 TX packets:211 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:17346 (16.9 KiB) TX bytes:17346 (16.9 KiB) ~ $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 00 br0 0.0.0.0 192.168.1.254 0.0.0.0 UG0 00 br0 Time to test if ping works: ~ $ ping -c3 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted --- 192.168.1.254 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2000ms I know the firewall is causing this issue so I stop the firewall: ~ $ service iptables stop Flushing firewall rules: [ OK ] Setting chains to policy ACCEPT: nat filter[ OK ] Unloading iptables modules:
Re: [CentOS] Centos and Bridging
On Friday 26 November 2010 12:22, Eduardo Grosclaude wrote: Presently I am running CentOS release 5.5 (Final). I am looking to setup bridging as I would like to setup some KVM virtual hosts on my system as a Time to test if ping works: ~ $ ping -c3 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted Did you remember to brctl addif the regular interfaces? Nope, that is what I had forgotten. Thnx -- Regards Robert Linux The adventure of a life time. Linux User #296285 Get Counted http://counter.li.org/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos and Bridging
On Friday 26 November 2010 12:27, Akemi Yagi wrote: I recommend you look at the documentaion available from docs.redhat.com. For setting up bridged networking, see: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html-single/Vi rtualization/index.html#sect-Virtualization-Network_Configuration-Bridged_ne tworking_with_libvirt Thank you kindly for the link. I have some reading a head of me. -- Regards Robert Linux The adventure of a life time. Linux User #296285 Get Counted http://counter.li.org/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos and Bridging
On Friday 26 November 2010 12:28, Robert Heller wrote: works before committing it to the config: brctl addbr br0 ifconfig eth0 down ifconfig br0 192.168.1.100 up ifconfig eth0 0.0.0.0 up brctl addif br0 eth0 You need to add the physical interface(s) to the bridge interface. Yes, thank you for this information. This is the set I had missed. You can set this up to go automagically like this: sauron.deepsoft.com% cat /etc/sysconfig/network-scripts/ifcfg-eth0 # nVidia Corporation MCP77 Ethernet DEVICE=eth0 BOOTPROTO=static HWADDR=00:19:66:D6:ED:93 ONBOOT=yes BRIDGE=br0 sauron.deepsoft.com% cat /etc/sysconfig/network-scripts/ifcfg-br0 DEVICE=br0 TYPE=Bridge BOOTPROTO=static BROADCAST=192.168.250.255 IPADDR=192.168.250.1 NETMASK=255.255.255.0 NETWORK=192.168.250.0 ONBOOT=yes Thnx again for this information. -- Regards Robert Linux The adventure of a life time. Linux User #296285 Get Counted http://counter.li.org/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos and Bridging
On Fri, Nov 26, 2010 at 12:15 PM, Robert Spangler mli...@zoominternet.net wrote: Hello, Presently I am running CentOS release 5.5 (Final). I am looking to setup bridging as I would like to setup some KVM virtual hosts on my system as a test lab. I am following the the instruction at this site Don't bother. The Qemu based tools in libvirt, and their implementation in virt-manager, should be taken out back and forced to read Eric Raymond's screed on open source interfaces (The Luxury of Ignorance). Compatibility with arbitrary virtualization suites is not your friend when it's done that badly. Simple operations, like set up two disks at first setup, are not possible from the GUI. This is one among numerous utilities available from the command line setup tool that are not accessible from the GUI: that's just a failure of GUI design. KVM, itself, was unusable in my testing due to the bridged network mishandling and its complete lack of a concept of failover for network issues, particularly pair bonding for the server itself. PXE for the clients was unusable, and it ran like a dyslexic on too many opiates, slow, twitchy, and unpredicatable. VMWare works well, even the free personal versions, and Xen used to work well (although its purchase by Citrix has me concerned, I've not played with it in 2 years now, and I'm very unhappy with libvirt.) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos and Bridging
On November 26, 2010 11:25:06 am Nico Kadel-Garcia wrote: KVM, itself, was unusable in my testing due to the bridged network mishandling and its complete lack of a concept of failover for network issues, particularly pair bonding for the server itself. PXE for the clients was unusable, and it ran like a dyslexic on too many opiates, slow, twitchy, and unpredicatable. The UI in RHEL 5/CentOS 5 is definitely very limited, but KVM does work with all these things under the hood. In particular KVM seems to run fine on top of a simple host bridge, which can in turn rely on a bonded interface. I have had no problems with boot support, although I confess I don't use PXE - DHCP and kickstart over the LAN work fine, though. I do hope the interface implementation in RHEL 6 will be much more usable. I don't mind doing things in XML files and command lines, but lots of people do. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos and Bridging
On Fri, Nov 26, 2010 at 02:12:04PM -0500, Robert Spangler wrote: On Friday 26 November 2010 12:27, Akemi Yagi wrote: I recommend you look at the documentaion available from docs.redhat.com. For setting up bridged networking, see: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html-single/Vi rtualization/index.html#sect-Virtualization-Network_Configuration-Bridged_ne tworking_with_libvirt Thank you kindly for the link. I have some reading a head of me. Much as I respect Akemi san, I would say, don't bother. It's the usual poorly written RH documentation. In contrast, there is the CentOS wiki, written by someone who actually knows something about writing documentation that people can understand. Ohwait, it's me. Actually, the KVM wiki article is very out of date, but the section on bridging is applicable. The RH docs were so bad, that I still had to go back to my own article. http://wiki.centos.org/HowTos/KVM -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos and Bridging
On Fri, Nov 26, 2010 at 5:16 PM, Scott Robbins scot...@nyc.rr.com wrote: On Fri, Nov 26, 2010 at 02:12:04PM -0500, Robert Spangler wrote: On Friday 26 November 2010 12:27, Akemi Yagi wrote: I recommend you look at the documentaion available from docs.redhat.com. For setting up bridged networking, see: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html-single/Virtualization/index.html#sect-Virtualization-Network_Configuration-Bridged_networking_with_libvirt Much as I respect Akemi san, I would say, don't bother. It's the usual poorly written RH documentation. In contrast, there is the CentOS wiki, written by someone who actually knows something about writing documentation that people can understand. Ohwait, it's me. Actually, the KVM wiki article is very out of date, but the section on bridging is applicable. The RH docs were so bad, that I still had to go back to my own article. http://wiki.centos.org/HowTos/KVM Mmm? I may not be the biggest fan of the Red Hat docs but I have to give a good score to that one about bridged networking. I followed the instructions in there and had no problem setting it up on my KVM hosts. It has couple of points the OP may need to know. One is that NetworkManager needs to be disabled. The other is how to handle iptables (OP disable it while troubleshooting). Akemi ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos and Bridging
On Fri, Nov 26, 2010 at 06:09:26PM -0800, Akemi Yagi wrote: On Fri, Nov 26, 2010 at 5:16 PM, Scott Robbins scot...@nyc.rr.com wrote: http://wiki.centos.org/HowTos/KVM Mmm? I may not be the biggest fan of the Red Hat docs but I have to give a good score to that one about bridged networking. I followed the instructions in there and had no problem setting it up on my KVM hosts. It has couple of points the OP may need to know. One is that NetworkManager needs to be disabled. The other is how to handle iptables (OP disable it while troubleshooting). Ah, aikawarazu, good point. Not using NetworkManager--to be honest, I find it causes more problems than it solves, I was't aware of that. (The wiki article does mention additions to iptables.) Regrettably, however, I've found KVM to be somewhat of a disappointment. (My own personal experience.) For any workstation, I'm finding VMware-player to be the new contender, running guests faster than the later VirtualBoxes and/or KVM, and for serious production, I -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos and Bridging
On Fri, Nov 26, 2010 at 3:00 PM, Alan Hodgson ahodg...@simkin.ca wrote: On November 26, 2010 11:25:06 am Nico Kadel-Garcia wrote: KVM, itself, was unusable in my testing due to the bridged network mishandling and its complete lack of a concept of failover for network issues, particularly pair bonding for the server itself. PXE for the clients was unusable, and it ran like a dyslexic on too many opiates, slow, twitchy, and unpredicatable. The UI in RHEL 5/CentOS 5 is definitely very limited, but KVM does work with all these things under the hood. In particular KVM seems to run fine on top of a simple host bridge, which can in turn rely on a bonded interface. I have had no problems with boot support, although I confess I don't use PXE - DHCP and kickstart over the LAN work fine, though. It is not merely limited. PXE is very common for server installations of brand new hardware, or for remote KVM managed hardware, to avoid having to pop a CD in it. It's well undertood, and I got nowhere, even with it for KVM. (VMWare and Xen worked fine.) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
