On Mon, Aug 19, 2019 at 01:30:06PM +0100, Daniel P. Berrangé wrote:
> On Mon, Aug 19, 2019 at 12:15:48PM +0000, Allen, John wrote:
> > On Mon, Aug 19, 2019 at 12:24:43PM +0100, Daniel P. Berrangé wrote:
> > > On Wed, Aug 14, 2019 at 01:30:26PM +, Allen, John wrote:
>
On Mon, Aug 19, 2019 at 12:24:43PM +0100, Daniel P. Berrangé wrote:
> On Wed, Aug 14, 2019 at 01:30:26PM +0000, Allen, John wrote:
> > After upgrading to v5.6.0, starting libvirtd fails with the following
> > message
> > in journalctl -xe:
> >
> > libvi
After upgrading to v5.6.0, starting libvirtd fails with the following message
in journalctl -xe:
libvirtd[186338]: internal error: Some activation file descriptors are unclaimed
5b8569dd6e284b9159c701e8bffafb196983fc4a introduces the message. The commit
message indicates that systemd version 227
Gentle reminder. Any comments on this patch?
Thanks,
John
On Mon, Apr 15, 2019 at 09:43:07AM -0500, Allen, John wrote:
> If a bitmap of a shorter length than the data buffer is passed to
> virBitmapToDataBuf, it will read off the end of the bitmap and copy junk
> into the returned bu
If a bitmap of a shorter length than the data buffer is passed to
virBitmapToDataBuf, it will read off the end of the bitmap and copy junk
into the returned buffer. Add a check to only copy the length of the
bitmap to the buffer.
The problem can be observed after setting a vcpu affinity using the
On Wed, Apr 03, 2019 at 01:48:33PM -0400, Cole Robinson wrote:
> On 3/26/19 4:06 PM, Allen, John wrote:
> > For pinned vcpus, vcpupin will report inaccurate affinity values on machines
> > with high core counts (256 cores in my case). The problem is produced as
> > foll
Sent this out to the list a few days ago, but never saw it appear on the
archives. Resending--hopefully this makes it to the list.
---
For pinned vcpus, vcpupin will report inaccurate affinity values on machines
with high core counts (256 cores in my case). The problem is produced as
follows:
$
For pinned vcpus, vcpupin will report inaccurate affinity values on machines
with high core counts (256 cores in my case). The problem is produced as
follows:
$ virsh vcpupin myguest 0 4
$ virsh vcpupin myguest 0
VCPU CPU Affinity
---
0 4,192,194,196-197
