So, I’ve got this problem where Qubes suddenly stop working…
There are timeouts and hangs, I’ve scanned the HD itself - nothing.
My Debian Qubes, Windows Qubes and also the Debian template do not work properly, leading to qrexec timeouts and also losing sudo for some reason.
Reinstalling the Debian template worked, also installing Windows worked - for a while, before it just started hanging again…
I did update dom-0 recently, but also noticed that this resembles the problems I had initially when installing Qubes itself the first time - could this be hardware related?
Since the Thinkpad X230 has a very neat option for swapping disks I might do a fresh install on another disk tomorrow…
Seems this is where it starts hanging for the Windows Qube at least:
{“execute”: “qmp_capabilities”}
qubes_gui/init: 592
qubes_gui/init: 607
qubes_gui/init: 609
qubes_gui/init[639]: version sent, waiting for xorg conf
{“return”: {}}
br0: port 2(vif29.0-emu) entered blocking state
br0: port 2(vif29.0-emu) entered disabled state
device vif29.0-emu entered promiscuous mode
br0: port 2(vif29.0-emu) entered blocking state
br0: port 2(vif29.0-emu) entered forwarding state
clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x25648d0c182, max_idle_ns: 440795218684 ns
qemu: pin_memory_cacheattr failed: Operation not permitted
random: crng init done
br0: port 2(vif29.0-emu) entered disabled state
device vif29.0-emu left promiscuous mode
br0: port 2(vif29.0-emu) entered disabled state
/etc/qemu-ifdown
br0: port 1(eth0) entered disabled state
device eth0 left promiscuous mode
br0: port 1(eth0) entered disabled state