NetVM didn't start on system boot

[marmarek]

Reported by joanna on 3 Jan 2012 07:41 UTC
Later in the log I found this:

[xen](joanna@dom0)$ cat xl-netvm.log.1
Waiting for domain netvm (domid 1) to die [2150](pid)
Domain 1 is dead
Unknown shutdown reason code 255. Destroying domain.
Action for shutdown reason code 255 is destroy
Domain 1 needs to be cleaned up: destroying the domain
Done. Exiting now

After the system booted up, I logged in and start the netvm manually (qvm-run) without any problem...

Migrated-From: https://wiki.qubes-os.org/ticket/403

[marmarek]

Comment by marmarek on 3 Jan 2012 09:15 UTC
Can you send/paste /var/log/boot.log?

[marmarek]

Comment by marmarek on 3 Jan 2012 09:15 UTC
Can you send/paste /var/log/boot.log?

[marmarek]

Comment by joanna on 3 Jan 2012 10:02 UTC
For some reason the boot.log is NULL on my system currently.

But it looked like if it timed out on the the qrexec connect waiting loop. So, it seems that domain crashed with this err=255 code immediately after it got created and that's way qrexec couldn't connect.

[marmarek]

Comment by joanna on 3 Jan 2012 10:02 UTC
For some reason the boot.log is NULL on my system currently.

But it looked like if it timed out on the the qrexec connect waiting loop. So, it seems that domain crashed with this err=255 code immediately after it got created and that's way qrexec couldn't connect.

[marmarek]

Comment by joanna on 18 Jan 2012 10:11 UTC
Seems on now, with the new systemd.

[marmarek]

Comment by joanna on 18 Jan 2012 10:11 UTC
Seems on now, with the new systemd.