Works!
Thanks, this looks like it may have just been the hvc0 vs xvc0 console spec.
Although I'm not sure why with the xvc0 console the network was still
non-functional. I'll have to play with the boot options and find
out
what specific item breaks it.
Thanks for the suggestion.
-Bruce
On Mon, Oct 12, 2009 at 7:10 AM, Konrad Rzeszutek Wilk
<
konrad.wilk@xxxxxxxxxx> wrote:
> On Sun, Oct 11, 2009 at 10:21:12PM -0700, Bruce Edge wrote:
>> Does the xen/master dom0 kernel just not currrently support the i7
>> with x58 chipset?
>
> No idea.
>
> But can you add some more verbose logging information?
>
> Add this in the kernel /xen.gz line: "guest_loglvl=all"
> and in the 'module /vmlinuz" add this:
> "earlyprintk=xen irqpoll console=hvc0 loglevel=10 debug"
>
> If 'quiet' shows in the line, remove it.
>
> .. snip ..
>
>> CONFIG_XEN_S3=y
>> CONFIG_XEN_GNTDEV=y
>
> What is the CONFIG_NR_CPUS set to? Try with
CONFIG_NR_CPUS=64
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxhttp://lists.xensource.com/xen-devel