Nir Soffer

@mhenriks I think I was confused by this comment: https://github.com/kubevirt/kubevirt/pull/11267#issuecomment-1954912217

@mhenriks any idea when we will have new release including this change?

## Build and install ``` make prog="out/docker-machine-driver-kvm2" rm -f "$prog"* make "$prog" cp "$prog" ~/.minikube/bin/ ``` ## Starting a cluster ``` $ out/minikube start --driver kvm2 -p dr1 --network default...

Failing tests look similar to #18241 - change in libvirt domain xml cannot break other drivers.

## Build and install ``` make prog="out/docker-machine-driver-kvm2" rm -f "$prog"* make "$prog" cp "$prog" ~/.minikube/bin/ ``` ## Start the first cluster ``` $ minikube start --driver kvm2 -p cluster1 😄...

@afbjorklund HyperKit and QEMU failures should be unrelated since the change is in libvirt configuration domain xml. Are these tests broken now?

This issue happens also in github runners, this is not a self-hosted runner issue. Example build with default cache (true): ``` Setup go version spec 1.23 Attempting to download 1.23......

/remove-lifecycle rotten

I learned about this today reviewing #2105 :-) Shouldn't this be documented in the pflags package?

I'm using `Run:` and terminate on errors with `log.Fatal()` or `os.Exit()`. If the error is not a usage error, why print usage messages?