Alexander Graf writes:
> On 19.06.2013, at 23:49, Anthony Liguori wrote:
>
>> Alexander Graf writes:
>>
>>> On 19.06.2013, at 22:40, Anthony Liguori wrote:
>>>
The creatively named reg field is a hypervisor assigned global
identifier for a virtual device. Despite the fact that no de
On Wed, 2013-06-19 at 23:28 +0200, Alexander Graf wrote:
> On 19.06.2013, at 22:40, Anthony Liguori wrote:
>
> > The creatively named reg field is a hypervisor assigned global
> > identifier for a virtual device. Despite the fact that no device
> > is assigned a reg of 0, guests still use it to r
On 19.06.2013, at 23:49, Anthony Liguori wrote:
> Alexander Graf writes:
>
>> On 19.06.2013, at 22:40, Anthony Liguori wrote:
>>
>>> The creatively named reg field is a hypervisor assigned global
>>> identifier for a virtual device. Despite the fact that no device
>>> is assigned a reg of 0,
Alexander Graf writes:
> On 19.06.2013, at 22:40, Anthony Liguori wrote:
>
>> The creatively named reg field is a hypervisor assigned global
>> identifier for a virtual device. Despite the fact that no device
>> is assigned a reg of 0, guests still use it to refer to early
>> console.
>>
>> Ins
On 19.06.2013, at 22:40, Anthony Liguori wrote:
> The creatively named reg field is a hypervisor assigned global
> identifier for a virtual device. Despite the fact that no device
> is assigned a reg of 0, guests still use it to refer to early
> console.
>
> Instead of handling this in the VTY
The creatively named reg field is a hypervisor assigned global
identifier for a virtual device. Despite the fact that no device
is assigned a reg of 0, guests still use it to refer to early
console.
Instead of handling this in the VTY device, handle this in the VIO
bus since this is ultimately ab
