Displaying 2 results from an estimated 2 matches for "vm010".
Did you mean:
vm01
2012 Dec 05
1
Incorrect currentMemory for qemu-1.2+
...ent and maximum(or entire host) memory present in both
configurations. 8Gb node is a simple non-numa machine so this is not
related to numa miscalculation. Previous test at the link above
processed on the 64GB two-head node with symmetric numa topology, if
it matters.
And finally,
$ virsh dumpxml vm010-000-000-092 | grep curr
<currentMemory unit='KiB'>5398528</currentMemory>
$ virsh qemu-monitor-command --hmp vm010-000-000-092 info balloon
balloon: actual=1176
Until virtio_balloon initializes in the guest, libvirt reporting
_right_ value for some seconds after VM start, so...
2018 May 23
0
Rebalance state stuck or corrupted
...n gfs-vm002. Error: rebalance session is in progress for
the volume 'gv0'
Staging failed on gfs-vm016. Error: rebalance session is in progress for
the volume 'gv0'
Staging failed on gfs-vm007. Error: rebalance session is in progress for
the volume 'gv0'
Staging failed on gfs-vm010. Error: rebalance session is in progress for
the volume 'gv0'
user at gfs-vm000:~$ sudo gluster volume rebalance gv0 stop
volume rebalance: gv0: failed: Rebalance not started.
tail log from gv0-rebalance.log
[2018-05-23 17:32:55.262168] I [MSGID: 109029]
[dht-rebalance.c:4260:gf_defrag_st...