On Fri, Dec 05, 2014 at 10:42:27AM +, Andrew Cooper wrote:
> On 05/12/14 09:54, Ian Campbell wrote:
> > On Fri, 2014-12-05 at 10:49 +0100, Tim Deegan wrote:
> >> At 09:20 + on 05 Dec (1417767654), Jan Beulich wrote:
> >> On 04.12.14 at 18:25, wrote:
> Potential feature flags, base
On 04/12/14 17:25, Tim Deegan wrote:
> 'HVM' 'PVH'
> 64bit hypercalls Yes Yes
> 32bit hypercalls Yes No
> Paging assistance Yes Yes
> ioreq-servers Yes No
Perhaps, but no default on
On 05/12/14 09:54, Ian Campbell wrote:
> On Fri, 2014-12-05 at 10:49 +0100, Tim Deegan wrote:
>> At 09:20 + on 05 Dec (1417767654), Jan Beulich wrote:
>> On 04.12.14 at 18:25, wrote:
Potential feature flags, based on whiteboard notes at the session.
Things that are 'Yes' in both
On Fri, 2014-12-05 at 10:49 +0100, Tim Deegan wrote:
> At 09:20 + on 05 Dec (1417767654), Jan Beulich wrote:
> > >>> On 04.12.14 at 18:25, wrote:
> > > Potential feature flags, based on whiteboard notes at the session.
> > > Things that are 'Yes' in both columns might not need actual flags :)
At 09:20 + on 05 Dec (1417767654), Jan Beulich wrote:
> >>> On 04.12.14 at 18:25, wrote:
> > Potential feature flags, based on whiteboard notes at the session.
> > Things that are 'Yes' in both columns might not need actual flags :)
> >
> > 'HVM' 'PVH'
> > 64bit hyp
>>> On 04.12.14 at 18:25, wrote:
> Potential feature flags, based on whiteboard notes at the session.
> Things that are 'Yes' in both columns might not need actual flags :)
>
> 'HVM' 'PVH'
> 64bit hypercalls Yes Yes
> 32bit hypercalls Yes No
I
Hi all,
At the Hackathon in Rackspace we discussed a plan to tidy up the
hypervisor side of PVH code so that 'PVH' stops being a separate guest
type, becoming instead a HVM guest with various features disabled (and
one or two other tweaks).
Although I had hoped to work on that in the meantime, v
