On Mon, Sep 29, 2008 at 4:17 PM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
> On Sat, Sep 27, 2008 at 7:04 PM, Ferenc Wagner <wferi@xxxxxxx> wrote:
>> "Andrew Lyon" <andrew.lyon@xxxxxxxxx> writes:
>>> It seems that the serial console is completely dead after "Freeing
>>> unused kernel memory: 208k freed"
>> That's strange indeed. What appears on the VGA console after this
>> line? (If you can scroll back via Shift+PgUp.)
>>> I cannot access the sysreq commands and which I need to debug a
>>> lockup problem.
>> I've never managed to get the break through the hypervisor on a serial
>> port. That means no sysrq for dom0. That and the lack of flow
>> control make the Xen serial support unprofessional. Those would be my
>> wishes for 3.4... :)
> Indeed mine too, I've been getting random lockups on all 3 of the
> machines I've tested Xen on, with kernel 2.6.18 xensource, 2.6.21
> gentoo and 2.6.25 suse, without sysrq I don't have any hope of
> debugging the lockups at all and I will probably end up abandoning Xen
> which will be a real shame, I really like the performance and features
> and I really dont want to go back to vmware now.
Sysrq works!, you need to use ctrl+o instead of break, i.e. ctrl+o, <command>.
>>> Is there something wrong with the way I have configured the serial
>> As you can see some kernel messages, it looks like you configured the
>> kernel console, contrary to what your config shows...
Xen-users mailing list