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.
On Wed, Feb 7, 2018 at 9:55 PM pixelfairy <pixelfa...@gmail.com> wrote:
> they're all pvh. they were hvm when restoring from qubes-backup, but that
> restore partially failed.
> On Wed, Feb 7, 2018 at 9:23 PM Chris Laprise <tas...@posteo.net> wrote:
>> On 02/07/2018 09:55 PM, pixel fairy wrote:
>> > On Wednesday, February 7, 2018 at 6:54:32 PM UTC-8, pixel fairy wrote:
>> >> 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.
>> > If theres any strait forward way to debug this id love to.
>> 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
>> PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.