Hi Michael,
I didn't save the original thread when you posted this, so my apologies for breaking threading. :)
I just tried this kernel on Fedora 14 x86_64 and, like several of the previous attempts, it simply reboots after xen.gz finishes booting (at least, this is what I can guess, as the screen is black). This is despite hearing other report much better success. So I was wondering if these kernels have been tested against dom0 with an encrypted ext4 root partition?
I'm going to try the 4.0.2-rc1 xen hypervisor shortly. In the meantime, is there anything I can do to help narrow down the potential source of the problem?
Thanks for the continued hard work. :)
On Tue, 11 Jan 2011, Digimer wrote:
I just tried this kernel on Fedora 14 x86_64 and, like several of the previous attempts, it simply reboots after xen.gz finishes booting (at least, this is what I can guess, as the screen is black). This is despite hearing other report much better success. So I was wondering if these kernels have been tested against dom0 with an encrypted ext4 root partition?
How much memory do you have, and does the kernel-debug kernel work? I am chasing a similar sounding crash on my 4GB machine. A workaround for me is to put dom0_mem=max:2GB on the xen line. Curiously enough it did work without this before Fedora stripped out the debugging options, and the debug kernel still boots for me.
If you want to see the crash information try adding vga=ask,keep to the xen line and console=hvc0 to the vmlinuz line (and pick a vga mode when asked). Ideally you would set up a serial console and capture the whole output, as detailed on the xen.org wiki, but my hardware doesn't make that practical.
Michael Young
On 01/11/2011 03:33 AM, M A Young wrote:
On Tue, 11 Jan 2011, Digimer wrote:
I just tried this kernel on Fedora 14 x86_64 and, like several of the previous attempts, it simply reboots after xen.gz finishes booting (at least, this is what I can guess, as the screen is black). This is despite hearing other report much better success. So I was wondering if these kernels have been tested against dom0 with an encrypted ext4 root partition?
How much memory do you have, and does the kernel-debug kernel work? I am chasing a similar sounding crash on my 4GB machine. A workaround for me is to put dom0_mem=max:2GB on the xen line. Curiously enough it did work without this before Fedora stripped out the debugging options, and the debug kernel still boots for me.
If you want to see the crash information try adding vga=ask,keep to the xen line and console=hvc0 to the vmlinuz line (and pick a vga mode when asked). Ideally you would set up a serial console and capture the whole output, as detailed on the xen.org wiki, but my hardware doesn't make that practical.
Michael Young
I've got 8GB. I'll try xen'ifying the debug kernel and dropping the dom0 memory to 8gb and will report back. As for the serial console, I'll have to see if I can do that. If it requires a serial port, then I'm out of luck. :)
Thanks.
-
Digimer -
M A Young