Reading @
How to know if the balloon driver is running
http://www.gossamer-threads.com/lists/xen/users/315064#315064
"...
IIRC the core balloon driver is always present when Xen is enabled and
so the kernel will respond to requests from the host/toolstack to change
On 04/07/16 15:58, PGNet Dev wrote:
> On 07/04/2016 04:22 AM, George Dunlap wrote:
>> Thanks for your persistence. :-)
>
> I appreciate the reply :-)
>
>> It's likely that this is related to a known problem with the interface
>> between the balloon driver and the toolstack. The warning itself is
On 07/04/2016 04:22 AM, George Dunlap wrote:
Thanks for your persistence. :-)
I appreciate the reply :-)
It's likely that this is related to a known problem with the interface
between the balloon driver and the toolstack. The warning itself is
benign: it simply means that the balloon driver
On Wed, Jun 29, 2016 at 5:27 PM, PGNet Dev wrote:
> In summary, there's a problem
>
> An indication of the guest trying to allocate more memory that the
> host admin has allowed.
>
> that's filling logs with 10s of thousands of redundant log entries, with a
> suspicion that it's 'balloonin
In summary, there's a problem
An indication of the guest trying to allocate more memory that the host
admin has allowed.
that's filling logs with 10s of thousands of redundant log entries, with
a suspicion that it's 'ballooning' issue in the guest
Perhaps something wrong in the gue
>>> On 29.06.16 at 17:38, wrote:
> On 06/29/2016 07:17 AM, Jan Beulich wrote:
>> I don't think a guest would itself issue any relevant messages.
>
> You mentioned ballooning in the guest. The doc I found addressed
> ballooning, in the guest.
>
> If not that, then what output, with specificity,
On 06/29/2016 07:17 AM, Jan Beulich wrote:
I don't think a guest would itself issue any relevant messages.
You mentioned ballooning in the guest. The doc I found addressed
ballooning, in the guest.
If not that, then what output, with specificity, would be helpful in
troubleshooting this ?
>>> On 29.06.16 at 14:58, wrote:
> On 06/29/2016 03:07 AM, Jan Beulich wrote:
>>> What needs to be fixed, or if of no concern, can these messages be silenced?
>>
>> Perhaps something wrong in the guest's balloon driver.
>
> I'm seeing these @host log-entries for Ubuntu, Arch & Opensuse guests.
>
fyi, per
Verify Xen Project PVHVM drivers are working in the Linux HVM guest
kernel
http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers
"Run "dmesg | egrep -i 'xen|front'" in the HVM guest VM."
with Guest cmd line,
... systemd.log_level=debug systemd.log_target=
On 06/29/2016 03:07 AM, Jan Beulich wrote:
What are these 'Over-allocation' messages?
An indication of the guest trying to allocate more memory that the
host admin has allowed.
currently, each guest has allocated
maxmem = 2048
memory = 2048
What needs to be fixed, or if of no concern,
>>> On 29.06.16 at 02:06, wrote:
> What are these 'Over-allocation' messages?
An indication of the guest trying to allocate more memory that the
host admin has allowed.
> What needs to be fixed, or if of no concern, can these messages be silenced?
Perhaps something wrong in the guest's balloon
(relo'd from user list)
I've launched an Ubuntu PVHVM guest, on a Xen 4.7 host
cat guest1.cfg
name = 'guest1'
builder = 'hvm'
xen_platform_pci = 1
device_model_version = 'qemu-xen'
bios = 'ovmf'
12 matches
Mail list logo
