Comment 3 for bug 1831543

hyper-v does not work in the way you are familiar with (such as libvirt) where 2 processor cores are assigned and essentially dedicated to the virtual host.

If i'm not mistaken I believe this is a result in the way hyper-v handles the virtual machines. When a VM is created (BASIC_A2_V2) the hypervisor decides where virtual operating system processes/threads are to be processed via the bare metal resources. I believe this is done at random. This could be why you may be seeing an unusually high amount of cpus in the "offlined" state.

I'm not sure this test should even be run on azure, due to hyper-v. I will take an action item to look into this further. For now, I do not think this is an issue in the least. This test suite is designed to be run on bare metal machines, not hyper-v vms