<div dir="ltr"><div><div>Anyone think it's related to microcode_ctl as noted in <a href="http://lists.us.dell.com/pipermail/linux-poweredge/2013-October/048538.html">http://lists.us.dell.com/pipermail/linux-poweredge/2013-October/048538.html</a> ?<br>
</div>I will see about testing for this issue ASAP...<br><br></div>pjwelsh<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 13, 2014 at 6:58 PM, PJ Welsh <span dir="ltr"><<a href="mailto:pjwelsh@gmail.com" target="_blank">pjwelsh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Comments at bottom:<br><div><div><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, Mar 11, 2014 at 12:32 PM, Phillippe Welsh <span dir="ltr"><<a href="mailto:pjwelsh@gmail.com" target="_blank">pjwelsh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Comments inline:<br>
<div><br>
----- Original Message -----<br>
> From: "Pasi Kärkkäinen" <<a href="mailto:pasik@iki.fi" target="_blank">pasik@iki.fi</a>><br>
> To: "Discussion about the virtualization on CentOS" <<a href="mailto:centos-virt@centos.org" target="_blank">centos-virt@centos.org</a>><br>
> Sent: Sunday, March 9, 2014 4:32:13 AM<br>
> Subject: Re: [CentOS-virt] Fwd: Xen4CentOS kernel panic on dom0 reboot<br>
><br>
> On Sat, Mar 08, 2014 at 09:09:07AM -0600, PJ Welsh wrote:<br>
> > No, I have not followed those instructions yet. These were<br>
> > production<br>
> > servers that I had scheduled firmware updates late Sunday<br>
> > evening. The<br>
> > first time I though the error was a fluke and only began to<br>
> > research it<br>
> > after the second failure (and still no firmware updates due to<br>
> > the<br>
> > power-cycle). I may try to sneak in a restart of one of the<br>
> > systems late<br>
> > Sunday night US CT.<br>
> ><br>
><br>
> OK.<br>
<br>
</div>I ran the "stop" for all of the xen related pieces in the order that the /etc/rc3.d/ had them.<br>
The VM's did not shutdown and the /usr/lib64/xen/bin/qemu-dm STUFF entries were left behind running.<br>
Since I could not xm shutdown any longer, I killed off all qemu-dm proccesses and attempted a reboot...<br>
HUNG on the reboot with the prepended umount error messages...<br>
<div><br>
><br>
> > Still not sure why the running vm's would stop the reboot... The<br>
> > server<br>
> > shows that it was suppose to be restarting. I have had a similar<br>
> > stuck on<br>
> > restarting message (minus all the umount errors) on some Dell<br>
> > T105's<br>
> > running CentOS 6.5 and the "reboot=pci" grub.conf kernel option<br>
> > is what<br>
> > ended up working for them. I have not tested that possible<br>
> > option yet,<br>
> > either since that would take 2 reboots to put into place.<br>
> ><br>
><br>
> Yeah, it's worth testing both, to figure out what's wrong.<br>
<br>
</div>Next reboot attempt included the "reboot=pci" grub.conf kernel option... No affect :(<br>
HUNG on the reboot with the prepended umount error messages...<br>
<br>
I ran out of time to attempt an xm shutdown for each VM manually, then reboot.<br>
<br>
What's interesting is that when I do an lsof on the file system that is unable to umount, the *only* connected PID's are the qemu-dm ones, but not *all* of them.???<br>
<br>
Thanks<br>
<br>
PJ<br>
...<br>
</blockquote></div><br></div></div></div><div class="gmail_extra">UPDATE: I cleanly shut down *all* vm's and unmounted the filesystem that had the umount issue noted previously and then issued the reboot command. *STILL* the Dell R710 will be hung at the rebooting line.<br>
<br></div><div class="gmail_extra">No reboot possible on 2 Dell R710's with at least the 2 most recent CentOSXen4 kernels.<br><br></div><div class="gmail_extra">Any other suggestions?<br><br>Thanks<br><br></div><div class="gmail_extra">
pjwelsh<br></div></div></div>
</blockquote></div><br></div>