Re: [Xen-users] xen 2.0.7 on VIA C3 (EPIA)

[Rafael Ferreira <lists@xxxxxxxxxx>]

Yeah I could not agree with you more. With power consumption becoming
more of a hot topic I believe that processor such as the C3 will become
even more relevant... even for production environments. 

- raf

On Mon, 2005-10-03 at 15:02 +0200, Harald Brass wrote:
> I'm with you as well. Tried desperately to transfer Adam's patch to xen 
> 2.0.6 and got the exact same "unknown interrupt" error.
> 
> Xen memory management has been completely rewritten since xen 2.0.1. It 
> seems that we definitely need some developer with asm skills and deep 
> insight into xen's architecture (both of which I do not have) to enable 
> 4kb pages support for xen 2.0.6 onwards.
> 
> It should be worth it, since it could open Xen to a wider usage besides 
> the high end server field. VIA Samuel C3 allows reliable low-energy, 
> fanless operation. With xen and such a mainboard, you can host 
> groupware, proxy and firewall services on one single fanless computer, 
> each of these services running completely separated in three xen 
> domains. This is an ideal solution for small workgroups or family 
> offices. We use xen 2.0.1 with Adam's patch for that purpose.
> 
> regards
> 
> > I'm on the same boat with a VIA Samuel C3. I can't get 2x  patched and
> > the 3.0 series won't boot. 
> >
> > I don't think the C3's are high in the priority list but It would be
> > awesome if one of the developers gave them some love one of these days. 
> >
> > - raf
> >
> > On Sun, 2005-10-02 at 14:58 -0700, glen martin wrote:
> >   
> >> On Sept 3 13:05:37, Chris Brookes <cbrookes@xxxxxxxxx 
> >> <mailto:cbrookes%40gmail.com>> wrote:
> >>
> >>     
> >>> Has anyone tried to get Xen 2.0.7 booting on a VIA EPIA board with a
> >>> VIA C3 CPU?
> >>>       
> >> yes, but not successfully. :)
> >>
> >>     
> >>> I know some of the EPIA mainboards have a CPU with
> >>> "features" (4kb pages and no cmov instruction) that require the patch
> >>> Adam Sulmicki put together for 2.0.0 and 2.0.1
> >>> (http://lists.xensource.com/archives/html/xen-devel/2004-12/txt8D0L7RWimG.txt),
> >>>       
> >> Mine is a VIA EPIA PD6000, regarding which /proc/cpuinfo says:
> >>   machine:/proc# more /proc/cpuinfo
> >>   processor       : 0
> >>   vendor_id       : CentaurHauls
> >>   cpu family      : 6
> >>   model           : 7
> >>   model name      : VIA Samuel 2
> >>   stepping        : 3
> >>   cpu MHz         : 601.505
> >>   cache size      : 64 KB
> >>   fdiv_bug        : no
> >>   hlt_bug         : no
> >>   f00f_bug        : no 
> >>   coma_bug        : no
> >>   fpu             : yes
> >>   fpu_exception   : yes
> >>   cpuid level     : 1
> >>   wp              : yes
> >>   flags           : fpu de tsc msr cx8 mtrr pge mmx 3dnow
> >>   bogomips        : 1187.84
> >>
> >>     
> >>> and I have managed to patch, compile and boot a NetBSD dom0
> >>> sucessfully with this version.
> >>>       
> >> I found this patch didn't go in cleanly (any more?) into testing (there 
> >> were a
> >> couple of changes to semi-magic constants in the codebase), and so I had 
> >> to 
> >> hand-insert a couple of chunks ... I won't post patches just yet in case 
> >> my 
> >> asm skills are as rusty as others' in the thread purport to be. :)
> >>
> >> ...
> >>     
> >>> (which is a great step forward from the immediate reboot
> >>> without it), 
> >>>       
> >> quite :)
> >>
> >>     
> >>> however the whole thing halts with "(XEN) Unknown
> >>> interrupt" just after "XEN) System RAM: 509MB (521852kB)".
> >>>       
> >> I've gotten to this failure now (well, I have less RAM). 
> >>
> >> So it's been a month since Chris posted orginally ... has anyone
> >> made any progress beyond this point, or is this breaking new ground?
> >>
> >> Cheers,
> >>
> >>     
> >
> >
> > _______________________________________________
> > 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
> 


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