Re: [Xen-devel] 4.2 unstable kernel restarting before booting OS kernel

[Aaron Lebahn <cplusplus328@xxxxxxxxx>]

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@xxxxxxxxx> 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@xxxxxxxxxx> 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@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

-- 
Aaron Lebahn
cplusplus328@xxxxxxxxx
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel