Re: [CentOS-virt] firewall best practice on dom-0
John Thomas wrote on Sun, 13 Jul 2008 07:44:14 -0700: but I think everything is the same, as if you have physical machines. It's not, see my remark about forwarding ;-) Maybe you need forwarding on your physical machines, I do not ;-) Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] xen 3.2
Any ideal when 3.2 xen will be avail for centos? Thanks! ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Windows HVM VMs - speed needed...
Hi All, I was hoping to run a Windows 2003 server in production on Centos 5.2 however the performance isn't very good. The host is Centos 5.2 64 bit. I did some file transfers and I'm seeing about 12Mb/s on a Windows 2003 VM and about 8Mb/s on a Windows 2003 32 bit VM. Numbers are measured using the builtin Windows 2003 server networking monitor (Press Ctrl Alt Del in Windows and go to the Windows tab). The server is an IBM xServe about a year old and the VMs are running in LVM partitions. Switches are Cisco Gigabit. So the hardware for server performance and network performance are not a limiting factor - I understand that the results I'm seeing are typical without running paravirtualized drivers in Windows. Just wanted to ask what the options are to get things going faster. I believe the choices are:- - Pay the dollars for a RedHat subscription which includes paravitualized drives for Windows - Install the LGPL PV drivers (don't want to do this, these are production machines and even up to a few months ago I'm seeing reports of VM corruption in the list. It would appear that the LGPL PV drivers are not at production standard yet) - Pay for an alternative Xen distribution, such as Xen's commercial product. Can someone confirm, have I covered all the bases? Thanks Stephen ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Need kernel-debuginfo-2.6.9-67.0.20.EL.x86_64.rpm
Short story: Would it be possible to get kernel-debuginfo-2.6.9-67.0.20.EL.x86_64.rpm on di.c.o? I have a need to run crash on a 2.6.9-67.0.20.ELxenU xm dump-core. Long story: Two Dell 6950 (now called R905, 4 Dual-Core AMD Opteron 8200 series) heartbeat/drbd nodes running the stock CentOS 5.2 Dom0. The domU's are the only resources in heartbeat. Dom1 is a perfectly running, updated, CentOS 5.2 Apache/MySQL/Samba server (2.6.18-92.1.6.el5xen). It's xen config: name = guinan bootloader = /usr/bin/pygrub uuid = 8fa0ac9e-fe28-17f5-6a72-07f84b4daa24 memory = 4097 vcpus = 6 on_poweroff = destroy on_reboot = restart on_crash = restart vfb = [ type=vnc,vncunused=1,keymap=en-us ] disk = [ phy:/dev/drbd1,xvda,w, phy:/dev/drbd2,xvdb,w ] vif = [ mac=00:16:3e:68:16:5d,bridge=xenbr0, bridge=xenbr1 ] Dom2 is a CentOS 4.6 software development and database server (2.6.9-67.0.20.ELxenU). Every so often, could be several hours or several days, it just hangs, locks up, becomes unresponsive. Nothing to the console. Nothing logged. When it gets to this point, the only recourse is an xm destroy. It's occurred with every combination of Dom0/DomU. The hardware of both servers checks out OK. The only sign of life, on Dom2's current Dom0, xentop shows CPU usage, and at a high percent, at that: xentop - 12:02:36 Xen 3.1.2-92.1.6.el5 2 domains: 2 running, 0 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown Mem: 16775712k total, 11629904k used, 5145808k freeCPUs: 8 @ 2194MHz NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR SSID Domain-0 -r 508911.5 9013525.4 no limit n/a 84 17720114 1876571300000 monolith -r 965342 599.2 10486632 62.5 10486784 62.5 62 332672635 3017828520 15805538 60805435 0 I've experimented with various xen config's. Currently it's this: name = monolith uuid = 283746fa-c708-cfa0-f5df-cad6abea568e memory = 10241 vcpus = 4 bootloader = /usr/bin/pygrub on_poweroff = destroy on_reboot = restart on_crash = restart vfb = [ type=vnc,vncunused=1,keymap=en-us ] disk = [ phy:/dev/drbd3,xvda,w, phy:/dev/drbd4,xvdb,w ] vif = [ mac=00:16:3e:08:8d:c3,bridge=xenbr0, bridge=xenbr1 ] Previously, I'd tried adjusting memory, but the problem resurfaced. Currently, I've gone from 6 vcpus to the 4 shown above in the hopes that stabilizes it. I'm at wits end. I've committed these machines to production status, so this instability has everyone kind of on edge, and wanting to go back to bare metal... jerry -- Your life is trite and jaded, boring and confiscated. - Twisted Sister ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] xen 3.2
On Mon, Jul 14, 2008 at 5:04 PM, Justin Lim [EMAIL PROTECTED] wrote: Any ideal when 3.2 xen will be avail for centos? When the upstream distribution provides it. I am not sure if it is on their roadmap. Of course, you could also use Xen 3.2 from XenSource, but that's not supported here. Take care, Daniel ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Need kernel-debuginfo-2.6.9-67.0.20.EL.x86_64.rpm
Hi, On Mon, Jul 14, 2008 at 10:49 PM, Jerry Amundson [EMAIL PROTECTED] wrote: Short story: Would it be possible to get kernel-debuginfo-2.6.9-67.0.20.EL.x86_64.rpm on di.c.o? I have a need to run crash on a 2.6.9-67.0.20.ELxenU xm dump-core. Debuginfo packages are available from: http://debuginfo.centos.org/ Take care, Daniel ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Need kernel-debuginfo-2.6.9-67.0.20.EL.x86_64.rpm
On Mon, Jul 14, 2008 at 2:49 PM, Daniel de Kok [EMAIL PROTECTED] wrote: Hi, On Mon, Jul 14, 2008 at 10:49 PM, Jerry Amundson [EMAIL PROTECTED] wrote: Short story: Would it be possible to get kernel-debuginfo-2.6.9-67.0.20.EL.x86_64.rpm on di.c.o? I have a need to run crash on a 2.6.9-67.0.20.ELxenU xm dump-core. Debuginfo packages are available from: http://debuginfo.centos.org/ I think it will become available once Johnny uploads it :-D The i686 rpm seems to be there but... Akemi ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] xen 3.2
On Mon, Jul 14, 2008 at 2:46 PM, Daniel de Kok [EMAIL PROTECTED] wrote: On Mon, Jul 14, 2008 at 5:04 PM, Justin Lim [EMAIL PROTECTED] wrote: Any ideal when 3.2 xen will be avail for centos? When the upstream distribution provides it. I am not sure if it is on their roadmap. Of course, you could also use Xen 3.2 from XenSource, but that's not supported here. Take care, Daniel ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt I was at a recent Linux convention and it seemed very likely that Xen is no longer Redhat's priority at all and would love to put KVM in it's place. The Redhat rep was very adamant about KVMs superiority over Xen and the amount of unnecessary work to integrate Xen into their kernels. Some day when KVM will actually do what Xen does (and do it reliably!) Xen may not be an easy option. Grant ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Windows HVM VMs - speed needed...
On Mon, Jul 14, 2008 at 3:33 PM, Stephen [EMAIL PROTECTED] wrote: Hi All, I was hoping to run a Windows 2003 server in production on Centos 5.2 however the performance isn't very good. The host is Centos 5.2 64 bit. I did some file transfers and I'm seeing about 12Mb/s on a Windows 2003 VM and about 8Mb/s on a Windows 2003 32 bit VM. Numbers are measured using the builtin Windows 2003 server networking monitor (Press Ctrl Alt Del in Windows and go to the Windows tab). The server is an IBM xServe about a year old and the VMs are running in LVM partitions. Switches are Cisco Gigabit. So the hardware for server performance and network performance are not a limiting factor - I understand that the results I'm seeing are typical without running paravirtualized drivers in Windows. Just wanted to ask what the options are to get things going faster. I believe the choices are:- - Pay the dollars for a RedHat subscription which includes paravitualized drives for Windows - Install the LGPL PV drivers (don't want to do this, these are production machines and even up to a few months ago I'm seeing reports of VM corruption in the list. It would appear that the LGPL PV drivers are not at production standard yet) - Pay for an alternative Xen distribution, such as Xen's commercial product. Can someone confirm, have I covered all the bases? I have heard of one other option: Halsign TurboGate Tools http://www.halsign.com/ I haven't tried them personally, but I have seen them announced on the Xen mailing lists. Todd -- Todd Deshane http://todddeshane.net check out our book: http://runningxen.com ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
