create new VM freeze screen 1

9 views
Skip to first unread message

'098134'0194328'017834'01783'40917834209

unread,
Jun 18, 2016, 8:29:38 AM6/18/16
to qubes-users
Hallo,

it is a little strange, always if I create a new VM (which takes several minutes), than the system response time for manual inputs (like typing something in an editor) is endless.

But there should be plenty CPU and RAM available.

It looks like that this is only effected all applications, which are shown on the same screen. So screen two seems ok.

Why is this behavior?

Can I define some parameter, which guides me to some liquid user experience?

Kind Reagards

Andrew David Wong

unread,
Jun 18, 2016, 8:48:47 AM6/18/16
to '098134'0194328'017834'01783'40917834209, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I've noticed the same thing, but it doesn't seem to be affected by
which screen an application is on. My CPU usage (as reported by the
KDE widget) spikes, so I assumed that was it.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXZUMjAAoJENtN07w5UDAwlnYP+wRcjKs+o7vUWC9fYVAkvHlw
nNeUMSUqOvUXYZhtVp7siqP3ZwIHhlvkeXzWGxUmTAIYQSj3veX2VnRWVhr09AXR
VrEFt/5Hgt1eq7lV4DWvaqolUdRXylaXs4KDph3ATeliCmQ/ArSILXJI0jtsVebE
Zg0bw90u6Bgrg0YtyeBJySZIzHSvNnXimi5J/kNDYFewfPcFpikiGsD76y8WFWqQ
g55FG4kXY8RAfIl/+hOEPYrowIgP/kz2lwK6M6Bg4ftWv1N0S/rjNgzdzpuTFWD/
vtZ5u0d03XcQCuQKHdSfFoGlLgcI+k2uyweTHFyWw5aNNDrNbKZPBJy79BNMg+r5
I4gHzTFlQUPotvbGd0KDFVrmHX2lOFGf66+RlALY8Z/BVYfXO+BnlB0TKm46JTAu
sREirJhqIE95Jqs/SbaLMSxsACpUE7ZU9Qkf5ltOQboz9XRFOBOVKjFfxYg2v+8P
+wSHvi7jauMypHEKDhLXdyzi3itYWl1ssvkKT6EtOVe2wKb83yzahVZNRgQmmzNX
ybr4SK5roZiudsjD3JH8gQdoJK5r1citt/JK4+kX4AL+wHOqtBEhY2g6RXntjhCL
7oefmQTS3yOImTxO5FY9HXy9z+0zG2YP7vXJagiR63KFyiveR+1jz3S4hLbAIY3E
ajT8tlAOKONeIR1Df5/D
=Dii5
-----END PGP SIGNATURE-----

'019438'019384'0914328'091328'409182'039481'09324

unread,
Jun 18, 2016, 9:55:25 AM6/18/16
to qubes-users
Hallo Andrew,

I used the KDE Desktop System Information view. So I can see some burst up to 80% CPU usage. But normally it is lower than 40% (X8 3.5GHrz 32 GB RAM).

So there must be plenty room to type some text in parallel inside a text-editor.

I thought to copy a VM would generate mostly IO stress and some SAN-like buffering, will help to accelerate this job (see upTempo).

Kind Regards


Chris Laprise

unread,
Jun 18, 2016, 10:03:34 AM6/18/16
to Andrew David Wong, '098134'0194328'017834'01783'40917834209, qubes-users


On 06/18/2016 08:48 AM, Andrew David Wong wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 2016-06-18 05:29, '098134'0194328'017834'01783'40917834209 wrote:
>> Hallo,
>>
>> it is a little strange, always if I create a new VM (which takes
>> several minutes), than the system response time for manual inputs
>> (like typing something in an editor) is endless.
>>
>> But there should be plenty CPU and RAM available.
>>
>> It looks like that this is only effected all applications, which
>> are shown on the same screen. So screen two seems ok.
>>
>> Why is this behavior?
>>
>> Can I define some parameter, which guides me to some liquid user
>> experience?
>>
>> Kind Reagards
>>
> I've noticed the same thing, but it doesn't seem to be affected by
> which screen an application is on. My CPU usage (as reported by the
> KDE widget) spikes, so I assumed that was it.
>

Hmmm, create new vm on my system = 5 seconds.

This sounds like low memory and lots of swapping. Check the amount of
swap usage with 'free'.

Chris

109348'109438'0193284'0913284'092183'0491820439

unread,
Jun 18, 2016, 2:55:41 PM6/18/16
to qubes-users
Hi Chris,

used 2777284
free 17995792
shared 338500
buffers 62024
cached 2037140

buffer/cache used 67812 free 80117772

swap 8011772 used 0

create Fedora23 AppVM = 6 Seconds, yes
create Debian8 AppVM = 5 Seconds, yes

But this was after a fresh restart of Q (before it took some kind of minutes).

Kind Regards


Chris Laprise

unread,
Jun 18, 2016, 7:30:05 PM6/18/16
to 109348'109438'0193284'0913284'092183'0491820439, qubes-users


On 06/18/2016 02:55 PM, 109348'109438'0193284'0913284'092183'0491820439
wrote:
When it slows down again, check 'free' again.

Also, this grinding slowdown can be caused by a vm that's swapping a
lot. If you've been playing around with PCI passthrough, you probably
turned off memory balancing without realizing you left that vm with very
little memory to use.

Chris
Reply all
Reply to author
Forward
0 new messages