Xen devel - Jul 2012 - 4.2 unstable kernel restarting before booting OS kernel

Hi all-
I''m using Ubuntu 12.04 and compiled unstable on revision
25605:9950f2dc2ee6, the compilation completed cleanly and I issued
sudo make install.  I modified the grub entry for Xen 4.1 as follows:

menuentry ''Ubuntu GNU/Linux, with Xen 4.2-unstable and Linux
3.2.19''
--class ubuntu --class gnu-linux --class gnu --class os --class xen {
	insmod part_msdos
	insmod ext2
	set root=''(hd0,msdos1)''
	search --no-floppy --fs-uuid --set=root 77928457-0585-4dac-bc8d-d99d346dff02
	echo	''Loading Xen 4.2-unstable ...''
	multiboot	/xen-4.2-unstable.gz placeholder
	echo	''Loading Linux 3.2.19 ...''
	module	/vmlinuz-3.2.19 placeholder root=/dev/mapper/xen-root ro
	echo	''Loading initial ramdisk ...''
	module	/initrd.img-3.2.19
}

It starts booting the Xen kernel, but then reboots prior to booting
the Linux kernel (as far as I can tell), without printing any sort of
error that I can see.  Are there any suggestions on how to diagnose
what is happening?

Thanks,
David

On Sat, 2012-07-14 at 17:56 -0400, David Erickson wrote:
> Hi all-
> I''m using Ubuntu 12.04 and compiled unstable on revision
> 25605:9950f2dc2ee6, the compilation completed cleanly and I issued
> sudo make install.  I modified the grub entry for Xen 4.1 as follows:
> 
> menuentry ''Ubuntu GNU/Linux, with Xen 4.2-unstable and Linux
3.2.19''
> --class ubuntu --class gnu-linux --class gnu --class os --class xen {
> 	insmod part_msdos
> 	insmod ext2
> 	set root=''(hd0,msdos1)''
> 	search --no-floppy --fs-uuid --set=root
77928457-0585-4dac-bc8d-d99d346dff02
> 	echo	''Loading Xen 4.2-unstable ...''
> 	multiboot	/xen-4.2-unstable.gz placeholder
> 	echo	''Loading Linux 3.2.19 ...''
> 	module	/vmlinuz-3.2.19 placeholder root=/dev/mapper/xen-root ro
> 	echo	''Loading initial ramdisk ...''
> 	module	/initrd.img-3.2.19
> }
> 
> It starts booting the Xen kernel, but then reboots prior to booting
> the Linux kernel (as far as I can tell), without printing any sort of
> error that I can see.  Are there any suggestions on how to diagnose
> what is happening?
You can add "noreboot" to your hypervisor command line which will give
you the chance to see any messages printed at the last minute.

Or you can use a serial console
http://wiki.xen.org/wiki/XenSerialConsole

Ian.

Hi Ian-
noreboot prevented the reboot, but it has hung right after Xen blanked
the screen.  My USB serial port is about a half an hour away so I''ll
get that later on and see if I can get any more info from its output.
Are there any kernel changes required when going from 4.1->4.2?
Should my kernel that works fine with 4.1 work with 4.2?  And
presumably since it has hung and the noreboot line was on the xen
kernel line, the problem exists in the xen kernel?

Thanks,
David


On Sat, Jul 14, 2012 at 3:04 PM, Ian Campbell <ian.campbell@citrix.com>
wrote:
> On Sat, 2012-07-14 at 17:56 -0400, David Erickson wrote:
>> Hi all-
>> I''m using Ubuntu 12.04 and compiled unstable on revision
>> 25605:9950f2dc2ee6, the compilation completed cleanly and I issued
>> sudo make install.  I modified the grub entry for Xen 4.1 as follows:
>>
>> menuentry ''Ubuntu GNU/Linux, with Xen 4.2-unstable and Linux
3.2.19''
>> --class ubuntu --class gnu-linux --class gnu --class os --class xen {
>>       insmod part_msdos
>>       insmod ext2
>>       set root=''(hd0,msdos1)''
>>       search --no-floppy --fs-uuid --set=root
77928457-0585-4dac-bc8d-d99d346dff02
>>       echo    ''Loading Xen 4.2-unstable ...''
>>       multiboot       /xen-4.2-unstable.gz placeholder
>>       echo    ''Loading Linux 3.2.19 ...''
>>       module  /vmlinuz-3.2.19 placeholder root=/dev/mapper/xen-root ro
>>       echo    ''Loading initial ramdisk ...''
>>       module  /initrd.img-3.2.19
>> }
>>
>> It starts booting the Xen kernel, but then reboots prior to booting
>> the Linux kernel (as far as I can tell), without printing any sort of
>> error that I can see.  Are there any suggestions on how to diagnose
>> what is happening?
>
> You can add "noreboot" to your hypervisor command line which will
give
> you the chance to see any messages printed at the last minute.
>
> Or you can use a serial console
> http://wiki.xen.org/wiki/XenSerialConsole
>
> Ian.
>
>

On Sat, 2012-07-14 at 19:01 -0400, David Erickson wrote:
> Hi Ian-
> noreboot prevented the reboot, but it has hung right after Xen blanked
> the screen.  My USB serial port is about a half an hour away so
I''ll
> get that later on and see if I can get any more info from its output.
Great, thanks.
> Are there any kernel changes required when going from 4.1->4.2?
> Should my kernel that works fine with 4.1 work with 4.2?
There''s no particular linkage between the kernel and the hypervisor
version. So your kernel should be fine.
>   And
> presumably since it has hung and the noreboot line was on the xen
> kernel line, the problem exists in the xen kernel?
It could still be either I think.

Did you see the last thing printed before the screen went blank?

You might want to add debug options to both command lines, there''s some
stuff about that in 
http://wiki.xen.org/wiki/XenParavirtOps

You mention the screen going blank, might be worth having a look through
http://wiki.xen.org/wiki/XenPVOPSDRM

Ian.

Note that while a usb-to-serial adapter will work for the remote debugging
computer, you need a physical port on the computer running xen.

On Sat, Jul 14, 2012 at 5:01 PM, David Erickson
<halcyon1981@gmail.com>wrote:
> Hi Ian-
> noreboot prevented the reboot, but it has hung right after Xen blanked
> the screen.  My USB serial port is about a half an hour away so
I''ll
> get that later on and see if I can get any more info from its output.
> Are there any kernel changes required when going from 4.1->4.2?
> Should my kernel that works fine with 4.1 work with 4.2?  And
> presumably since it has hung and the noreboot line was on the xen
> kernel line, the problem exists in the xen kernel?
>
> Thanks,
> David
>
>
> On Sat, Jul 14, 2012 at 3:04 PM, Ian Campbell
<ian.campbell@citrix.com>
> wrote:
> > On Sat, 2012-07-14 at 17:56 -0400, David Erickson wrote:
> >> Hi all-
> >> I''m using Ubuntu 12.04 and compiled unstable on revision
> >> 25605:9950f2dc2ee6, the compilation completed cleanly and I issued
> >> sudo make install.  I modified the grub entry for Xen 4.1 as
follows:
> >>
> >> menuentry ''Ubuntu GNU/Linux, with Xen 4.2-unstable and
Linux 3.2.19''
> >> --class ubuntu --class gnu-linux --class gnu --class os --class
xen {
> >>       insmod part_msdos
> >>       insmod ext2
> >>       set root=''(hd0,msdos1)''
> >>       search --no-floppy --fs-uuid --set=root
> 77928457-0585-4dac-bc8d-d99d346dff02
> >>       echo    ''Loading Xen 4.2-unstable ...''
> >>       multiboot       /xen-4.2-unstable.gz placeholder
> >>       echo    ''Loading Linux 3.2.19 ...''
> >>       module  /vmlinuz-3.2.19 placeholder
root=/dev/mapper/xen-root ro
> >>       echo    ''Loading initial ramdisk ...''
> >>       module  /initrd.img-3.2.19
> >> }
> >>
> >> It starts booting the Xen kernel, but then reboots prior to
booting
> >> the Linux kernel (as far as I can tell), without printing any sort
of
> >> error that I can see.  Are there any suggestions on how to
diagnose
> >> what is happening?
> >
> > You can add "noreboot" to your hypervisor command line which
will give
> > you the chance to see any messages printed at the last minute.
> >
> > Or you can use a serial console
> > http://wiki.xen.org/wiki/XenSerialConsole
> >
> > Ian.
> >
> >
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>


-- 
Aaron Lebahn
cplusplus328@gmail.com


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

On Sat, Jul 14, 2012 at 4:09 PM, Ian Campbell <ian.campbell@citrix.com>
wrote:
> On Sat, 2012-07-14 at 19:01 -0400, David Erickson wrote:
>> Hi Ian-
>> noreboot prevented the reboot, but it has hung right after Xen blanked
>> the screen.  My USB serial port is about a half an hour away so
I''ll
>> get that later on and see if I can get any more info from its output.
>
> Great, thanks.
>
>> Are there any kernel changes required when going from 4.1->4.2?
>> Should my kernel that works fine with 4.1 work with 4.2?
>
> There''s no particular linkage between the kernel and the
hypervisor
> version. So your kernel should be fine.
>
>>   And
>> presumably since it has hung and the noreboot line was on the xen
>> kernel line, the problem exists in the xen kernel?
>
> It could still be either I think.
>
> Did you see the last thing printed before the screen went blank?
It went by super fast, it was hard to see, I''ll get the cable and
report back.

> You might want to add debug options to both command lines, there''s
some
> stuff about that in
> http://wiki.xen.org/wiki/XenParavirtOps
>
> You mention the screen going blank, might be worth having a look through
> http://wiki.xen.org/wiki/XenPVOPSDRM
Thanks I''ll take a look at these.

On Sat, Jul 14, 2012 at 4:15 PM, Aaron Lebahn <cplusplus328@gmail.com>
wrote:
> Note that while a usb-to-serial adapter will work for the remote debugging
> computer, you need a physical port on the computer running xen.
Yep I have a port on the machine, but nowhere to sink it to right now :)

Ok, boot log attached.  Grub boot line was as follows:

menuentry ''Ubuntu GNU/Linux, with Xen 4.2-unstable and Linux
3.2.19''
--class ubuntu --class gnu-linux --class gnu --class os --class xen {
	insmod part_msdos
	insmod ext2
	set root=''(hd0,msdos1)''
	search --no-floppy --fs-uuid --set=root 77928457-0585-4dac-bc8d-d99d346dff02
	echo	''Loading Xen 4.2-unstable ...''
	multiboot	/xen-4.2-unstable.gz placeholder sync_console
console_to_ring loglvl=all guest_loglvl=all com1=38400,8n1,0x3f8,4
console=com1,vga
	echo	''Loading Linux 3.2.19 ...''
	module	/vmlinuz-3.2.19 placeholder root=/dev/mapper/xen-root ro
console=hvc0,vga earlyprintk=xen nomodeset initcall_debug debug
loglevel=10
	echo	''Loading initial ramdisk ...''
	module	/initrd.img-3.2.19
}

Also, I am using an Intel Xeon E3-1230 V2 Ivy Bridge Xeon if that is relevant.

Thanks,
David


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

On Jul 15, 2012 12:21 AM, "David Erickson"
<halcyon1981@gmail.com> wrote:
>
> Ok, boot log attached.  Grub boot line was as follows:Oil
>
> menuentry ''Ubuntu GNU/Linux, with Xen 4.2-unstable and Linux
3.2.19''
> --class ubuntu --class gnu-linux --class gnu --class os --class xen {
>         insmod part_msdos
>         insmod ext2
>         set root=''(hd0,msdos1)''
>         search --no-floppy --fs-uuid --set=root
77928457-0585-4dac-bc8d-d99d346dff02
>         echo    ''Loading Xen 4.2-unstable ...''
>         multiboot       /xen-4.2-unstable.gz placeholder sync_console
> console_to_ring loglvl=all guest_loglvl=all com1=38400,8n1,0x3f8,4
> console=com1,vga
>         echo    ''Loading Linux 3.2.19 ...''
>         module  /vmlinuz-3.2.19 placeholder root=/dev/mapper/xen-root ro
> console=hvc0,vga earlyprintk=xen nomodeset initcall_debug debug
> loglevel=10
>         echo    ''Loading initial ramdisk ...''
>         module  /initrd.img-3.2.19
> }
>
> Also, I am using an Intel Xeon E3-1230 V2 Ivy Bridge Xeon if that is
relevant.

This is a known issue. Please add xsave=0 to your can kernel command line.

http://lists.xen.org/archives/html/xen-devel/2012-05/msg00049.html
> Thanks,
> David
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

> This is a known issue. Please add xsave=0 to your can kernel command line.
>
> http://lists.xen.org/archives/html/xen-devel/2012-05/msg00049.html
Confirmed, this resolved it.  Also, using kernel 3.4.4 works without
the additional parameter.