performance hit with 4.0rc4

72 views
Skip to first unread message

pixel fairy

unread,
Feb 7, 2018, 9:54:32 PM2/7/18
to qubes-users
reinstalled over 4.0rc3 and vms take much longer to start now. it usually takes a few seconds before getting the notification that an app vm is starting.

firefox performs fine, including youtube in full screen (1080p)

chrome is a bit jumpy in most use, but plays video fine as long as it not full screen

blender is noticeably slower, but still usable for small scenes.

pixel fairy

unread,
Feb 7, 2018, 9:55:45 PM2/7/18
to qubes-users

If theres any strait forward way to debug this id love to.

Chris Laprise

unread,
Feb 8, 2018, 12:24:02 AM2/8/18
to pixel fairy, qubes-users
What does 'qvm-prefs' show for the virt_mode? It is the hvm mode that
starts most slowly and taxes the system. Most of the VMs (except sys-net
and sys-usb) should be using pvh mode.

If the VMs are taking a very long time to start you can try enabling
debug mode from either 'qvm-prefs' or VM Settings dialog.

--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

pixelfairy

unread,
Feb 8, 2018, 12:56:17 AM2/8/18
to Chris Laprise, qubes-users
they're all pvh. they were hvm when restoring from qubes-backup, but that restore partially failed.

pixelfairy

unread,
Feb 8, 2018, 3:35:17 AM2/8/18
to Chris Laprise, qubes-users
with debug true, it started what seemed to be a console. probing edd..ok was the last thing it printed, which happend pretty fast. then it just stayed there showing that edd message before blanking and dom0 showing the notification that the domain had started.

in 4.0rc3 they were hvm, and ran faster.
Reply all
Reply to author
Forward
0 new messages