[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] Xen 3.0.4.1 AMD-V HVM


  • To: "Holger" <Age_M@xxxxxx>
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Thu, 7 Jun 2007 18:12:41 +0200
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 07 Jun 2007 09:11:20 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcepEs9GBwVWUnRhT9ieeNC0ddrMEgAC3WHw
  • Thread-topic: [Xen-users] Xen 3.0.4.1 AMD-V HVM

 

> -----Original Message-----
> From: Holger [mailto:Age_M@xxxxxx] 
> Sent: 07 June 2007 15:47
> To: Petersson, Mats
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Xen 3.0.4.1 AMD-V HVM
> 
> 
> Hi there :-D
> 
> I don't believe it. your explanation brought me up to an idea!
> if the g stepping cpu is the first cpu that support deactivation of 
> AMD-V, what would happen if i use a bios version that doesn' 
> recognize 
> the G-step cpu :-p
> 
> voila.. bios version F2 activates the AMD-V feature -> I 
> don't believe it.
> I am just worrying what would happen to my system!? turning off 
> speedstepping should do it, right?

Well, you shouldn't be able to use "PownerNow!" on a the new procesor
with the old BIOS, but other than that, it shouldn't cause any noticable
problems, unless there's some new bugs in the new processor that
requires special fixes (and if there is, they are probably fairly
obscure, so unlikely to occur on "average" code). 

Can you try running Xen 3.1 with the newer BIOS and see if says "AMD-V
locked by BIOS" when you attempt that? Unfortunately, the older version
of Xen doesn't "know" the "lock" bit... 

--
Mats
> 
> Greetz Age_M
> 
> Petersson, Mats schrieb:
> >  
> >
> >   
> >> -----Original Message-----
> >> From: Holger [mailto:Age_M@xxxxxx] 
> >> Sent: 07 June 2007 14:59
> >> To: Petersson, Mats
> >> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> >> Subject: Re: [Xen-users] Xen 3.0.4.1 AMD-V HVM
> >>
> >>
> >> Hi there again ;)
> >>
> >> Thanks for the reply, I think I get it now. So the only 
> >> problem is the 
> >> Mainboard. Do you think I am in a position to expect 
> Gigabyte to fix 
> >> this? Is it my right to say "This is an AM2 mainboard, so 
> you have to 
> >> build this feature into the bios?". I mean, virtualization 
> is a key 
> >> feature of AM2, right?
> >>     
> >
> > Well, the KEY feature to processors that go into an AM2 is 
> the ability
> > to use DDR2 memory (which for the same performance is less expensive
> > than DDR). It just so happens that we (AMD) choose to implement
> > virtualization features into the same product upgrade 
> cycle, so AM2 is
> > an easy way to explain which processors have AMD-V or not.
> >
> > And the other key point here is that before Rev G, it was 
> very difficult
> > to disable AMD-V. In Rev G, it's one bit which is "sticky" 
> (sticky means
> > that it can't be reset without resetting the entire 
> processor) in one
> > register to disable AMD-V. 
> >
> > There is ABSOLUTELY no reason why this shouldn't be fixable 
> in the BIOS.
> >
> >
> >   
> >> I really hope, that I don't have to buy a new mainboard again :-/
> >>     
> >
> > Yes, I agree - although I would also say that if you bought 
> the system
> > with the intention of running AMD-V, then it would be fair 
> to say that
> > you should be able to take the motherboard back to the shop with a
> > complaint that "it doesn't do what it should be able to" 
> based on not
> > being able to run AMD-V. [Being stricly legal, this is 
> possibly beyond
> > what the legal definition of "fit for purpose" covers if you didn't
> > explicitly say to the retailer that you NEED the AMD-V 
> feature - but I
> > still would attempt to get a replacement it on these 
> grounds before just
> > buying a new motherboard]. 
> >
> > --
> > Mats
> >   
> >> Thanks for your detailed explanations ;)
> >> Greetz Holger
> >>
> >> Petersson, Mats schrieb:
> >>     
> >>>  
> >>>
> >>>   
> >>>       
> >>>> -----Original Message-----
> >>>> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> >>>> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Holger
> >>>> Sent: 07 June 2007 14:30
> >>>> To: xen-users@xxxxxxxxxxxxxxxxxxx
> >>>> Subject: Re: [Xen-users] Xen 3.0.4.1 AMD-V HVM
> >>>>
> >>>> Hello Mats,
> >>>>
> >>>> I think I didn't really get the point in your statement.
> >>>>
> >>>> "please wait until the processors are available"
> >>>>     
> >>>>         
> >>> This was in reference to the NEW processors that are not 
> yet on the
> >>> market - I can't really tell the general public about details of
> >>> processors that are not yet available - at least not if I want to
> >>> continue working for AMD... 
> >>>   
> >>>       
> >>>> What processors are you talking about?! My AMD AM2 3600+ 
> X2 (65nm) 
> >>>> already has the AMD-V feature, right?!? And the Mainboard 
> >>>>         
> >> already has 
> >>     
> >>>> turned off this AMD-V feature, but I want to turn it ON 
> >>>>         
> >> again, right?!
> >>     
> >>>>     
> >>>>         
> >>> Aha! 65 nm is the Rev G model. I'm not sure, but I think 
> >>>       
> >> Rev G has the
> >>     
> >>> ability to disable AMD-V. But your BIOS really should 
> have a way to
> >>> ENABLE it if that's the case. [Most of the processors 
> >>>       
> >> currently on the
> >>     
> >>> market are Rev F - I only saw the first Rev G myself the 
> other day,
> >>> although I knew of their existance a long time ago]
> >>>   
> >>>       
> >>>> So, what do I have to do to get HVM support? New CPU? New 
> >>>> Mainboard?? Or 
> >>>> should I completely switch to Intel Core2Duo?
> >>>>     
> >>>>         
> >>> I'd suggest if Gigabyte isn't helping you (soon), you 
> >>>       
> >> should invest in a
> >>     
> >>> different motherbaord. 
> >>>
> >>>   
> >>>       
> >>>> I am completely irritated now :-p
> >>>>     
> >>>>         
> >>> That wasn't my intention. Sorry for that. 
> >>>
> >>>   
> >>>       
> >>>> Greetz Holger
> >>>>
> >>>>
> >>>>
> >>>> Petersson, Mats wrote:
> >>>>     
> >>>>         
> >>>>>  
> >>>>>
> >>>>>   
> >>>>>       
> >>>>>           
> >>>>>> -----Original Message-----
> >>>>>> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> >>>>>> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> >>>>>> Christian Horn
> >>>>>> Sent: 07 June 2007 09:14
> >>>>>> To: Tony Hoyle
> >>>>>> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> >>>>>> Subject: Re: [Xen-users] Xen 3.0.4.1 AMD-V HVM
> >>>>>>
> >>>>>> On Wed, Jun 06, 2007 at 08:02:38PM +0100, Tony Hoyle wrote:
> >>>>>>     
> >>>>>>         
> >>>>>>             
> >>>>>>> Yes.  Some manufacturers actually do this (especially 
> >>>>>>>       
> >>>>>>>           
> >>>>>>>               
> >>>>>> laptops). It's 
> >>>>>>     
> >>>>>>         
> >>>>>>             
> >>>>>>> possible a bios upgrade will reenable the option.
> >>>>>>>       
> >>>>>>>           
> >>>>>>>               
> >>>>>> Are you sure manufaturers can disable this for AM2-boards?
> >>>>>> For intel its well known, but for AMD..
> >>>>>>     
> >>>>>>         
> >>>>>>             
> >>>>> I'll probably be told off for explaining this :-(
> >>>>>
> >>>>> Without going into "secrets", yes there is a way to "turn 
> >>>>>           
> >> off" AMD-V
> >>     
> >>>>> with the BIOS, and no, you can't ask for more details 
> >>>>>       
> >>>>>           
> >>>> unless you have an
> >>>>     
> >>>>         
> >>>>> NDA with AMD. It's also not possible to "re-enable it". 
> >>>>>           
> >> Although the
> >>     
> >>>>> BIOS _SHOULD_ allow the enabling/disabling to be "user 
> >>>>>           
> >> selectable".
> >>     
> >>>>> Future versions have a more well-documented way to do 
> this. Again,
> >>>>> unless you have an NDA with AMD, please wait until the 
> >>>>>       
> >>>>>           
> >>>> processors are
> >>>>     
> >>>>         
> >>>>> available, and there will be more details available to everyone.
> >>>>>
> >>>>> --
> >>>>> Mats
> >>>>>   
> >>>>>       
> >>>>>           
> >>>>>> Christian
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> 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
> >>>>
> >>>>
> >>>>
> >>>>     
> >>>>         
> >>>   
> >>>       
> >>
> >>
> >>     
> >
> >
> >
> > _______________________________________________
> > 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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.