On 7/23/19 8:00 PM, Sven Vogel wrote:
Hey there,
I hope anyone can bring some light in the following problem.
we have an base bridge for example and cloudbr0. After we add an mtu to the vm
bridge here it seems the base bridge gets the same mtu like the vnet adapter.
Is this
I'm curious that why librbd sets this limitation? The rule first
appeared in librbd.git commit d57485f73ab. Theoretically, a
write-through cache is also safe for VM migration, if the cache
implementation guarantees that cache invalidation and disk write are
synchronous operations.
For example,
On 7/29/19 3:51 AM, Ming-Hung Tsai wrote:
I'm curious that why librbd sets this limitation? The rule first
appeared in librbd.git commit d57485f73ab. Theoretically, a
write-through cache is also safe for VM migration, if the cache
implementation guarantees that cache invalidation and disk write
Sorry, the title and content are wrong. I mean libvirt, not librbd.
Ming-Hung Tsai :
>
> I'm curious that why librbd sets this limitation? The rule first
> appeared in librbd.git commit d57485f73ab. Theoretically, a
> write-through cache is also safe for VM migration, if the cache
>
Hi,
Is there a way to find out total CPU's, Memory and Storage using virsh
command? For example virsh list --all list out all VM's
11dockerregistry01 running
12gitlab running
Any help will be highly appreciated. Thanks in Advance.
Best Regards,
Kaushal
Hi Michal,
Thanks for your answer.
I don’t understand why an interface created without mtu gets only 1500 visible
in the virtual machine but if I create an interface with mtu higher than 1500
e.g. 2000 the bridge will change too. Before the bridge was e.g. by 9000.
I ask because you wrote if I
