Ian Murray
2009-Sep-17 18:40 UTC
[Xen-users] CentOS Xen Kernel 2.6.18-164 and Gitco Hypervisor 3.3.1 problem
Hi All, I upgraded my Dom0 kernel to the above version during a normal yum update. After reboot, I got some flashed message about not a proper root and then a cannot sync error followed by an (almost) immediate reboot. I have no clue where this is logged, if indeed it is. /var/log/messages has yielded nothing, but I suspect this is way early in the boot process for that. I will try to look for a start-up kernel switch to stop it rebooting immediately. Running the kernel straight had no issues. I was more intent on just getting my server up so reverted to previous kernel and all was back to normal. I have already asked on the CentOS list and apparently this kernel is not having any issues with the hypervisor provided under CentOS. Whilst I try to get a few more details of exactly what those error messages were, I thought I would ask see if anybody has anything similar or if they have the above configuration without issue. Thanks in advance, Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Boris Derzhavets
2009-Sep-17 18:51 UTC
Re: [Xen-users] CentOS Xen Kernel 2.6.18-164 and Gitco Hypervisor 3.3.1 problem
>I upgraded my Dom0 kernel to the above version during a normal yum >updateAre you saying that CentOS Xen Hypervisor is 3.3.1 in meantime ? I guess normal yum update goes only to CentOS Repo. I believe that yum install Gitco''s rpms along with gitco''s repo activated may bring your hypervisor to 3.3.1 Boris. --- On Thu, 9/17/09, Ian Murray <murrayie@yahoo.co.uk> wrote: From: Ian Murray <murrayie@yahoo.co.uk> Subject: [Xen-users] CentOS Xen Kernel 2.6.18-164 and Gitco Hypervisor 3.3.1 problem To: xen-users@lists.xensource.com Date: Thursday, September 17, 2009, 2:40 PM Hi All, I upgraded my Dom0 kernel to the above version during a normal yum update. After reboot, I got some flashed message about not a proper root and then a cannot sync error followed by an (almost) immediate reboot. I have no clue where this is logged, if indeed it is. /var/log/messages has yielded nothing, but I suspect this is way early in the boot process for that. I will try to look for a start-up kernel switch to stop it rebooting immediately. Running the kernel straight had no issues. I was more intent on just getting my server up so reverted to previous kernel and all was back to normal. I have already asked on the CentOS list and apparently this kernel is not having any issues with the hypervisor provided under CentOS. Whilst I try to get a few more details of exactly what those error messages were, I thought I would ask see if anybody has anything similar or if they have the above configuration without issue. Thanks in advance, Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Murray
2009-Sep-17 21:15 UTC
Re: [Xen-users] CentOS Xen Kernel 2.6.18-164 and Gitco Hypervisor 3.3.1 problem
>>I upgraded my Dom0 kernel to the above version during a normal yum >update > >Are you saying that CentOS Xen Hypervisor is 3.3.1 in meantime ? >I guess normal yum update goes only to CentOS Repo. >I believe that yum install Gitco''s rpms along with gitco''s repo activated >may bring your hypervisor to 3.3.1Sorry, I may not have been explicit. I am currently using the Xen hypervisor from Gitco, which is 3.3.1 and the xen kernel from normal CentOS repos. Xen hypervisor hasn''t changed, nor did I want it to. Thanks. Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Murray
2009-Sep-17 23:21 UTC
Re: [Xen-users] CentOS Xen Kernel 2.6.18-164 and Gitco Hypervisor 3.3.1 problem
Turned out I have an extra initrd image file for the problematic kernel with the suffix ".dup_orig" on it. I removed a few old kernels and removed and re-added the 2.6.18-164 xen kernel and then all was fine. Thanks anyway. ----- Original Message ----> From: Ian Murray <murrayie@yahoo.co.uk> > To: Boris Derzhavets <bderzhavets@yahoo.com>; xen-users@lists.xensource.com > Sent: Thursday, 17 September, 2009 22:15:26 > Subject: Re: [Xen-users] CentOS Xen Kernel 2.6.18-164 and Gitco Hypervisor 3.3.1 problem > > > >>I upgraded my Dom0 kernel to the above version during a normal yum >update > > > >Are you saying that CentOS Xen Hypervisor is 3.3.1 in meantime ? > >I guess normal yum update goes only to CentOS Repo. > >I believe that yum install Gitco''s rpms along with gitco''s repo activated > >may bring your hypervisor to 3.3.1 > > Sorry, I may not have been explicit. I am currently using the Xen hypervisor > from Gitco, which is 3.3.1 and the xen kernel from normal CentOS repos. Xen > hypervisor hasn''t changed, nor did I want it to. > > Thanks. > > > Send instant messages to your online friends http://uk.messenger.yahoo.com > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users