virt

virt@lists.centos.org

1608 discussions

Vmware Server 2 and KVM....
by Tom Bishop 17 Aug '10

17 Aug '10

I am finally starting to pull the plug on vmware 2 and want to start migrating to KVM, what I would like to know and I have searched but not found anything conclusive. Is it possible to run Vmware server 2 and KVM at the same time, I am running Centos 5.5 x64 on a 16 core 32g memory machine....the reason I would like to do this is that it would allow me to convert the vm's one at a time and do it in more of a phased approach, otherwise I may have to try to do it all at the same time....I dont have many VM's maybe 6 or 7 but would be nice if I could do them one at a time....Thanks in advance.... :)

5 12

Jack Van Ham is out of the office.
by jack.vanham＠agfa.com 16 Aug '10

16 Aug '10

I will be out of the office starting 08/16/2010 and will not return until 08/20/2010. I will be out of the office (training) for the week of AUG 16 to AUG 20, 2010. I will check email as often as I can. For urgent matter, please call: 519-574-7707 (cell), and leave me a message if I do not answer, and I'll get back to you.

1 0

IP aliases from a QEMU/KVM guest
by Mathieu Baudier 13 Aug '10

13 Aug '10

Hello, I'm trying to set up IP aliases within a QEMU/KVM guest on CentOS 5.5 x86_64, going through a bridged virtualized interface. The virtualized interface in the guest is configured as follow: # ifcfg-eth1 DEVICE=eth1 BOOTPROTO=none PEERDNS=yes GATEWAY=IP.OF.HOST.GATEWAY HWADDR=11:11:11:11:11:11 IPADDR=IP.OF.GUEST.ETH1 NETMASK=255.255.255.255 ONBOOT=yes ARP=yes USERCTL=no IPV6INIT=no # route-eth1 IP.OF.HOST.GATEWAY dev eth1 default via IP.OF.HOST.GATEWAY dev eth1 This is the configuration recommended by the provider (OVH) after a virtual MAC address has been allocated for IP.OF.GUEST.ETH1: http://help.ovh.com/BridgeClient It works fine for virtual interfaces added via libvirt/QEMU. But when I try to configure an IP alias on another IP address aliasing a virtualized interface, as per the instructions from http://help.ovh.co.uk/IpAlias (and after assigning it a virtual mac just like for eth1) : # ifcfg-eth1:1 DEVICE=eth1:1 BOOTPROTO=none PEERDNS=yes GATEWAY=IP.OF.HOST.GATEWAY HWADDR=22:22:22:22:22:22 IPADDR=IP.OF.GUEST.ETH1:1 NETMASK=255.255.255.255 ONBOOT=yes ARP=yes USERCTL=no IPV6INIT=no I get the following error when restarting the network: SIOCADDRT: Network is unreachable and IP.OF.GUEST.ETH1:1 is: - pingable from the same guest - not pingable from other guests by the same provider - not pingable from outside Setting BOOTPROTO=static or commenting out #GATEWAY=IP.OF.HOST.GATEWAY or setting: NETMASK=255.255.255.252 (the IP block was a /30, but I don't think that has something to do here) did not change the behavior. I'll be interested to hear from experiences with setting IP alias from within a guest. Maybe my problem is due to the configuration of the provider network and it is actually impossible to use IP aliases on virtualized interfaces. Any opinion/idea welcome! Mathieu

4 5

IP based VirtualHost: IP aliases vs. additional virtual interfaces
by Mathieu Baudier 10 Aug '10

10 Aug '10

Hi, I have a virtualized infrastructure based on KVM/QEMU with CentOS 5.5 x86_64 hosts and guests, using bridge networking. I want to set up IP based VirtualHosts in Apache (because they will use SSL) and I have ordered an IP block. Now, in order to have the IPs available on some guests, I'm wondering whether I should: 1 - add additional virtual interfaces or 2 - set up IP aliases (eth0:1, etc.) in the guests I imagine that (1) would be faster and more efficient (but that's a guts feeling), and it feels cleaner. But with (2), I just need to restart the network in order to add new IPs (there won't be that many: like around 10 in the next few months), insteead of restarting the whole guest. Are there any best practices for adding IP-addresses to virtualized guests? Thanks in advance for your insights! Mathieu

3 4

Matthias Lorch ist außer Haus.
by matthias.lorch＠kzvrlp.de 10 Aug '10

10 Aug '10

Ich werde ab 09.08.2010 nicht im Büro sein. Ich kehre zurück am 30.08.2010. Bitte wenden Sie sich in dringenden Fällen an Herrn Roth, 0261 / 9120 - 258 Vielen Dank Gruß M.Lorch

1 0

CentOS, Xen and VLANs
by Jared Ravetch 10 Aug '10

10 Aug '10

I ran into an issue when trying to create VMs in CentOS 5.5 with VLANs. My setup is as follows: -CentOS 5.5 x64 xen kernel -LVM for storage -Kickstart file hosted on apache in /var/www/html/ -VM start file in /etc/xen/ -VLAN100 interface with public IP, VLAN200 interface with private IP My vm start file is as follows: kernel = "/boot/vm-inst/vmlinuz" ramdisk = "/boot/vm-inst/initrd.img" name = "vm1-inst" memory = 1000 disk = [ 'phy:/dev/VolGroup01/vm01,xvda,w', ] vif = ['bridge=virbr0', ] vcpus = 1 ip = '172.16.1.100' netmask = '255.255.255.0' gateway = '172.16.1.1' extra = "text ks=http://172.16.1.155/vm-inst1-ks.cfg ip=172.16.1.100 netmask=255.255.255.0 gateway=172.16.1.1 dns=172.16.1.200" To start the install I run: xm create -c vm1-inst The CentOS installer finds the kernel and ramdisk files, configures the IP, then hangs for a while until it states it cannot find the kickstart file. I have to then have to exit the console and shutdown the vm To remove any issues with the kickstart file, I tried just using vm-install --prompt to create the VM and pointing to a FTP site with the install files. The CentOS installer starts, I configure the IP using a static IP, but then the it complains it cannot find any files in the FTP site. Finally, I tried using the CentOS DVD ISO as the install media for the VM. The installer starts, but then complains it does not have the drivers to load the media. I googled and found this is a limitation of CentOS when creating VMs. Has anyone had experience getting the installer over VLANs to work with a network install? Is there another way around this issue? Thanks and Regards, Jared

1 0

working config for xen which would transfer a serial interface
by Manuel Wolfshant 06 Aug '10

06 Aug '10

Hello Can anyone share a known working config for xen which would transfer a serial interface ( add-on card preferably, mine uses e880-e887 : 0000:03:05.0 / ec00-ec07 : 0000:03:05.0 ) to a DomU ? I've been trying with the stock packages from Centos 5.5 ( fully updated) and also with gitco's 3.4.3 but after 2 days of googling and testing we still fail to access the serial interface from DomU. No matter what we've tried, - in DomU there is no reference to any kind of serial ports in /proc/{interrupts,ioports} - the test program which accesses ttyS0 fails ( it works just fine in dom0) even after manually loading parport_serial in DomU /dev/ttyS{0..3} do get created by default, if that matters. Here is the content of the config file, after the last attempt (which uses gitco's xen, but we failed similarly with the stock packages): name = "testr" uuid = "57baf51a-e293-fa35-9f2e-056a1c0e322a" maxmem = 512 memory = 512 vcpus = 1 bootloader = "/usr/bin/pygrub" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vfb = [ "type=vnc,vncunused=1,keymap=en-us" ] disk = [ "tap:aio:/var/lib/xen/images/testr,xvda,w" ] vif = [ "mac=00:16:36:0c:aa:1a,bridge=xenbr0,script=vif-bridge" ] irq = [11 ] ioports = [ "ec00-ec07","e080-e08f" ] // we also tried to pass all the IO ports referenced in lspci -vvv [root@Dom0]#lspci -vvv 03:05.0 Communication controller: NetMos Technology PCI 9835 Multi-I/O Controller (rev 01) Subsystem: LSI Logic / Symbios Logic 1P2S Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at ec00 [size=8] Region 1: I/O ports at e880 [size=8] Region 2: I/O ports at e800 [size=8] Region 3: I/O ports at e480 [size=8] Region 4: I/O ports at e400 [size=8] Region 5: I/O ports at e080 [size=16] [root@Dom0 ~]# dmesg | grep ttyS [root@Dom0 ~]# cat /etc/modprobe.d/blacklist #[...] blacklist 8250 blacklist 8250_pnp blacklist serial_core blacklist parport_serial blacklist 8250_pci [root@Dom0 ~]# grep xen /etc/grub.conf title CentOS (2.6.18-194.el5xen) kernel /xen.gz-3.4.3 module /vmlinuz-2.6.18-194.el5xen ro root=/dev/VolGroup00/LogVol00 module /initrd-2.6.18-194.el5xen.img title CentOS (2.6.18-194.8.1.el5xen) kernel /xen.gz-3.4.3 module /vmlinuz-2.6.18-194.8.1.el5xen ro root=/dev/VolGroup00/LogVol00 xencons=off module /initrd-2.6.18-194.8.1.el5xen.img [root@Dom0 ~]# uname -a Linux Dom0 3 2.6.18-194.8.1.el5xen #1 SMP Thu Jul 1 19:41:05 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux sniff from the boot messages in tge DomU: XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/ioports/0 XENBUS: Device with no driver: device/ioports/1 XENBUS: Device with no driver: device/ioports/2 XENBUS: Device with no driver: device/ioports/3 XENBUS: Device with no driver: device/ioports/4 XENBUS: Device with no driver: device/ioports/5 XENBUS: Device with no driver: device/irq/0 XENBUS: Device with no driver: device/console/0 [root@DomU ~]# cat /proc/interrupts CPU0 256: 7433 Dynamic-irq timer0 257: 0 Dynamic-irq resched0 258: 0 Dynamic-irq callfunc0 259: 554 Dynamic-irq xenbus 260: 705 Dynamic-irq xencons 261: 802 Dynamic-irq xenfb 262: 0 Dynamic-irq xenkbd 263: 6607 Dynamic-irq blkif 264: 8959 Dynamic-irq eth0 NMI: 0 LOC: 0 ERR: 0 MIS: 0 [root@DomU ~]# cat /proc/ioports 0000-001f : dma1 0020-0021 : pic1 0040-0043 : timer0 0050-0053 : timer1 0060-0060 : keyboard 0064-0064 : keyboard 0080-008f : dma page reg 00a0-00a1 : pic2 00c0-00df : dma2 00f0-00ff : fpu [root@DomU ~]# lsmod Module Size Used by 8250_pnp 43969 0 parport_serial 41153 0 8250_pci 56257 1 parport_serial 8250 86057 2 8250_pnp,8250_pci serial_core 56385 1 8250 [...] [root@DomU ~]# uname -a Linux DomU 2.6.18-194.8.1.el5xen #1 SMP Thu Jul 1 19:41:05 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux TIA manuel

2 5

Re: [CentOS-virt] Arp Flip Flops make machine inaccessible.
by chaim.rieger＠gmail.com 31 Jul '10

31 Jul '10

Comment out the mac addy from eth1 and try that Sent via BlackBerry from T-Mobile

2 1

Arp Flip Flops make machine inaccessible.
by Ben M. 31 Jul '10

31 Jul '10

CentOS 5.5 Xen "standard" Xen Installation. I have two nics. I just put the second one to DHCP and modified the ifcfg-et01 and so far I am holding, but I am not confident. Prior they were sequential IP Addrs on same subnet. arpwatch has indicated flip flips. I can find no rhyme or reason to predict them. I know I missed I must have missed a step somewhere. I want to keep the traffic pinned to the physical ethXs by their Xen bridge assignation. Segregate traffic. Current working setup: # ifcfg-eth0 # nVidia Corporation MCP55 Ethernet DEVICE=eth0 BOOTPROTO=none #BROADCAST=10.255.255.255 #HWADDR=00:e0:81:d2:0b:36 IPADDR=10.0.0.50 #NETMASK=255.255.255.0 #NETWORK=10.0.0.0 ONBOOT=yes GATEWAY=10.0.0.1 TYPE=Ethernet #ARP=yes IPV6INIT=no #ifcfg-eth1 # nVidia Corporation MCP55 Ethernet DEVICE=eth1 BOOTPROTO=dhcp ONBOOT=yes HWADDR=00:e0:81:d2:0b:37 [root@localdomain ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:E0:81:D2:0B:36 inet addr:10.0.0.50 Bcast:10.255.255.255 Mask:255.0.0.0 inet6 addr: fe80::2e0:81ff:fed2:b36/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:17853 errors:0 dropped:0 overruns:0 frame:0 TX packets:100 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1249977 (1.1 MiB) TX bytes:8043 (7.8 KiB) eth1 Link encap:Ethernet HWaddr 00:E0:81:D2:0B:37 inet addr:10.255.252.22 Bcast:10.255.255.255 Mask:255.0.0.0 inet6 addr: fe80::2e0:81ff:fed2:b37/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8631 errors:0 dropped:0 overruns:0 frame:0 TX packets:13361 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:657672 (642.2 KiB) TX bytes:6476669 (6.1 MiB) lo Link 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:18946 errors:0 dropped:0 overruns:0 frame:0 TX packets:18946 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:7802726 (7.4 MiB) TX bytes:7802726 (7.4 MiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:17887 errors:0 dropped:0 overruns:0 frame:0 TX packets:137 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1253769 (1.1 MiB) TX bytes:11507 (11.2 KiB) Interrupt:252 Base address:0xa000 peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:363575 errors:0 dropped:0 overruns:0 frame:0 TX packets:161997 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:500789617 (477.5 MiB) TX bytes:17282884 (16.4 MiB) Interrupt:251 Base address:0xc000 sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 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) tap0 Link encap:Ethernet HWaddr 76:A2:E4:74:CD:79 inet6 addr: fe80::74a2:e4ff:fe74:cd79/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:2652 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 b) TX bytes:449235 (438.7 KiB) tap1 Link encap:Ethernet HWaddr AA:BB:F6:55:59:5E inet6 addr: fe80::a8bb:f6ff:fe55:595e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:8862 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:60 (60.0 b) TX bytes:878033 (857.4 KiB) veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 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) veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 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) vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:100 errors:0 dropped:0 overruns:0 frame:0 TX packets:17853 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8043 (7.8 KiB) TX bytes:1249977 (1.1 MiB) vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:13361 errors:0 dropped:0 overruns:0 frame:0 TX packets:8631 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6476669 (6.1 MiB) TX bytes:657672 (642.2 KiB) vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF 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) vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF 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) 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 NOARP MTU:1500 Metric:1 RX packets:63 errors:0 dropped:0 overruns:0 frame:0 TX packets:8730 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:6847 (6.6 KiB) TX bytes:866585 (846.2 KiB) vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:179 errors:0 dropped:0 overruns:0 frame:0 TX packets:8627 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:15806 (15.4 KiB) TX bytes:857989 (837.8 KiB) vif4.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:148068 errors:0 dropped:0 overruns:0 frame:0 TX packets:357556 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:6980701 (6.6 MiB) TX bytes:500418149 (477.2 MiB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.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:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) virbr1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.100.1 Bcast:192.168.100.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:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:1506 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:163593 (159.7 KiB) TX bytes:0 (0.0 b) xenbr1 Link encap:Ethernet HWaddr 76:A2:E4:74:CD:79 UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:1503 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:161739 (157.9 KiB) TX bytes:0 (0.0 b) [root@river50 ~]# brctl show bridge name bridge id STP enabled interfaces virbr0 8000.000000000000 yes virbr1 8000.000000000000 yes xenbr0 8000.feffffffffff no peth0 vif0.0 xenbr1 8000.76a2e474cd79 no vif4.0 tap0 vif3.0 tap1 vif1.0 peth1 vif0.1 REPLACED in xend-config.sxp # (network-script network-bridge) (network-script my-network-bridge) file: my-network-bridge [root@localdomain ~]# cat /etc/xen/scripts/my-network-bridge #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0 "$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1 IPTABLES (not modified by any action by me) [root@localdomain ~]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps RH-Firewall-1-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere private.ip-address.localhost/24 state RELATED,ESTABLISHED ACCEPT all -- private.ip-address.localhost/24 anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable REJECT all -- anywhere anywhere reject-with icmp-port-unreachable ACCEPT all -- anywhere private.ip-address.localhost/24 state RELATED,ESTABLISHED ACCEPT all -- private.ip-address.localhost/24 anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable REJECT all -- anywhere anywhere reject-with icmp-port-unreachable RH-Firewall-1-INPUT all -- anywhere anywhere ACCEPT all -- private.ip-address.localhost anywhere PHYSDEV match --physdev-in vif1.0 ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif1.0 udp spt:bootpc dpt:bootps ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif3.0 ACCEPT all -- private.ip-address.localhost anywhere PHYSDEV match --physdev-in vif4.0 ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif4.0 udp spt:bootpc dpt:bootps Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain RH-Firewall-1-INPUT (2 references) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT esp -- anywhere anywhere ACCEPT ah -- anywhere anywhere ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns ACCEPT udp -- anywhere anywhere udp dpt:ipp ACCEPT tcp -- anywhere anywhere tcp dpt:ipp ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:5901 ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:smtp REJECT all -- anywhere anywhere reject-with icmp-host-prohibited

1 0

which virtualization platform to choose
by Gilberto Nunes 28 Jul '10

28 Jul '10

Friends I'm in doubt here: which virtualization platform to choose and why? If I have just installed a VM I choose Xen or KVM? And when I have more than 5 or 10 VM's? Please, I need your help to choose right. Thanks -- Gilberto Nunes

7 14

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt