Re: [CentOS-virt] Fwd: Xen4CentOS kernel panic on dom0 reboot

[PJ Welsh]

No, I have not followed those instructions yet. These were production
servers that I had scheduled firmware updates late Sunday evening. The
first time I though the error was a fluke and only began to research it
after the second failure (and still no firmware updates due to the
power-cycle). I may try to sneak in a restart of one of the systems late
Sunday night US CT.

Still not sure why the running vm's would stop the reboot... The server
shows that it was suppose to be restarting. I have had a similar stuck on
restarting message (minus all the umount errors) on some Dell T105's
running CentOS 6.5 and the reboot=pci grub.conf kernel option is what
ended up working for them. I have not tested that possible option yet,
either since that would take 2 reboots to put into place.


On Fri, Mar 7, 2014 at 10:43 PM, Pasi Kärkkäinen pa...@iki.fi wrote:

 On Thu, Mar 06, 2014 at 01:54:22PM -0600, Phillippe Welsh wrote:
 
  Subject: Re: [CentOS-virt] Xen4CentOS kernel panic on dom0 reboot
 
  On Wed, Mar 5, 2014 at 10:17 AM, David Vrabel david.vrabel at
 citrix.comwrote:
 
On 05/03/14 15:09, Karl Johnson wrote:
 I've been using Xen4CentOS for the last 3 months. It's working
 fine and
 dom0/domUs are stable but the server does a kernel panic when
 doing a
 reboot and the server has to be hard reset manually. It has kernel
 panic
on the 3 last reboot.
   
There is a xenbus device still present and during shutdown it is
 trying
to set it to CLOSED but at this point xenstored isn't running and the
xenbus write stalls.
   
Do you have VMs that are still running when you attempt a reboot?
  If so
shutting them down will likely avoid this.
   
Can you provide the output of xenstore-ls prior to attempting a
 reboot?
   
   
   
   I though Xen init.d scripts would stop all of them before rebooting?
 Here's
   the output of chkconfig and xenstore-ls:
  
   http://pastebin.centos.org/8186/
  
   Thanks,
  
   Karl
 
  I've got the me-too on the reboot hang issue for 2 different Dell
 R710's with xen-4.2.4-29.el6 and at least the kernels 
 kernel-3.10.25-11.el6.centos.alt.x86_64
 and kernel-3.10.23-11.el6.centos.alt.x86_64. I have not tried to reboot
 with the latest kernel-3.10.32-11.el6.centos.alt.x86_64 (if kernel even
 makes a difference). I *have* had dom0_mem=1024M,max:1024M option in place
 for all of them with only 6 VM's.
 
  Any new suggestions?
 

 So did you make sure all the VMs are shut down before trying to reboot
 dom0?

 -- Pasi

 ___
 CentOS-virt mailing list
 CentOS-virt@centos.org
 http://lists.centos.org/mailman/listinfo/centos-virt

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] Remove Centos from AWS marketplace

[JacobV]

https://forums.aws.amazon.com/thread.jspa?messageID=481859#481859
https://forums.aws.amazon.com/thread.jspa?messageID=453572#453572

This is a timebomb waiting to strike so many people who like do daily snapshot 
backups and keep them for few weeks and not realizing their snapshots are 
useless if they had accidentally mess up some boot related file earlier on.


Another scenario you mess up the sudoers file or the root authorized keys - 
you'd have to loose a whole days data and go to previous nights restore just 
for single file error like that ?

If AWS marketplace is unable to remove this hardcoded rule then it's only 
prudent to remove Centos from AWS marketplace and release it in the community 
section instead ?

Thoughts ?___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt