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

Cannot start NetVM #324

Closed
marmarek opened this Issue Mar 8, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 15 Aug 2011 09:22 UTC
Sometimes qvm-start netvm hangs, and the following is in the logs:

[~](joanna@dom0)$ cat /var/log/xen/xl-netvm.log
Waiting for domain netvm (domid 14) to die [13139](pid)
Domain 14 is dead
Action for shutdown reason code 3 is destroy
Domain 14 needs to be cleaned up: destroying the domain
libxl: error: libxl_device.c:513:libxl__wait_for_backend Backend /local/domain/0/backend/pci/14/0 not ready
libxl: error: libxl_device.c:513:libxl__wait_for_backend Backend /local/domain/0/backend/pci/14/0 not ready
Done. Exiting now

```}

Migrated-From: https://wiki.qubes-os.org/ticket/324
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by rafal on 15 Aug 2011 19:21 UTC
In order to capture dmesg for the crashed domain kernel, please do:

  1. in /usr/share/qubes/vm-template.conf, change "on crash=destroy" to "on_crash=preserve"
  2. in qubes.py, comment out self.force_shutdown() after failed qrexec_daemon start (around line 974)

then reproduce the crash, connect to the crashed domain via xl console. Collect the logs; then cleanup via xl destroy.

Member

marmarek commented Mar 8, 2015

Comment by rafal on 15 Aug 2011 19:21 UTC
In order to capture dmesg for the crashed domain kernel, please do:

  1. in /usr/share/qubes/vm-template.conf, change "on crash=destroy" to "on_crash=preserve"
  2. in qubes.py, comment out self.force_shutdown() after failed qrexec_daemon start (around line 974)

then reproduce the crash, connect to the crashed domain via xl console. Collect the logs; then cleanup via xl destroy.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 31 Aug 2011 12:36 UTC
How long have you waited and after which message qvm-start hanged?

If dom0 had network connected (via qvm-dom0-network-via-netvm) and netvm was halted, dom0 left with ghost eth0. This causes long DNS timeouts (ex sudo tries to determinate hostname).

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 31 Aug 2011 12:36 UTC
How long have you waited and after which message qvm-start hanged?

If dom0 had network connected (via qvm-dom0-network-via-netvm) and netvm was halted, dom0 left with ghost eth0. This causes long DNS timeouts (ex sudo tries to determinate hostname).

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 1 Sep 2011 08:35 UTC
I think this is a dup of #336.

Member

marmarek commented Mar 8, 2015

Comment by joanna on 1 Sep 2011 08:35 UTC
I think this is a dup of #336.

@marmarek marmarek closed this Mar 8, 2015

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