Re: [Xen-devel] VMX status daily report Nov. 3

[Ewan Mellor <ewan@xxxxxxxxxxxxx>]

On Thu, Nov 03, 2005 at 09:35:37AM -0600, Khoa Huynh wrote:

> 
> "Shi, Kuiliang" <kuiliang.shi@xxxxxxxxx> wrote on 11/03/2005 03:14:46 AM:
> 
> >
> >
> > We have test latest xen (ChangeSet 7608) on VT platform with Intel 915
> > chipset and Here is the test summary:
> >
> > IA32:
> >     Build&Boot SMP xen0 without problem
> >     Can startup XenU with different configuration
> >
> >     IA32 issues contain:
> >     VMX can not be created
> >
> >
> > IA32E:
> >     Build&Boot SMP xen0 without problem
> >     Can startup XenU with different configuration
> >
> >    IA32E issues contain:
> >     VMX can not be created.
> >
> 
> I think you need this patch (also from Intel) to create
> a VMX domain:
> 
> diff -r ae2e13795c63 tools/python/xen/xend/server/DevController.py
> --- a/tools/python/xen/xend/server/DevController.py     Tue Nov  1
> 19:13:06 2005 +0100
> +++ b/tools/python/xen/xend/server/DevController.py     Wed Nov  2
> 14:38:31 2005 +0800
> @@ -57,6 +57,8 @@
>           @return The ID for the newly created device.
>           """
>           (devid, back, front) = self.getDeviceDetails(config)
> +        if devid == 0:
> +            return devid
> 
>           self.writeDetails(config, devid, back, front)
> 
> I have not seen this patch applied to the latest xen-unstable tree
> yet.  I hope it will be applied soon as this works for me.  Thanks.

This patch breaks vifs for everyone else (vif IDs are allocated from 0).  I
have a replacement ready and waiting to go.

Ewan.

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