On Sat, Mar 06, 2010 at 12:58:33PM +0100, Josip Rodin wrote:
> I updated the hypervisor from 3.4.0 to 3.4.3rc3, which seemed to go well
> because it seems to behave as usual, but the dom0 kernel update from an
> earlier (pre-2009-11-30) xen/master snapshot based on 184.108.40.206 didn't -
> as soon as it starts, it just instantly reboots, or if noreboot is passed,
> it gets stuck, with absolutely nothing on the screen.
So the 2009-11-30 xen/master 220.127.116.11 dom0 kernel works with Xen 3.4.3rc3
but when you update the dom0 kernel to current xen/master 18.104.22.168, it crashes?
> I tried adding loglvl=all guest_loglvl=all sync_console console_to_ring
> to the hypervisor options, and console=hvc0 earlyprintk=xen initcall_debug
> to the kernel options, to no avail. The hypervisor showed the sync console
> warning, but the dom0 kernel didn't change its behaviour.
You should set up a serial console so you can capture the boot/error logs,
and we can analyze them to troubleshoot the problem, see:
Xen-devel mailing list