[05:35] d0ugal: Thanks for the help. But as per the doc I checked for virsh.py file and only "/usr/share/sosreport/sos/plugins/virsh.py" is available in my setup. So is there any way to install virsh drivers? [07:27] Bug #1881892 changed: CPU usage bar not shown in UI for KVMs [08:27] sakharkar: Sorry, I only really idle here for the bug stream :) Lots of far more knowledgeable people are looking at discourse and can help there. [08:27] but I don't really know how the sosreport is related to this issue :) [08:53] d0ugal: sure I am looking into it. Thanks for the help [09:05] sakharkar: np, btw where in the docs does it say to look for virsh.py? [09:06] sakharkar: Did you see this? https://discourse.maas.io/t/maas-2-6-breaks-virsh-esxi-powertype/734 [09:06] d0ugal: yup [09:07] d0ugal: I edited it and now power management started working but commissioning is failing [09:07] I see [10:53] I updated maas from 2.6 to 2.8 and now I get error: warn] Failed to change the boot order to PXE 10.2.2.2: /snap/maas/7808/usr/sbin/ipmi-chassis-config: 15: exec: /usr/sbin/ipmi-config: not found. In 2.6 everything worked fine. Any ideas? [12:15] abyss: Hi, this channel isn't really active. Can you open a bug with more details or maybe ask a question on discourse.maas.io [12:37] abyss: if you can include `snap info maas` in the bug that would be useful [12:51] Bug #1789650 opened: Servers set to boot from disk after MAAS installation [13:20] d0ugal: ok, thank you for info [13:36] Bug #1809939 opened: dhcp snippet create fail when dhcp subnet is relayed [16:31] Bug #1888413 opened: "Add a rack controller" instructions are wrong [18:07] Bug #1888419 opened: MAAS UI is unclear when unable to MAAS deploy machines