Xentop shows windows 11 qube twice + high cpu on idle

User Support
1

Is this normal???
I have one line in xentop where it actually says WindowsNew with appropriate memory I assigned to it, and then a second line with the WindowsNew and then memory of 0.9%…

But the CPU is the most critical part for me. On IDLE the first WindowsNew constantly above 50%, on average around 75% actually!!! (I assigned 2 vcpus to the qube) and the second line around 5-10%.
All the rest of my qubes are linux based and I don’t see anything like that, and I have 0-1% usage on them on idle.

Can someone help please???

2

I have one line in xentop where it actually says WindowsNew with appropriate memory I assigned to it, and then a second line with the WindowsNew and then memory of 0.9%…

The second one is probably WindowsNew-dm, a Device Model Stub Domain. They get created for each HVM qube you have and it’s normal. Making sure you're not a bot!

But the CPU is the most critical part for me. On IDLE the first WindowsNew constantly above 50%, on average around 75% actually!!! (I assigned 2 vcpus to the qube) and the second line around 5-10%.

If I had to guess that’s just Windows being a shit OS, as always.

1 Like
3

No! That’s the thing… it’s WindowsNew TWICE! And it’s WITHOUT QWT!!!

4

@atrate is right - its’ the stub domain and the normal qube. You see
this with all HVM.

1 Like
5

OMG!!! it has a tiny “-” at the end… without “-dm”… yes you were right, thanks!

6

Could be, but I tried windows 10 and it’s not like that…
If anyone has windows 11 please share

7

The rest of the name is probably cut off in the xentop window.

Could be, but I tried windows 10 and it’s not like that…

Windows 11 is famously slopcoded and badly optimised:

https://winaero.com/windows-11-start-menu-revealed-as-resource-heavy-react-native-app-sparks-performance-concerns/

1 Like
8

I think you are most likey right, even through it’s not helping to deal with the windows qube