[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] booting fails after xen upgrade


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Dongkyu Lee <dongq.lee@xxxxxxxxx>
  • Date: Mon, 16 Nov 2009 15:40:02 +0900
  • Delivery-date: Sun, 15 Nov 2009 22:40:35 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=ddu7Y4FmaV9tZ2hLSnQZqpN8rnxgPQrtJYklKFGYVMLrLwF4KBVRoKgZau/bbEsQND 5ME2915ZDxvmBUTvjVFltraBs8bSGCaJUvgOM1VR3DFukxWsmM1o8seKdfSRPv9NT9Zx GKGM6YbXBVGFnOkoelihxqtjCBaBEn7w8nQr8=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

We are running xen on more 50 servers and recently updated xen from 3.1.3 to 3.4.1. Gitco yum repository has been used for updating. The problem is that more than 50% of servers failed to boot after updating xen. We followed exactly same procedure to update xen version on every server but some servers were successfully updated and others failed (about half and half). All xen and system log files did not show any error message.

Physical Server Model: IBM x3650
Operating System: CentOS 5.3
Raid Controller: IBM ServeRAID-MR10i SAS/SATA Controller

Steps we followed for updating xen
1. edit yum repository (add gitco repository)
2. remove current virtualization package (yum groupremove)
3. install updated xen version (yum groupinstall)
4. edit menu.list
5. reboot

It is hard to distinguish that it is caused from hardware, Linux Kernel, or Xen. Would you guys give me any suggestions that we should check to find out which caused this problem?

Thank you so much in advance.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.