> And it looked suspicious that it was intermittent before. Anyway - likely a > firmware problem (for which upstream we recently added a workaround), > but impossible to tell for sure without a full hypervisor log at at least > "info" > log level.
What I posted was output with loglvl & guest_loglvl already at "=all". Isn't "all" more verbose already than "info"? Re the fix, which upstream was that - Xen or kernel? Do you have a commit reference? LT -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
