Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upVM not starting with 3 Monitors #3634
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Feb 26, 2018
Member
no vm starts at all again from that point on ( starts but no window appears)
So does VM start or not? Check with qvm-ls command - what do you have in "STATE" column? What happens when you try starting a VM from terminal with qvm-start SOME_VM? Can you start any application with qvm-run command (for example qvm-run work firefox)?
So does VM start or not? Check with |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
TheBubblePopped
Feb 26, 2018
I am reformatting it now. Will check and update but the VM start in general in the Qubes manager it appears green ( and i can t shut it down) but there is no window that opens. I tried the qvm-run personal firefox but it does nothing at all and seems like stucked
TheBubblePopped
commented
Feb 26, 2018
|
I am reformatting it now. Will check and update but the VM start in general in the Qubes manager it appears green ( and i can t shut it down) but there is no window that opens. I tried the qvm-run personal firefox but it does nothing at all and seems like stucked |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
TheBubblePopped
Feb 26, 2018
So here is my update. Now i know that the main problem is. Everytime i connect my 3t monitor nothing is starting. Any ideas how to solve this? its a 4k 60hz combined with an iiyama 3k and a normal 2k monitor
TheBubblePopped
commented
Feb 26, 2018
•
edited
Edited 1 time
-
TheBubblePopped
edited Feb 26, 2018 (most recent)
edited
-
Feb 26, 2018 (most recent)
|
So here is my update. Now i know that the main problem is. Everytime i connect my 3t monitor nothing is starting. Any ideas how to solve this? its a 4k 60hz combined with an iiyama 3k and a normal 2k monitor |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
What is your total resolution? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
TheBubblePopped
Feb 26, 2018
So here about the KDE :
If i remove the 1 monitor i can open a vm again but i have no signal on the main monitor on the kde version . If i do not install the KDE i can just not open another vm if i have the 3th monitor attached. I have to reboot without the 3th monitor and then it works. Also something else that was weird: on the non KDE version when i attached the 3th monitor it just mirrored the second monitor. The 1th had another picture. So monitor 2 and 3 were screening the same stuff.
The resolutiuon is 2560 1440 19201080 and the last one 3840 × 2160 pivot mode flipped clockwise left
TheBubblePopped
commented
Feb 26, 2018
|
So here about the KDE : If i remove the 1 monitor i can open a vm again but i have no signal on the main monitor on the kde version . If i do not install the KDE i can just not open another vm if i have the 3th monitor attached. I have to reboot without the 3th monitor and then it works. Also something else that was weird: on the non KDE version when i attached the 3th monitor it just mirrored the second monitor. The 1th had another picture. So monitor 2 and 3 were screening the same stuff. The resolutiuon is 2560 1440 19201080 and the last one 3840 × 2160 pivot mode flipped clockwise left |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Feb 26, 2018
Member
So, in total it is 6640 x 3840, right? This should be far from GUI protocol limits (max window 16384x6144). But check /var/log/qubes/gui*log in dom0 and X logs in VMs anyway.
|
So, in total it is 6640 x 3840, right? This should be far from GUI protocol limits (max window 16384x6144). But check /var/log/qubes/gui*log in dom0 and X logs in VMs anyway. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
TheBubblePopped
Feb 26, 2018
But it is not as 1 monitor it is splitted into 3 parts so why does the total resolution matter?
TheBubblePopped
commented
Feb 26, 2018
•
edited
Edited 1 time
-
TheBubblePopped
edited
Feb 26, 2018 (most recent)
edited
-
Feb 26, 2018 (most recent)
|
But it is not as 1 monitor it is splitted into 3 parts so why does the total resolution matter? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
TheBubblePopped
Feb 26, 2018
The only thing i get is Icon size: 128x128
4 times in a row, and if i connect my monitor and do some stuff i get under each of these icon size messages
5 times :
reloading X server parameters...
and then one time random on the second icon size message the message:
open /var /run/qubes/qubes/clipboard.bin.xevent; No such file or directory
TheBubblePopped
commented
Feb 26, 2018
|
The only thing i get is Icon size: 128x128 4 times in a row, and if i connect my monitor and do some stuff i get under each of these icon size messages 5 times : and then one time random on the second icon size message the message: open /var /run/qubes/qubes/clipboard.bin.xevent; No such file or directory |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
TheBubblePopped
Feb 26, 2018
And on the qube personal log i can see
Icon size: 128x128
reloading X server parameters...
reloading X server parameters...
reloading X server parameters...
reloading X server parameters...
reloading X server parameters...
open /var/run/qubes/qubes-clipboard.bin.xevent: No such file or directory
reloading X server parameters...
reloading X server parameters...
reloading X server parameters...
reloading X server parameters...
invalid PMaxSize for 0x400045 (587/32767)
TheBubblePopped
commented
Feb 26, 2018
|
And on the qube personal log i can see |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
swilso793
Feb 26, 2018
Anyone else with 3 monitors have the same problem? I am about to buy a third one as well and this would be a deal breaker.
swilso793
commented
Feb 26, 2018
|
Anyone else with 3 monitors have the same problem? I am about to buy a third one as well and this would be a deal breaker. |
TheBubblePopped
changed the title from
VM not starting after updates
to
VM not starting with 3 Monitors
Feb 26, 2018
andrewdavidwong
added
bug
C: gui-virtualization
labels
Feb 26, 2018
andrewdavidwong
added this to the Release 4.0 milestone
Feb 26, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Polygonbugs
Mar 3, 2018
This should be far from GUI protocol limits (max window 16384x6144).
What happens if there are four 4K monitors? BTW, it won't be possible unless if I could install dGPU drivers... I've only seen few of them use dGPU.
Polygonbugs
commented
Mar 3, 2018
What happens if there are four 4K monitors? BTW, it won't be possible unless if I could install dGPU drivers... I've only seen few of them use dGPU. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tonsilware
Mar 21, 2018
This issue is probably the same as #3174
Basically the hardcoded "VideoRam 65536" in /etc/X11/xorg-qubes-conf.template in the problem. As I mentioned in the other issue, the VideoRam value should be dynamically calculated to ensure it accommodates the total resolution and not just hardcoded at 65536, because 65536 is too low for multiple 4k displays and causes the VMs to not start.
My current solution: Disconnect all extra monitors (so you can actually start the vms). Then start each template vm and edit /etc/X11/xorg-qubes-conf.template in each template vm, increasing the "VideoRam 65536" to a sufficiently large value to ensure that there is sufficient memory to accommodate your total resolution. (I just doubled the VideoRam to 131072 and that is fine for my setup.) Then shutdown the edited template vms and after that everything should work.. until an update overwrites your xorg-qubes-conf.template and you have to re-edit the files to fix the problem again..
tonsilware
commented
Mar 21, 2018
•
edited
Edited 1 time
-
tonsilware
edited Mar 21, 2018 (most recent)
edited
-
Mar 21, 2018 (most recent)
|
This issue is probably the same as #3174 Basically the hardcoded "VideoRam 65536" in /etc/X11/xorg-qubes-conf.template in the problem. As I mentioned in the other issue, the VideoRam value should be dynamically calculated to ensure it accommodates the total resolution and not just hardcoded at 65536, because 65536 is too low for multiple 4k displays and causes the VMs to not start. My current solution: Disconnect all extra monitors (so you can actually start the vms). Then start each template vm and edit /etc/X11/xorg-qubes-conf.template in each template vm, increasing the "VideoRam 65536" to a sufficiently large value to ensure that there is sufficient memory to accommodate your total resolution. (I just doubled the VideoRam to 131072 and that is fine for my setup.) Then shutdown the edited template vms and after that everything should work.. until an update overwrites your xorg-qubes-conf.template and you have to re-edit the files to fix the problem again.. |
added a commit
to marmarek/qubes-gui-agent-linux
that referenced
this issue
Mar 22, 2018
marmarek
referenced this issue
in QubesOS/qubes-gui-agent-linux
Mar 22, 2018
Merged
Dynamic video ram #36
andrewdavidwong
modified the milestones:
Release 4.0,
Release 4.0 updates
Mar 31, 2018
marmarek
closed this
in
marmarek/qubes-gui-agent-linux@ac21967
Apr 5, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
May 2, 2018
Automated announcement from builder-github
The package gui-agent-linux has been pushed to the r4.0 testing repository for the CentOS centos7 template.
To test this update, please install it with the following command:
sudo yum update --enablerepo=qubes-vm-r4.0-current-testing
qubesos-bot
commented
May 2, 2018
|
Automated announcement from builder-github The package |
qubesos-bot
added
the
r4.0-centos7-cur-test
label
May 2, 2018
qubesos-bot
referenced this issue
in QubesOS/updates-status
May 2, 2018
Closed
gui-agent-linux v4.0.10 (r4.0) #501
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
May 2, 2018
Automated announcement from builder-github
The component gui-agent-linux (including package pulseaudio-qubes-4.0.10-1.fc26) has been pushed to the r4.0 testing repository for the Fedora template.
To test this update, please install it with the following command:
sudo yum update --enablerepo=qubes-vm-r4.0-current-testing
qubesos-bot
commented
May 2, 2018
|
Automated announcement from builder-github The component |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
May 2, 2018
Automated announcement from builder-github
The package qubes-gui-agent_4.0.10-1+deb9u1 has been pushed to the r4.0 testing repository for the Debian template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing stretch-testing (or appropriate equivalent for your template version), then use the standard update command:
sudo apt-get update && sudo apt-get dist-upgrade
qubesos-bot
commented
May 2, 2018
|
Automated announcement from builder-github The package |
qubesos-bot
added
the
r4.0-stretch-cur-test
label
May 2, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
May 14, 2018
Automated announcement from builder-github
The package gui-agent-linux has been pushed to the r4.0 stable repository for the Fedora centos7 template.
To install this update, please use the standard update command:
sudo yum update
qubesos-bot
commented
May 14, 2018
|
Automated announcement from builder-github The package |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
May 14, 2018
Automated announcement from builder-github
The package qubes-gui-agent_4.0.10-1+deb9u1 has been pushed to the r4.0 stable repository for the Debian template.
To install this update, please use the standard update command:
sudo apt-get update && sudo apt-get dist-upgrade
qubesos-bot
commented
May 14, 2018
|
Automated announcement from builder-github The package |
qubesos-bot
added
r4.0-stretch-stable
and removed
r4.0-stretch-cur-test
labels
May 14, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
May 14, 2018
Automated announcement from builder-github
The component gui-agent-linux (including package pulseaudio-qubes-4.0.10-1.fc26) has been pushed to the r4.0 stable repository for the Fedora template.
To install this update, please use the standard update command:
sudo yum update
qubesos-bot
commented
May 14, 2018
|
Automated announcement from builder-github The component |
TheBubblePopped commentedFeb 26, 2018
•
edited
Edited 1 time
-
TheBubblePopped
edited Feb 26, 2018 (most recent)
Qubes OS version:
4.0RC4
Affected component(s):
VM not starting
Steps to reproduce the behavior:
Install OS then just sudo qubes-dom0-update => no vm starts at all again from that point on ( starts but no window appears)
i tested current-testing unstable and secure updates but still facing the same problem
Expected behavior:
Vm should open
General notes:
1800x
I think the kernel updates there too and causes problems but i have no idea