On Sunday, December 4, 2016 at 10:27:19 PM UTC+1, Marek Marczykowski-Górecki 
wrote:
> What exactly you get when starting sys-net manually? Also, take a look
> at /var/log/libvirt/libxl/libxl-driver.log and
> /var/log/xen/console/hypervisor.log for any related messages. For
> example you can use `tail -f` while starting sys-net manually, to see
> what messages will show up there:
> 
>     sudo tail -f /var/log/libvirt/libxl/libxl-driver.log

It says cannot create qrexec-daemon.
During boot it says "Failed to start Qubes NetVM startup" and "Failed to start 
Start Qubes VM sys-net"(and some more for the other serviceVMs)

This is the log from libxl-driver.log:

[user@dom0 ~]$ sudo tail -f /var/log/libvirt/libxl/libxl-driver.log
2016-12-05 17:24:33 CET libxl: error: libxl_pci.c:1047:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device 0000:23:00.0
2016-12-05 17:24:33 CET libxl: error: libxl_pci.c:1047:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device 0000:23:00.2
2016-12-05 17:24:43 CET libxl: error: 
libxl_device.c:1269:libxl__wait_for_backend: Backend 
/local/domain/0/backend/pci/4/0 not ready
2016-12-05 17:24:43 CET libxl: error: libxl_pci.c:1321:do_pci_remove: 
xc_physdev_unmap_pirq irq=16: Invalid argument
2016-12-05 17:24:54 CET libxl: error: 
libxl_device.c:1269:libxl__wait_for_backend: Backend 
/local/domain/0/backend/pci/4/0 not ready
2016-12-05 17:24:54 CET libxl: error: libxl_pci.c:1047:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device 0000:23:00.0
2016-12-05 17:25:04 CET libxl: error: 
libxl_device.c:1269:libxl__wait_for_backend: Backend 
/local/domain/0/backend/pci/4/0 not ready
2016-12-05 17:25:04 CET libxl: error: libxl_pci.c:1321:do_pci_remove: 
xc_physdev_unmap_pirq irq=18: Invalid argument
2016-12-05 17:25:04 CET libxl: error: libxl_pci.c:1047:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device 0000:23:00.2
2016-12-05 17:25:14 CET libxl: error: 
libxl_device.c:1269:libxl__wait_for_backend: Backend 
/local/domain/0/backend/pci/4/0 not ready
2016-12-05 17:29:34 CET libxl: error: 
libxl_device.c:1269:libxl__wait_for_backend: Backend 
/local/domain/0/backend/pci/5/0 not ready
2016-12-05 17:29:45 CET libxl: error: 
libxl_device.c:1269:libxl__wait_for_backend: Backend 
/local/domain/0/backend/pci/5/0 not ready

and hypervisor.log:
[user@dom0 ~]$ sudo tail -f /var/log/xen/console/hypervisor.log
(XEN)    0000000000000000 ffffffff81c03f30 ffffffff81d53c6a 3e55772b4f5cc499
(XEN)    0000000000000000 ffffffff81c03f60 ffffffff81c03f5c 0000000000000000
(XEN)    0000000000000000 ffffffff81c03f40 ffffffff81d53339 ffffffff81c03ff8
(XEN)    ffffffff81d56b96 000206a700000000 0000000103100800 000000001f898b75
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 00010102464c457f
(XEN)    0000000000000000 00000001003e0003 00000000000009b0 0000000000000040
(XEN) d6v0 Unhandled invalid opcode fault/trap [#6, ec=0000]
(XEN) domain_crash_sync called from entry.S: fault at ffff82d08022c643 
create_bounce_frame+0x12b/0x13a
(XEN) Domain 6 (vcpu#0) crashed on cpu#3:
(XEN) ----[ Xen-4.6.3  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    3
(XEN) RIP:    e033:[<ffffffff81d57b3a>]
(XEN) RFLAGS: 0000000000000292   EM: 1   CONTEXT: pv guest (d6v0)
(XEN) rax: 0000000000000000   rbx: 0000000000012c00   rcx: 00000000ffffffff
(XEN) rdx: ffffffff81a3f810   rsi: 000000000000003f   rdi: 0000000000000000
(XEN) rbp: ffffffff81c03e70   rsp: ffffffff81c03da8   r8:  0000000000000011
(XEN) r9:  0000000000000168   r10: 0000000100000000   r11: 0000000000000000
(XEN) r12: 00000000000a9b00   r13: 0000000080000000   r14: 0000000111d00000
(XEN) r15: 0000000000000011   cr0: 0000000080050033   cr4: 00000000000426e0
(XEN) cr3: 0000000333409000   cr2: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=ffffffff81c03da8:
(XEN)    00000000ffffffff 0000000000000000 ffffffff81d57b3a 000000010000e030
(XEN)    0000000000010092 ffffffff81c03de8 000000000000e02b ffffffff81d57b3a
(XEN)    ffffffff81df7920 0000000000000000 0000000000000000 ffffffff81c03e10
(XEN)    ffffffff00000001 0000000000111d00 0000000000012c00 0000000012c00000
(XEN)    7ff0ffff81c03e88 ffffffff00000013 ffffffff81dfc020 db3d2ed3ec447c09
(XEN)    0000000001000000 ffffffff81c03f00 ffffffff81df7920 0000000000000000
(XEN)    0000000000000000 ffffffff81c03e88 ffffffff81d5e406 0000000001000000
(XEN)    ffffffff81c03ef0 ffffffff81d5bd08 ffffffff00000010 ffffffff81c03f00
(XEN)    ffffffff81c03eb8 db3d2ed3ec447c09 697a696c61697469 db3d2ed3ec447c09
(XEN)    ffffffffffffffff 0000000000000000 ffffffff81df7920 0000000000000000
(XEN)    0000000000000000 ffffffff81c03f30 ffffffff81d53c6a db3d2ed3ec447c09
(XEN)    0000000000000000 ffffffff81c03f60 ffffffff81c03f5c 0000000000000000
(XEN)    0000000000000000 ffffffff81c03f40 ffffffff81d53339 ffffffff81c03ff8
(XEN)    ffffffff81d56b96 000206a700000000 0000000101100800 000000001f898b75
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 00010102464c457f
(XEN)    0000000000000000 00000001003e0003 00000000000009b0 0000000000000040



> This sounds familiar. Try removing the network devices from sys-net to 
> see if it will start then. Next, re-add the network devices and try 
> starting sys-net again.
> 
> Chris
Yes, removing network devices from sys-net makes it possible to start it, 
forgot to re-add them and try again, I'll do that later.


-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/f95a23b8-557e-43b6-b84e-5daa87d0911a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to