17.3.23

Clean up your old qemu processes if using vagrant


In the new sig-windows-dev-tools, we have QEMU !!! https://github.com/kubernetes-sigs/sig-windows-dev-tools/tree/master-qemu that hopefully will be merged to be the Default way we make windows dev clusters moving forward


but wait !!  sometimes it looks like qemu can hang.. then you get 


The forwarded port to 50022 is already in use

on the host machine.


 from Vagrant !!! This is bc i guess, a QEMU process lingered even after vagrant destroyed the VMs.


To fix it just lsof and delete the process manually 

 qemu-syst 27140 jvyas   17u     IPv4 0xb8d84121701ee151        0t0                 TCP *:50022 (LISTEN)

  sig-windows-dev-tools git:(master-qemu) vagrant destroy --force

cni: calico

calico: 3.25.0; containerd: 1.6.15

==> winw1: Instance is not created. Please run `vagrant up` first.

==> controlplane: Instance is not created. Please run `vagrant up` first.

  sig-windows-dev-tools git:(master-qemu) lsof  | grep 50022     

qemu-syst 27140 jvyas   17u     IPv4 0xb8d84121701ee151        0t0                 TCP *:50022 (LISTEN)

  sig-windows-dev-tools git:(master-qemu) lsof  | grep 50022

qemu-syst 27140 jvyas   17u     IPv4 0xb8d84121701ee151        0t0                 TCP *:50022 (LISTEN)

  sig-windows-dev-tools git:(master-qemu) kill 27140

No comments:

Post a Comment