>From a user/someone that has supported the current situation for many years
I am entirely supportive!
-Joel
@j...@cloudisland.nz
On Sun, 25 Jun 2023, 06:35 Hervé Werner, wrote:
> Thanks for your complete answer.
>
> Anyway, I have two other things I need to get done, and then I'll be
> back
This is actually a source of great frustration as many vendors ship
the machine type with custom strings. Engineers then do virsh
dumpxml's from one sys and wonder why it doesn't work on another
without realizing say ubuntu has this set to a machine type different
to rhel ( but actually are basical
tworking scripts refering to that virbr1 will create a
race condition which will stop the vm from getting started as you mention.
On 29 April 2017 at 14:45, Laine Stump wrote:
> On 04/28/2017 07:23 PM, Joel Wirāmu Pauling wrote:
> > Possibly related I notice race conditions cause
Possibly related I notice race conditions caused by vnic never getting
loaded if an existing bridge is already up (by OS init scripts etc) and
stopping VM's from getting started.
Often this is behavior you want ; i.e having Host Hypervisor NIC's added
and up before libvirtd sets up it's nics/bridg
