[Xen-devel] [PATCH] libxc: remove stale error check for domain size in xc_sr_save_x86_hvm.c

2017-09-26 Thread Juergen Gross
Long ago domains to be saved were limited to 1TB size due to the migration stream v1 limitations which used a 32 bit value for the PFN and the frame type (4 bits) leaving only 28 bits for the PFN. Migration stream V2 uses a 64 bit value for this purpose, so there is no need to refuse saving (or mi

Re: [Xen-devel] [PATCH] libxc: remove stale error check for domain size in xc_sr_save_x86_hvm.c

2017-09-26 Thread Andrew Cooper
On 26/09/2017 08:33, Juergen Gross wrote: > Long ago domains to be saved were limited to 1TB size due to the > migration stream v1 limitations which used a 32 bit value for the > PFN and the frame type (4 bits) leaving only 28 bits for the PFN. > > Migration stream V2 uses a 64 bit value for this p

Re: [Xen-devel] [PATCH] libxc: remove stale error check for domain size in xc_sr_save_x86_hvm.c

2017-09-26 Thread Juergen Gross
On 26/09/17 09:41, Andrew Cooper wrote: > On 26/09/2017 08:33, Juergen Gross wrote: >> Long ago domains to be saved were limited to 1TB size due to the >> migration stream v1 limitations which used a 32 bit value for the >> PFN and the frame type (4 bits) leaving only 28 bits for the PFN. >> >> Mig

Re: [Xen-devel] [PATCH] libxc: remove stale error check for domain size in xc_sr_save_x86_hvm.c

2017-09-26 Thread Juergen Gross
On 26/09/17 09:41, Andrew Cooper wrote: > On 26/09/2017 08:33, Juergen Gross wrote: >> Long ago domains to be saved were limited to 1TB size due to the >> migration stream v1 limitations which used a 32 bit value for the >> PFN and the frame type (4 bits) leaving only 28 bits for the PFN. >> >> Mig