RE: [Xen-users] Moved from Xen 2 to Xen 3... some questions..

["Petersson, Mats" <Mats.Petersson@xxxxxxx>]

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Steve Kemp
> Sent: 01 June 2006 12:35
> To: george@xxxxxxxxxxxx
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Moved from Xen 2 to Xen 3... some questions..
> 
> On Thu, Jun 01, 2006 at 12:25:35PM +0100, George Styles wrote:
> 
> > Ive got it working, but I want to ask a couple of questions 
> about it.
> 
>   I can't help with all of them, but I'll answer a couple of 
> your  questions.
> 
> >    1. There no longer seems to be a seperate DomU and Dom0 
> built when I build
> >    from source. Is this the new policy? this would suit me, 
> as I always used
> >    Xen0 kernels in my guest domains anyway.
> 
>   Yes.  You can still build seperate kernels if you wish, but 
> it is no  longer the default.
> 
> 
> >    5. Is there ANY way to see the pre-linux-kernel messages 
> from boot (the
> >    messages from the hypervisor)? they scroll past so 
> quickly I cannot read
> >    them, then if I get a kernel panic when the Linux kernel 
> starts, I cannot
> >    see what the hypervisor was saying. It turned out to be 
> lack of sata
> >    drivers in the kernel (they were modules), but that was 
> guesswork. Im sure
> >    the Xen boot messages would tell me what hardware it had 
> picked up.
> 
>   xm dmesg
> 
> >    6. When I was trying to build a custom kernel (with the 
> sata drivers in),
> >    i tried the usual
> >    make ARCH=xen menuconfig
> >    in the linux source dir, but it gave an error (something 
> about no such
> >    target or somesuch).
> >    Is this no longer nescesary? it worked OK when I 
> ommitted the ARCH=xen,
> >    but I didnt proceed as I wasnt sure if it would compile 
> in the Xen
> >    stuff... whats going on???
> 
>   Yes Xen is no longer a sub-arch, and has been merged into the normal
>   system.  So you can exclude it as you did with safety.

I think technically, you should have said "Xen is NOW A SUBARCH, no
longer a separate architecture", so you need to set the
"Subarchitecture" inside the x86 processor choice in the Linux .config
(which will be done automagically if you use Xen from the normal source
files). 

--
Mats

> 
> Steve
> --
> http://www.steve.org.uk/
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users