[CentOS-virt] IP aliases of CentOS Guests not accessible running 2.6.18-164.el5xen
Hi all, First of all I am posting this on two lists for a reason, because the issue being reported by me could be because of a change delivered by a Kernel update or due to Xen. I have recently managed to update all Xen Guest domains running CentOS 5.3 to the latest bunch of updates + Kernel. My Xen host also runs the same CentOS 5.3 updated to all recent packages. The Guest images in concern had IP aliases assigned to them. Everything worked until I ran the updates and restarted. Since I have restarted the aliased IP addresses are no longer accessible from the outside world, they can still be accessed from all machines (guest virtual machines) in the subnet (ping, services like http). I have removed all firewall rules to test if that would have effected it without any change (any the fact that I can access them within the subnet proves its not the firewall). Is there anything special I have to do to enable aliasing? May be this is a Xen issue? I am suspecting the Xen host, but not sure how to go about proving this. Any information would be greatly appreciated. My Guests do run fail2ban (delivered via atrpms) and iptables (allowing only HTTP, HTTPS and SSH) connections. PS for obvious reasons I am not posting IP addresses and routes etc first up, I can make that information available if required. -- The secret impresses no-one, the trick you use it for is everything - Alfred Borden (The Prestiege) ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Domain0 with Kernel 2.6.18-92.1.22.el5xen fails to boot Guests with Kernel 2.6.18-164.el5xen
Hi Pasi,
On Sun, Sep 27, 2009 at 8:21 PM, Pasi Kärkkäinen pa...@iki.fi wrote:
On Sun, Sep 27, 2009 at 12:46:46PM +1000, Devraj Mukherjee wrote:
Hi all,
I am in a bit of a fix here, I have several Guests paravirtualized
running on a Dom0 that is currently running the 2.6.18-92.1.22.el5xen
Kernel. All my guests (administered by different people) have
subsequently been updated to later versions of the kernel (namely
2.6.18-164.el5xen or 2.6.18-128.4.1.el5xen).
Ones that are still running are using the Kernel 2.6.18-128.4.1.el5xen
while Dom0 is still booted up into 2.6.18-92.1.22.el5xen
I restarted a Guest that's now trying to boot with the
2.6.18-164.el5xen Kernel and it spits out messages like
XENBUS: Waiting for devices to initialise: 295s...290s...
and eventually reboots.
If I try and interrupt the boot and choose a previous version of the
Kernel on the Guest, it says the following and fails to boot. The
guests use a single disk image that has the SWAP and Root partitions.
Is this happening because the version of the kernel on the Dom0 is way
too old for guests to boot? I am just a bit hesitant in rebooting my
server for the new kernel to take effect unless I am sure :)
No, that shouldn't be the reason.
The layer between dom0 and guests is Xen hypervisor, not the kernel.
Although Redhat ships the hypervisor in the same rpm as the kernel :)
That's what I thought as well. I did however find the following post
while searching for answers
http://lists.centos.org/pipermail/centos/2008-January/049757.html
That outlines something similar to what I am experiencing and
indicates a reboot of the Dom0 fixed it. I am guessing this is because
of Kernel + Driver loading issues.
The output looks like the initrd image is broken; it doesn't set up the root
device.. does it load the xenblk driver? Does it detect the xvd* disks?
Is xenblk supposed to be loaded on Dom0?
Please paste the full domU kernel boot log..
The following is my Dom0 xend.log
[2009-09-28 07:48:38 xend 19091] INFO (SrvDaemon:283) Xend Daemon started
[2009-09-28 07:48:38 xend 19091] INFO (SrvDaemon:287) Xend changeset:
unavailable.
[2009-09-28 07:48:38 xend 3549] INFO (SrvDaemon:190) Xend stopped due
to signal 15.
[2009-09-28 07:48:38 xend.XendDomainInfo 19091] DEBUG
(XendDomainInfo:222) XendDomainInfo.recreate({'paused': 0, 'cpu_time':
144612597591622L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0,
'dying': 0, 'mem_kb': 1047748L, 'domid': 0, 'max_vcpu_id': 7,
'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': 0,
'online_vcpus': 8, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0], 'blocked': 0})
[2009-09-28 07:48:38 xend.XendDomainInfo 19091] INFO
(XendDomainInfo:234) Recreating domain 0, UUID
----.
[2009-09-28 07:48:38 xend 19091] DEBUG (XendDomain:163) number of
vcpus to use is 0
[2009-09-28 07:48:38 xend.XendDomainInfo 19091] DEBUG
(XendDomainInfo:1036) XendDomainInfo.handleShutdownWatch
[2009-09-28 07:48:38 xend.XendDomainInfo 19091] DEBUG
(XendDomainInfo:222) XendDomainInfo.recreate({'paused': 0, 'cpu_time':
649872953225837L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0,
'dying': 0, 'mem_kb': 716584L, 'domid': 11, 'max_vcpu_id': 3,
'crashed': 0, 'running': 0, 'maxmem_kb': 716800L, 'shutdown': 0,
'online_vcpus': 4, 'handle': [158, 197, 14, 207, 118, 131, 228, 14,
11, 141, 80, 155, 130, 15, 78, 19], 'blocked': 1})
[2009-09-28 07:48:38 xend.XendDomainInfo 19091] INFO
(XendDomainInfo:234) Recreating domain 11, UUID
9ec50ecf-7683-e40e-0b8d-509b820f4e13.
[2009-09-28 07:48:38 xend.XendDomainInfo 19091] DEBUG
(XendDomainInfo:222) XendDomainInfo.recreate({'paused': 0, 'cpu_time':
31557343513225L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0,
'dying': 0, 'mem_kb': 614220L, 'domid': 15, 'max_vcpu_id': 0,
'crashed': 0, 'running': 0, 'maxmem_kb': 614400L, 'shutdown': 0,
'online_vcpus': 1, 'handle': [205, 119, 123, 10, 116, 195, 147, 157,
102, 33, 48, 200, 229, 25, 31, 67], 'blocked': 1})
[2009-09-28 07:48:38 xend.XendDomainInfo 19091] INFO
(XendDomainInfo:234) Recreating domain 15, UUID
cd777b0a-74c3-939d-6621-30c8e5191f43.
[2009-09-28 07:48:38 xend.XendDomainInfo 19091] DEBUG
(XendDomainInfo:222) XendDomainInfo.recreate({'paused': 0, 'cpu_time':
439665875780158L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0,
'dying': 0, 'mem_kb': 1433392L, 'domid': 19, 'max_vcpu_id': 3,
'crashed': 0, 'running': 0, 'maxmem_kb': 1433600L, 'shutdown': 0,
'online_vcpus': 4, 'handle': [5, 72, 139, 170, 228, 55, 87, 82, 223,
36, 98, 155, 30, 97, 160, 1], 'blocked': 1})
[2009-09-28 07:48:38 xend.XendDomainInfo 19091] INFO
(XendDomainInfo:234) Recreating domain 19, UUID
05488baa-e437-5752-df24-629b1e61a001.
[2009-09-28 07:48:38 xend.XendDomainInfo 19091] DEBUG
(XendDomainInfo:222) XendDomainInfo.recreate({'paused': 0, 'cpu_time':
46317871738603L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0,
'dying': 0, 'mem_kb': 1048340L, 'domid': 20, 'max_vcpu_id': 3,
'crashed': 0, 'running': 0
[CentOS-virt] Activity logger for Xen Guest Domains using libvirt
Hi all, Wondering if anyone knows of any tools I can run on my Dom0 to log various stats (like CPU usage, memory usage, etc) for each guest domain for analysis over a period of time? I can see that xentop displays that information anyway but would be nice to be able to present that information on a web based interface for day to day administration. Also any tools that send out email notifications in case of a guest running in critical condition like out of memory etc. Thanks. -- The secret impresses no-one, the trick you use it for is everything - Alfred Borden (The Prestiege) ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Ubuntu 8.04 DomU image from jailtime.org on CentOS 5.2 Dom0
Further thought to my own issue, the processor in use isn't on the Xen Wiki for HVM compatible processors. That might be my issue Thanks. On Wed, Jan 7, 2009 at 6:55 PM, Devraj Mukherjee dev...@gmail.com wrote: Hi Todd / all, Thanks again for responding to me. Interestingly the screen dump of virt-install on that howto is different from mine. Mine actually doesn't ask about fully virtualized guests. How can I start virt-install to boot from an ISO? Thanks. On Wed, Jan 7, 2009 at 4:52 PM, Todd Deshane desha...@gmail.com wrote: On Wed, Jan 7, 2009 at 12:41 AM, Devraj Mukherjee dev...@gmail.com wrote: Hi Todd, Thanks for the message. I got a little bit further but still no joy, its stops with the following messages. Is it better off installing Ubuntu in the image? Boris has a bunch of howtos on this sort of thing... Here is one for Ubuntu on CentOS 5.2: http://bderzhavets.wordpress.com/2008/10/28/install-ubuntu-intrepid-server-pv-domu-at-xen-33-port-via-httpgetco-centos-52-dom0/ I am pretty sure that problem below is still fixable, but the hour is late, so I remember the solution... Google and/or xen.markmail.org may have some hints for you... Best of Luck. Todd mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! [r...@sphere auto]# -- Todd Deshane http://todddeshane.net http://runningxen.com -- I never look back darling, it distracts from the now, Edna Mode (The Incredibles) -- I never look back darling, it distracts from the now, Edna Mode (The Incredibles) ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Ubuntu 8.04 DomU image from jailtime.org on CentOS 5.2 Dom0
Hello all, I am trying to get an Ubuntu 8.04 image running on my CentOS 5.2 Dom0 which so far has only been running CentOS 5.2 DomUs. The image I am trying to run was fetched from jailtime.org (just so I didn't have to go through building an image for myself). The configuration of the DomU is based on what the guys at jailtime.org provided and its as follows name = redgum kernel = /boot/vmlinuz-2.6.18-92.1.22.el5xen memory = 1024 disk = ['file:/srv/xen/redgum.img,sda1,w'] root = /dev/sda1 ro vif = [ 'bridge=xenbr0', ] vcpus=4 on_reboot = 'restart' on_crash = 'restart' When I start the VM I get the following message VFS: Cannot open root device sda1 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) As per my configuration I have mounted the image to sda1 and the root is specified for the Kernel. Any one with similar experiences or could point me to the right direction? Thanks. -- I never look back darling, it distracts from the now, Edna Mode (The Incredibles) ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Ubuntu 8.04 DomU image from jailtime.org on CentOS 5.2 Dom0
Hi Todd / all, Thanks again for responding to me. Interestingly the screen dump of virt-install on that howto is different from mine. Mine actually doesn't ask about fully virtualized guests. How can I start virt-install to boot from an ISO? Thanks. On Wed, Jan 7, 2009 at 4:52 PM, Todd Deshane desha...@gmail.com wrote: On Wed, Jan 7, 2009 at 12:41 AM, Devraj Mukherjee dev...@gmail.com wrote: Hi Todd, Thanks for the message. I got a little bit further but still no joy, its stops with the following messages. Is it better off installing Ubuntu in the image? Boris has a bunch of howtos on this sort of thing... Here is one for Ubuntu on CentOS 5.2: http://bderzhavets.wordpress.com/2008/10/28/install-ubuntu-intrepid-server-pv-domu-at-xen-33-port-via-httpgetco-centos-52-dom0/ I am pretty sure that problem below is still fixable, but the hour is late, so I remember the solution... Google and/or xen.markmail.org may have some hints for you... Best of Luck. Todd mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! [r...@sphere auto]# -- Todd Deshane http://todddeshane.net http://runningxen.com -- I never look back darling, it distracts from the now, Edna Mode (The Incredibles) ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
