From: Jeremy Fitzhardinge <jeremy@goop.org>
To: xming <xmingske@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cannot boot xen DomU > 2.6.23.1
Date: Thu, 17 Jan 2008 09:15:14 -0800 [thread overview]
Message-ID: <478F8D22.60004@goop.org> (raw)
In-Reply-To: <519a8b110801170813h96b8f2by795e6d8b72a00ba4@mail.gmail.com>
xming wrote:
> 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 boot into the kernel,
> generating a lots of cosole out it will hang, no oops, no more
> console/network. Generating with the same way through ssh will not
> hang the domU.
>
> When I reverse the following patch, things work as before, tried this
> with 2.6.23.14 and 2.6.14-rc8. But I don't have the knowledge to
> understand the reason behind this.
>
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, or distributed by someone? Are you using a 32 or 64 bit xen/dom0?
I don't understand where the "too much console activity" message comes
from. Could you post an actual cut'n'paste of the message, or a
screenshot? Are you using a serial console on your dom0?
Thanks,
J
> BTW, I am not subscribed.
>
> --- a/include/xen/interface/vcpu.h
> +++ b/include/xen/interface/vcpu.h
> @@ -160,8 +160,9 @@ struct vcpu_set_singleshot_timer {
> */
> #define VCPUOP_register_vcpu_info 10 /* arg == struct vcpu_info */
> struct vcpu_register_vcpu_info {
> - uint32_t mfn; /* mfn of page to place vcpu_info */
> - uint32_t offset; /* offset within page */
> + uint64_t mfn; /* mfn of page to place vcpu_info */
> + uint32_t offset; /* offset within page */
> + uint32_t rsvd; /* unused */
> };
>
> #endif /* __XEN_PUBLIC_VCPU_H__ */
>
> I am running Xen 3.1.2 PAE
>
> # uname -a
> Linux builder 2.6.24-rc8 #2 SMP Thu Jan 17 16:37:19 CET 2008 i686
> AMD Athlon(tm) X2 Dual Core Processor BE-2300 AuthenticAMD GNU/Linux
>
> # cat /proc/cpuinfo
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 15
> model : 107
> model name : AMD Athlon(tm) X2 Dual Core Processor BE-2300
> stepping : 1
> cpu MHz : 1899.930
> cache size : 512 KB
> physical id : 0
> siblings : 2
> core id : 1
> cpu cores : 2
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 1
> wp : yes
> flags : fpu tsc msr pae mce cx8 mca cmov pat pse36 clflush
> mmx fxsr sse sse2 ht nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16
> lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch ts fid vid ttp
> tm stc 100mhzsteps
> bogomips : 3829.72
> clflush size : 64
>
> processor : 1
> vendor_id : AuthenticAMD
> cpu family : 15
> model : 107
> model name : AMD Athlon(tm) X2 Dual Core Processor BE-2300
> stepping : 1
> cpu MHz : 1899.930
> cache size : 512 KB
> physical id : 0
> siblings : 2
> core id : 1
> cpu cores : 2
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 1
> wp : yes
> flags : fpu tsc msr pae mce cx8 mca cmov pat pse36 clflush
> mmx fxsr sse sse2 ht nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16
> lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch ts fid vid ttp
> tm stc 100mhzsteps
> bogomips : 3829.72
> clflush size : 64
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2008-01-17 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 16:13 Cannot boot xen DomU > 2.6.23.1 xming
2008-01-17 17:15 ` Jeremy Fitzhardinge [this message]
2008-01-17 19:13 ` xming
2008-01-18 7:32 ` Jeremy Fitzhardinge
2008-01-18 12:38 ` xming
2008-01-18 16:19 ` Jeremy Fitzhardinge
2008-01-18 16:56 ` xming
2008-01-18 17:26 ` Jeremy Fitzhardinge
2008-01-20 13:08 ` xming
2008-01-20 18:37 ` Jeremy Fitzhardinge
2008-01-20 19:29 ` xming
2008-01-20 23:52 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=478F8D22.60004@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xmingske@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox