24 messages in com.xensource.lists.xen-develRe: [Xen-devel] 3.1.x and 3.2.x releases
FromSent OnAttachments
Keir Fraser19 Dec 2007 08:00 
Dan Magenheimer19 Dec 2007 09:22 
John Levon19 Dec 2007 10:34 
You, Yongkang19 Dec 2007 19:58 
John Levon19 Dec 2007 21:02 
Keir Fraser20 Dec 2007 02:25 
Dan Magenheimer26 Dec 2007 11:52 
Keir Fraser26 Dec 2007 15:07 
S.Çağlar Onur27 Dec 2007 15:37 
Keir Fraser28 Dec 2007 00:38 
S.Çağlar Onur28 Dec 2007 02:16 
Keir Fraser28 Dec 2007 05:16 
John Levon28 Dec 2007 06:55 
Keir Fraser28 Dec 2007 07:18 
Daniel P. Berrange28 Dec 2007 07:46 
Keir Fraser28 Dec 2007 08:00 
Dan Magenheimer28 Dec 2007 14:51 
S.Çağlar Onur28 Dec 2007 15:04 
Ryan Scott28 Dec 2007 17:17 
Keir Fraser29 Dec 2007 01:18 
Keir Fraser29 Dec 2007 01:21 
S.Çağlar Onur01 Jan 2008 08:31 
Dan Magenheimer03 Jan 2008 09:23 
Keir Fraser06 Jan 2008 14:50 
Subject:Re: [Xen-devel] 3.1.x and 3.2.x releases
From:Keir Fraser (Keir@cl.cam.ac.uk)
Date:12/29/2007 01:21:12 AM
List:com.xensource.lists.xen-devel

On 29/12/07 09:18, "Keir Fraser" <Keir@cl.cam.ac.uk> wrote:

I tried something a bit more dramatic. In arch/x86/hvm/hvm.c, in the case HVM_PARAM_TIMER_MODE, I changed the "goto param_fail;" to "panic("BAD HVMPTM");" and added "timer_mode=6" in the config file, but the panic was not triggered. But the same code/config change in xen-unstable DOES panic.

Am I missing something in configuring this for xen-3.1-testing? Or perhaps the 3.1 patch just isn't passing timer_mode down properly?

Line 1542 of XendDomainInfo.py should be passing the mode down to Xen. Presumably that is not working.

Also, I have a suspicion that timer_mode won't survive a save/restore of an HVM guest, either in unstable or in 3.1-testing. I haven't confirmed this though. But there's no code to do it, so unless it happens automagically...

-- Keir

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