On 11.02.2019 16:40, Andrea Bolognani wrote:
> On Mon, 2019-02-11 at 08:14 +, Nikolay Shirokovskiy wrote:
>> On 08.02.2019 17:34, Andrea Bolognani wrote:
>>> Even with that fixed, while your code prevents a element
>>> associated to the isa-debugcon to be automatically created, it
>>> doesn
On Mon, Feb 11, 2019 at 02:40:55PM +0100, Andrea Bolognani wrote:
> On Mon, 2019-02-11 at 08:14 +, Nikolay Shirokovskiy wrote:
> > On 08.02.2019 17:34, Andrea Bolognani wrote:
> > > Even with that fixed, while your code prevents a element
> > > associated to the isa-debugcon to be automaticall
On Mon, 2019-02-11 at 08:14 +, Nikolay Shirokovskiy wrote:
> On 08.02.2019 17:34, Andrea Bolognani wrote:
> > Even with that fixed, while your code prevents a element
> > associated to the isa-debugcon to be automatically created, it
> > doesn't prevent something like
> >
> >
> >
> >
On 08.02.2019 17:34, Andrea Bolognani wrote:
> On Thu, 2019-02-07 at 14:31 +0300, Nikolay Shirokovskiy wrote:
> [...]
>> @@ -4392,6 +4393,9 @@ virDomainDefAddConsoleCompat(virDomainDefPtr def)
>>
>> switch ((virDomainChrSerialTargetType) def->serials[0]->targetType)
>> {
>>
On Thu, 2019-02-07 at 14:31 +0300, Nikolay Shirokovskiy wrote:
[...]
> @@ -4392,6 +4393,9 @@ virDomainDefAddConsoleCompat(virDomainDefPtr def)
>
> switch ((virDomainChrSerialTargetType) def->serials[0]->targetType) {
> case VIR_DOMAIN_CHR_SERIAL_TARGET_TYPE_ISA:
> +i
This interface can be used for example by firmware to print
debug messages. Here is domain xml example:
Add checks to make sure this new serial type won't be reported
as back-compat console.
Signed-off-by: Nikolay Shirokovskiy
---
docs/formatdomain.html.
