On Tue, Jul 05, 2016 at 01:41:50PM +0100, Dr. David Alan Gilbert wrote:
> * Michael S. Tsirkin (m...@redhat.com) wrote:
> > On Tue, Jul 05, 2016 at 12:59:42PM +0200, Paolo Bonzini wrote:
> > >
> > >
> > > On 05/07/2016 12:06, Michael S. Tsirkin wrote:
> > > > > -m 2G,slots=16,maxmem=2T
> > >
* Michael S. Tsirkin (m...@redhat.com) wrote:
> On Tue, Jul 05, 2016 at 12:59:42PM +0200, Paolo Bonzini wrote:
> >
> >
> > On 05/07/2016 12:06, Michael S. Tsirkin wrote:
> > > > -m 2G,slots=16,maxmem=2T
> > > >
> > > > On a host with a 39bit physaddress limit do you error
> > > > on that or
On Tue, Jul 05, 2016 at 01:46:58PM +0200, Paolo Bonzini wrote:
>
>
> On 05/07/2016 13:09, Michael S. Tsirkin wrote:
> > > How do you handle migration in the above scenario from say 46bit host to
> > > 39bit host, where the firmware has mapped (while running on the source)
> > > a 64-bit BAR above
On Tue, Jul 05, 2016 at 10:49:48AM +0100, Dr. David Alan Gilbert wrote:
> * Daniel P. Berrange (berra...@redhat.com) wrote:
> > On Mon, Jul 04, 2016 at 08:16:03PM +0100, Dr. David Alan Gilbert (git)
> > wrote:
> > > From: "Dr. David Alan Gilbert"
> > >
> > > QEMU sets the guests physical address
On 05/07/2016 13:09, Michael S. Tsirkin wrote:
> > How do you handle migration in the above scenario from say 46bit host to
> > 39bit host, where the firmware has mapped (while running on the source)
> > a 64-bit BAR above the destination's maximum physical address?
>
> Again management would spe
On Tue, Jul 05, 2016 at 12:59:42PM +0200, Paolo Bonzini wrote:
>
>
> On 05/07/2016 12:06, Michael S. Tsirkin wrote:
> > > -m 2G,slots=16,maxmem=2T
> > >
> > > On a host with a 39bit physaddress limit do you error
> > > on that or not? I think oVirt is currently doing something
> > > simila
On 05/07/2016 12:06, Michael S. Tsirkin wrote:
> > -m 2G,slots=16,maxmem=2T
> >
> > On a host with a 39bit physaddress limit do you error
> > on that or not? I think oVirt is currently doing something
> > similar to that, but I'm trying to get confirmation.
>
> That would only be a proble
On Tue, Jul 05, 2016 at 11:13:26AM +0100, Dr. David Alan Gilbert wrote:
> * Michael S. Tsirkin (m...@redhat.com) wrote:
> > On Tue, Jul 05, 2016 at 10:33:25AM +0100, Dr. David Alan Gilbert wrote:
> > > * Michael S. Tsirkin (m...@redhat.com) wrote:
> > > > On Mon, Jul 04, 2016 at 08:16:03PM +0100, D
* Michael S. Tsirkin (m...@redhat.com) wrote:
> On Tue, Jul 05, 2016 at 10:33:25AM +0100, Dr. David Alan Gilbert wrote:
> > * Michael S. Tsirkin (m...@redhat.com) wrote:
> > > On Mon, Jul 04, 2016 at 08:16:03PM +0100, Dr. David Alan Gilbert (git)
> > > wrote:
> > > > From: "Dr. David Alan Gilbert"
On Tue, Jul 05, 2016 at 10:33:25AM +0100, Dr. David Alan Gilbert wrote:
> * Michael S. Tsirkin (m...@redhat.com) wrote:
> > On Mon, Jul 04, 2016 at 08:16:03PM +0100, Dr. David Alan Gilbert (git)
> > wrote:
> > > From: "Dr. David Alan Gilbert"
> > >
> > > QEMU sets the guests physical address bit
* Daniel P. Berrange (berra...@redhat.com) wrote:
> On Mon, Jul 04, 2016 at 08:16:03PM +0100, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > QEMU sets the guests physical address bits to 40; this is wrong
> > on most hardware, and can be detected by the guest.
> >
On Mon, Jul 04, 2016 at 08:16:03PM +0100, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> QEMU sets the guests physical address bits to 40; this is wrong
> on most hardware, and can be detected by the guest.
> It also stops you using really huge multi-TB VMs.
>
> Red Hat
* Michael S. Tsirkin (m...@redhat.com) wrote:
> On Mon, Jul 04, 2016 at 08:16:03PM +0100, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > QEMU sets the guests physical address bits to 40; this is wrong
> > on most hardware, and can be detected by the guest.
> > It a
On Mon, Jul 04, 2016 at 08:16:03PM +0100, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> QEMU sets the guests physical address bits to 40; this is wrong
> on most hardware, and can be detected by the guest.
> It also stops you using really huge multi-TB VMs.
>
> Red Hat
From: "Dr. David Alan Gilbert"
QEMU sets the guests physical address bits to 40; this is wrong
on most hardware, and can be detected by the guest.
It also stops you using really huge multi-TB VMs.
Red Hat has had a patch, that Andrea wrote, downstream for a couple
of years that reads the hosts v
15 matches
Mail list logo
