Re: Cannot boot xen DomU > 2.6.23.1

2008-01-18 Thread xming
AZZ # uname -a Linux builder 2.6.18-xen-r8 #3 SMP Thu Dec 20 15:07:20 CET 2007 i686 AMD Athlon(tm) X2 Dual Core Processor BE-2300 AuthenticAMD GNU/Linux cheers xming -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: Cannot boot xen DomU > 2.6.23.1

2008-01-18 Thread xming
> OK, I misunderstood your original report to mean that something was > complaining about "too much" output. You're saying that lots of console > output seems to lock the domain. Sorry about that, and yes that is the case. > I've had a report about heavy disk IO seems to lock up as well. Perhap

Re: Cannot boot xen DomU > 2.6.23.1

2008-01-20 Thread xming
On Jan 18, 2008 6:26 PM, Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote: > >> Would it be possible to map the eip and some top parts of the stack back > >> to kernel symbols? Seems to be the same place in both traces, which is > >> interesting. > Do "nm -n vmlinux" on the kernel to set an address

Re: Cannot boot xen DomU > 2.6.23.1

2008-01-20 Thread xming
On Jan 20, 2008 7:37 PM, Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote: > xming wrote: > > ok I have done some of them, but I still don't know what I should be looking > > at. Do you mean code related to xen or code related to > > have_vcpu_info_placemen

Cannot boot xen DomU > 2.6.23.1

2008-01-17 Thread xming
Hi, I finally found the piece of code that prevents me from booting Xen DomU with vallina kernel > 2.6.23.1. The problem is that with every kernel (> 2.6.32.1 including 2.6.24 RCs) will just hang with "too much" console activity. Sometimes (well most of the time) boot msg is too much. When I can

Re: Cannot boot xen DomU > 2.6.23.1

2008-01-17 Thread xming
On Jan 17, 2008 6:15 PM, Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote: > Uh, that's very strange. That patch fixes an outright bug, unless > you're using one specific changeset out of the xen-unstable mercurial > tree. What version of Xen are you using? Is it one you've built from > xenbits, o