On 12/8/21 14:15, Daniel P. Berrangé wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> On Wed, Dec 08, 2021 at 01:32:48PM +0100, Philipp Klocke wrote:
>> On
On Wed, Dec 08, 2021 at 01:32:48PM +0100, Philipp Klocke wrote:
> On 12/8/21 12:09, Peter Krempa wrote:
> > CAUTION: This email originated from outside of the organization. Do not
> > click links or open attachments unless you recognize the sender and know
> > the content is safe.
> >
> >
> > O
On 12/8/21 12:09, Peter Krempa wrote
On Wed, Dec 08, 2021 at 10:30:27 +, Philipp Klocke wrote:
Hi,
the command
virsh qemu-monitor-command ubuntu_vm --hmp --cmd "info tlb"
fails with "error: Unable to encode message payload".
I found a bugtracker entry for a similiar error [1], but
On 12/8/21 12:09, Peter Krempa wrote:
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
On Wed, Dec 08, 2021 at 10:30:27 +, Philipp Klocke wrote:
Hi,
the command
virs
On Wed, Dec 08, 2021 at 10:30:27 +, Philipp Klocke wrote:
> Hi,
>
> the command
> virsh qemu-monitor-command ubuntu_vm --hmp --cmd "info tlb"
> fails with "error: Unable to encode message payload".
>
> I found a bugtracker entry for a similiar error [1], but I don't if this is
> the same
Hi,
the command
virsh qemu-monitor-command ubuntu_vm --hmp --cmd "info tlb"
fails with "error: Unable to encode message payload".
I found a bugtracker entry for a similiar error [1], but I don't if this is the
same error (message too large). I also don't know how large an info tlb message
i
