/qubes-issues

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VMs stay yellow in Qubes VM Manger (QVMM) / qrexec not connected error when trying to start applications from QVMM #2178

Closed
adrelanos opened this Issue Jul 16, 2016 · 6 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
No milestone
3 participants
@adrelanos @marmarek @andrewdavidwong
@adrelanos
Member

adrelanos commented Jul 16, 2016

Qubes OS version (e.g., R3.1):

R3.2 with testing repository

Affected TemplateVMs (e.g., fedora-23, if applicable):

Debian, Fedora (also with R3.2 testing repository)

Expected behavior:

///

Actual behavior:

Both, Fedora and Debian based browser VMs stay yellow in QVMM. Running konsole from QVMM keeps failing (tried 3 times each). QVMM reported qrexec not connected. Strangely however running qvm-run brwser konsole instantly worked.

(sys-net and sys-firewall are green.)

Steps to reproduce the behavior:

  1. boot Qubes
  2. as per "actual behavior"

General notes:

It is probably not the xendriverdomain systemd service not enabled in Fedora (#2141) issue since that is now sorted out.
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 16, 2016

Member

What is the status of those VMs in qvm-ls output?
After failed attempt, check VM related logs in /var/log/qubes and in the
VM itself (journalctl, if you can't access VM terminal window, try sudo xl console).

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Member

marmarek commented Jul 16, 2016

What is the status of those VMs in qvm-ls output?
After failed attempt, check VM related logs in /var/log/qubes and in the
VM itself (journalctl, if you can't access VM terminal window, try sudo xl console).

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

@andrewdavidwong andrewdavidwong added bug C: qubes-manager labels Jul 17, 2016

@marmarek marmarek closed this in marmarek/old-qubes-core-admin@b467dd6 Jul 18, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 19, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.2.7-1.fc23 has been pushed to the r3.2 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update
Member

marmarek commented Jul 19, 2016

Automated announcement from builder-github

The package qubes-core-dom0-3.2.7-1.fc23 has been pushed to the r3.2 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@marmarek marmarek added the r3.2-dom0-cur-test label Jul 19, 2016

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Jul 21, 2016

Member

This update fixed it for me.
Member

adrelanos commented Jul 21, 2016

This update fixed it for me.
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 28, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.2.7-1.fc23 has been pushed to the r3.2 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update
Member

marmarek commented Jul 28, 2016

Automated announcement from builder-github

The package qubes-core-dom0-3.2.7-1.fc23 has been pushed to the r3.2 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

@marmarek marmarek added r3.2-dom0-stable and removed r3.2-dom0-cur-test labels Jul 28, 2016

marmarek added a commit to QubesOS/qubes-core-admin that referenced this issue Nov 20, 2016

@HW42 @marmarek
QubesWatch: do not create multiple dom0 QubesDB connections 
When calling _register_watches() multiple times for dom0 (by passing
None or since 7e9c816 by passing the corresponding libvirt domain) the
check was missing if there is already a QubesDB in _qdb. Therefore a new
QubesDB was created and the old one is destroyed by the GC. As a
consequence the watch_fd is closed but the libvirt event handle for this
fd is still registered. So when libvirt calls poll() it returns
immediately POLLNVAL with the closed fd. This is not caught in libvirt
and the callback is called as if an event happened. _qdb_handler() now
calls read_watch() on the new fd for dom0 and thereby hangs the thread.
This leads (at leads) to qubes-manager to miss VM status updates and
block device events.

Fixes QubesOS/qubes-issues#2178

(cherry picked from commit b467dd6)
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
0971626
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Nov 20, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.1.18-1.fc20 has been pushed to the r3.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update
Member

marmarek commented Nov 20, 2016

Automated announcement from builder-github

The package qubes-core-dom0-3.1.18-1.fc20 has been pushed to the r3.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@marmarek marmarek added the r3.1-dom0-cur-test label Nov 20, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Dec 4, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.1.18-1.fc20 has been pushed to the r3.1 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update
Member

marmarek commented Dec 4, 2016

Automated announcement from builder-github

The package qubes-core-dom0-3.1.18-1.fc20 has been pushed to the r3.1 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

@marmarek marmarek added r3.1-dom0-stable and removed r3.1-dom0-cur-test labels Dec 4, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment