/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 not anymore running / Cannot execute qrexec-daemon ?? #3459

Closed
ThierryIT opened this Issue Jan 14, 2018 · 13 comments

Comments

Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
  Release 3.2 updates
3 participants
@ThierryIT @andrewdavidwong @marmarek
@ThierryIT

ThierryIT commented Jan 14, 2018 •
edited
Edited 8 times
  • @ThierryIT ThierryIT edited Jan 16, 2018 (most recent)
  • @ThierryIT ThierryIT edited Jan 15, 2018
  • @ThierryIT ThierryIT edited Jan 15, 2018
  • @ThierryIT ThierryIT edited Jan 15, 2018
  • @ThierryIT ThierryIT edited Jan 15, 2018
  • @ThierryIT ThierryIT edited Jan 14, 2018
  • @ThierryIT ThierryIT edited Jan 14, 2018
  • @ThierryIT ThierryIT edited Jan 14, 2018

Qubes OS version:

R3.2
Kernel 4.9.56-21

Affected TemplateVMs:

Steps to reproduce the behavior:

Installing AEM ?

update: VMs with devices selected do have an qrexec-daemon error and cannot start, this is not the case for VMs who do not have any devices selected. (what ever the default Template is: debian 9 or fedora 26)

Expected behavior:

VMs running

Actual behavior:

netVM is not running (cannot execute qrexec-daemon)
proxyVM is running if not link to my netVM.

General notes:

I have installed yesterday AEM and sys-usb.
sys-usb has been removed following the procedure.
When booting I should have my two VMs "netVM and proxyVM" starting to boot automatically. Not the case anymore.
My wifi device doesn't seems to be up as it was before (internal not usb). Same if using ethernet (docking station)

Related issues:

Perhaps an interference since I have installed AEM ?

@ThierryIT ThierryIT referenced this issue Jan 14, 2018

Closed

sys-net , Error starting VM: Cannot exeCute qrexec-daemon! #1724

@ThierryIT ThierryIT changed the title from VM not anymore running ?? to VMs not anymore running / Cannot execute qrexec-daemon ?? Jan 14, 2018

@andrewdavidwong andrewdavidwong added the bug label Jan 14, 2018

@andrewdavidwong andrewdavidwong added this to the Release 3.2 updates milestone Jan 14, 2018

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jan 14, 2018

Member

You mentioned that you've removed sys-usb, but it depends on the steps you took to remove it. If you have not already done so, please follow these instructions in order to properly remove the USB qube:

https://www.qubes-os.org/doc/usb/#removing-a-usb-qube
Member

andrewdavidwong commented Jan 14, 2018

You mentioned that you've removed sys-usb, but it depends on the steps you took to remove it. If you have not already done so, please follow these instructions in order to properly remove the USB qube:

https://www.qubes-os.org/doc/usb/#removing-a-usb-qube
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Jan 15, 2018

Trying to debug:

I have created a new netVM based on Debian 9 template (Global Settings/Default Template: Debian 9 instead of fedora 26)
When booting without any devices selected, VMs 'all type' are working even if the VM is based on fedora 26.
If I add network devices (ethernet controller as exemple) on VM, I still do have an : qrerex-daemon error
So it seems that it has nothing to do with the Template but only with selected devices.

ThierryIT commented Jan 15, 2018 •
edited
Edited 2 times
  • @ThierryIT ThierryIT edited Jan 15, 2018 (most recent)
  • @ThierryIT ThierryIT edited Jan 15, 2018

Trying to debug:

I have created a new netVM based on Debian 9 template (Global Settings/Default Template: Debian 9 instead of fedora 26)
When booting without any devices selected, VMs 'all type' are working even if the VM is based on fedora 26.
If I add network devices (ethernet controller as exemple) on VM, I still do have an : qrerex-daemon error
So it seems that it has nothing to do with the Template but only with selected devices.

@ThierryIT ThierryIT referenced this issue Jan 15, 2018

Open

Cannot start VMs running 4.14.13-1 kernel #3466

@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Jan 16, 2018

Still trying to give you the maximum useful information.
The booting menu give me the possibility between:

  • AEM Qubes with Xen hypervisor
  • Advanced options with AEM boot for Qubes (different kernel version)
  • Qubes with hypervisor Xen
  • Advanced options for Qubes

If choosing "Qubes with hypervisor Xen" -> working has it was before
If choosing AEM ... -> qrexec-daemon pb

ThierryIT commented Jan 16, 2018 •
edited
Edited 1 time
  • @ThierryIT ThierryIT edited Jan 16, 2018 (most recent)

Still trying to give you the maximum useful information.
The booting menu give me the possibility between:

  • AEM Qubes with Xen hypervisor
  • Advanced options with AEM boot for Qubes (different kernel version)
  • Qubes with hypervisor Xen
  • Advanced options for Qubes

If choosing "Qubes with hypervisor Xen" -> working has it was before
If choosing AEM ... -> qrexec-daemon pb
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Jan 19, 2018

nobody ? I am completely stuck on this ....

ThierryIT commented Jan 19, 2018

nobody ? I am completely stuck on this ....
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 19, 2018

Member

Check /var/log/xen/console/guest-sys-net.log just after trying to start sys-net.
Member

marmarek commented Jan 19, 2018

Check /var/log/xen/console/guest-sys-net.log just after trying to start sys-net.
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Jan 19, 2018

I do not have any logs to see.
If I am doing the last imput using "ls -rtl" the most recent input will be for the "hypervisor.log" ...
All other logs are from the 17th, 15th ....

If using the right click on the VM / logs / ....guest-netVM-WAN.log ... It is empty
................................................................................/ .....qrexec.netVM-WAN.log:

  • domain dead
  • cannot connect to qrexec agent: No such process

ThierryIT commented Jan 19, 2018 •
edited
Edited 2 times
  • @ThierryIT ThierryIT edited Jan 19, 2018 (most recent)
  • @ThierryIT ThierryIT edited Jan 19, 2018

I do not have any logs to see.
If I am doing the last imput using "ls -rtl" the most recent input will be for the "hypervisor.log" ...
All other logs are from the 17th, 15th ....

If using the right click on the VM / logs / ....guest-netVM-WAN.log ... It is empty
................................................................................/ .....qrexec.netVM-WAN.log:

  • domain dead
  • cannot connect to qrexec agent: No such process
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 19, 2018

Member

Hmm, so lets see hypervisor.log.
Member

marmarek commented Jan 19, 2018

Hmm, so lets see hypervisor.log.
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Jan 19, 2018

Not in the same pc, I am going to do my best:

(XEN) 89c527cea.... 00000000.... fffffffffff81....... 0000000000....
...
(XEN) 0000000000000 0000000000000 0000000000000 0000000000000
(XEN) 0000000000000 0000000000000 0000000000000 0000000000000

ThierryIT commented Jan 19, 2018

Not in the same pc, I am going to do my best:

(XEN) 89c527cea.... 00000000.... fffffffffff81....... 0000000000....
...
(XEN) 0000000000000 0000000000000 0000000000000 0000000000000
(XEN) 0000000000000 0000000000000 0000000000000 0000000000000
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 19, 2018

Member

Ough, looks bad. There should be some header, like domain X crashed and some textual reason.
What is the kernel version for sys-net?
Member

marmarek commented Jan 19, 2018

Ough, looks bad. There should be some header, like domain X crashed and some textual reason.
What is the kernel version for sys-net?
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Jan 19, 2018

I have to reboot my Qubes and boot back to: "Qubes with hypervisor Xen" instead of "AEM"
I come back to you asap

ThierryIT commented Jan 19, 2018 •
edited
Edited 1 time
  • @ThierryIT ThierryIT edited Jan 19, 2018 (most recent)

I have to reboot my Qubes and boot back to: "Qubes with hypervisor Xen" instead of "AEM"
I come back to you asap
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Jan 19, 2018

4.9.56-21

ThierryIT commented Jan 19, 2018

4.9.56-21
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 19, 2018

Member

Hmm, so the latest in stable. You could try 4.14.13 from testing, but I guess it wont help. AEM (specifically: tboot) do cause problems on some hardware, see AEM README - section about memory size. Maybe this is another case like this? Having more detailed message could help, but better ask on xen-devel or tboot-devel mailing lists.
Member

marmarek commented Jan 19, 2018

Hmm, so the latest in stable. You could try 4.14.13 from testing, but I guess it wont help. AEM (specifically: tboot) do cause problems on some hardware, see AEM README - section about memory size. Maybe this is another case like this? Having more detailed message could help, but better ask on xen-devel or tboot-devel mailing lists.
@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Jan 20, 2018

No link with ticket: #3465 ?

ThierryIT commented Jan 20, 2018

No link with ticket: #3465 ?

@ThierryIT ThierryIT closed this Feb 28, 2018

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