Re: [Xen-devel] [v5][PATCH 11/16] tools/libxl: detect and avoid conflicts with RDM

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Tue, Jul 07, 2015 at 12:51:48PM +0100, Ian Jackson wrote:
> Tiejun Chen writes ("[v5][PATCH 11/16] tools/libxl: detect and avoid 
> conflicts with RDM"):
> > While building a VM, HVM domain builder provides struct hvm_info_table{}
> > to help hvmloader. Currently it includes two fields to construct guest
> > e820 table by hvmloader, low_mem_pgend and high_mem_pgend. So we should
> > check them to fix any conflict with RDM.
> ...
> > Note later we need to provide a parameter to set that predefined boundary
> > dynamically.
> 
> Why ...
> 
> > +libxl_device_rdm = Struct("device_rdm", [
> > +    ("start", uint64),
> > +    ("size", uint64),
> > +    ("flag", libxl_rdm_reserve_flag),
> > +    ])
> > +
> >  libxl_device_dtdev = Struct("device_dtdev", [
> >      ("path", string),
> >      ])
> > @@ -592,6 +598,7 @@ libxl_domain_config = Struct("domain_config", [
> >      ("disks", Array(libxl_device_disk, "num_disks")),
> >      ("nics", Array(libxl_device_nic, "num_nics")),
> >      ("pcidevs", Array(libxl_device_pci, "num_pcidevs")),
> > +    ("rdms", Array(libxl_device_rdm, "num_rdms")),
> >      ("dtdevs", Array(libxl_device_dtdev, "num_dtdevs")),
> >      ("vfbs", Array(libxl_device_vfb, "num_vfbs")),
> >      ("vkbs", Array(libxl_device_vkb, "num_vkbs")),
> 
> ... does this need to be exposed at the libxl API ?  Are we expecting
> that callers will want to specify the rdms set explicitly ?
> 

Yes according to their design -- so that they can migrate guests among
hosts which have different RDM ranges by setting RDM parameter to the
super set of all RDM regions on all hosts.

Wei.

> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel