hi guys
I have a kvm quest & two nodes.
a kvm guest on nodeA and IPaddr2 on nodeB(at this time)
nodeA & nodeB comprise a HA cluster
now...
- nodeA can ping IPaddr2 IP
- nodeB can ping kvm guest IP
- kvm guest can get to nodeB's IP but*
Only a bit non-common bit in my setup is:
- both nodeA &
On 04/09/2018 09:00 AM, llilulu wrote:
> Hi:
>I use libvirt manage virtual guest, When I start many virtual domain(my
> host 128G physical memory）, example, I start 100 guest, 1G per guest。sometime
> I will encounter "cannot allocate memory", "cannot set up guest memory
> \'pc.ram\'： cannot
Hi:
I use libvirt manage virtual guest, When I start many virtual domain(my host
128G physical memory）, example, I start 100 guest, 1G per guest。sometime I will
encounter "cannot allocate memory", "cannot set up guest memory \'pc.ram\'：
cannot allocate memory". sometime encounter qemu
Hi all,
on CentOS7 / RHEL7 launching virt-manager causes a "discovery process"
of the various configured VMs.
This discovery is executed by inspection and overlayed disk files and it
create a very short lived guest-xxxzzzyyy virtual machine. The end
result is a pretty icon to the left of the
On Mon, Apr 09, 2018 at 03:21:04PM +0200, Gionatan Danti wrote:
> Hi all,
> on CentOS7 / RHEL7 launching virt-manager causes a "discovery process" of
> the various configured VMs.
>
> This discovery is executed by inspection and overlayed disk files and it
> create a very short lived
