On Tue, May 29, 2012 at 03:29:48PM +0300, Pasi Kärkkäinen wrote: > On Tue, May 29, 2012 at 01:38:09PM +0200, Steven Smith wrote: > > > > When i update the kernel with yum, the kernel is built, the (many) grub > > entries are added (all appended correctly). Everything looks good. I can > > boot the non-xen kernel fine.. starts up, correct version of kernel. But > > starting the new xen dom0 kernel does not work. It just hangs, even with > > manual command-line entries. I can boot the old xen dom0 kernel without > > any problems, and it runs as before. What is held in the xen-4.1.x.gz > > file? I had expected this gz to be rebuilt or at least touched.. but it > > is not. What are the usual steps required to upgrade the dom0 kernel > > manually? Must it be done from the xendom0 or the stand alone kernel? > > Are any special steps needed? (yum update is apparently insufficient). > > Is there a special order to be adhered to? > > > > uname (current): > > Linux myserver.mydomain.local 3.2.1-3.fc16.x86_64 #1 SMP Mon Jan 23 > > 15:36:17 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux > > > > the newly compiled non-booting kernel is: 3.3.1-3.fc16.x86_64 > > > > Oh, yes, the latest kernel has some bug when running as dom0. > I wonder if it's this one: https://bugzilla.redhat.com/show_bug.cgi?id=804347 I think it is. I just booted vmlinuz-3.3.6-3.fc16.x86_64 and it had no such trouble. > > Konrad probably knows/remembers.. > > Meanwhile you should set up a serial console so you can capture the crash logs: > http://wiki.xen.org/wiki/XenSerialConsole > > So please post the full Xen hypervisor + dom0 Linux kernel verbose debug log here. > > -- Pasi > > -- > xen mailing list > xen@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/xen
