You are not logged in.

#1 2017-02-19 09:39:50

dancinggrass
Member
Registered: 2015-04-17
Posts: 7

Xen: dom0 hangs on boot after all systemd service started

After installing and then reboot into Xen, it hangs after all the services for the dom0 started. I said this because when I see the log using journalctl, it shows that the services have started. Even the "Welcome to Arch Linux" banner displayed (which, I guess indicated that systemd has load all the services needed?). It hangs on the part where kernel spew some messages (I don't know what it's called), so the messages still there and it's not switching into login prompt.

I just installed xen from AUR and follow the instructions from the wiki, except the network part, since I just wanted to test the dom0. I also enabled the systemd services provided.

There's some catches tho, and I don't know if one these (or both) is the cause or not.

The first one is, I found failed attempt to login in journalctl. It seems that I can try to login, even when it only shows boot log.

Feb 19 14:34:49 Tyria login[470]: pam_unix(login:auth): check pass; user unknown
Feb 19 14:34:49 Tyria login[470]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost=
Feb 19 14:34:51 Tyria ntpd[600]: Listen normally on 7 net0 [fe80::96de:80ff:feba:8422%2]:123
Feb 19 14:34:51 Tyria ntpd[600]: new interface(s) found: waking up resolver
Feb 19 14:34:52 Tyria login[470]: FAILED LOGIN 1 FROM tty1 FOR a, Authentication failure
Feb 19 14:35:00 Tyria systemd[1]: Started Getty on tty3.
Feb 19 14:35:00 Tyria systemd[1]: Started Getty on tty2.

The second one is, somehow, systemd-load-modules failed loading some modules. I searched for solutions but I only found how to remove the error, not how to fix inserting those modules.
The failed modules (as well as systemd-load-modules log) is shown here:

Feb 19 14:34:46 Tyria systemd-journald[272]: System journal (/var/log/journal/b33f80594b744b99b3923f6acf17f7d3) is 832.0M, max 4.0G, 3.1G free.
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Inserted module 'xen_evtchn'
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Inserted module 'xen_gntdev'
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Inserted module 'xen_gntalloc'
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Inserted module 'xen_blkback'
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Inserted module 'xen_netback'
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Inserted module 'xen_pciback'
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Failed to find module 'evtchn'
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Failed to find module 'gntdev'
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Failed to find module 'netbk'
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Failed to find module 'blkbk'
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Failed to find module 'xen-scsibk' 
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Failed to find module 'usbbk'
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Failed to find module 'pciback'
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Inserted module 'xen_acpi_processor'
Feb 19 14:34:46 Tyria systemd-modules-load[268]: Failed to find module 'blktap2'

The last one is, I find these weird error and I don't really understand what this means. But I think it's the most probable cause. Here's the excerpt from journalctl:

Feb 19 14:34:46 Tyria kernel: VPMU disabled by hypervisor.
Feb 19 14:34:46 Tyria kernel: Performance Events: Haswell events, PMU not available due to virtualization, using software events only.
Feb 19 14:34:46 Tyria kernel: NMI watchdog: disabled (cpu0): hardware events not enabled
Feb 19 14:34:46 Tyria kernel: NMI watchdog: Shutting down hard lockup detector on all cpus
Feb 19 14:34:46 Tyria kernel: installing Xen timer for CPU 1
Feb 19 14:34:46 Tyria kernel: [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 0 APIC: 1
Feb 19 14:34:46 Tyria kernel: cpu 1 spinlock event irq 37
Feb 19 14:34:46 Tyria kernel: installing Xen timer for CPU 2
Feb 19 14:34:46 Tyria kernel: [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 0 APIC: 2
Feb 19 14:34:46 Tyria kernel: cpu 2 spinlock event irq 44
Feb 19 14:34:46 Tyria kernel: installing Xen timer for CPU 3
Feb 19 14:34:46 Tyria kernel: [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 0 APIC: 3
Feb 19 14:34:46 Tyria kernel: cpu 3 spinlock event irq 51
Feb 19 14:34:46 Tyria kernel: installing Xen timer for CPU 4
Feb 19 14:34:46 Tyria kernel: [Firmware Bug]: CPU4: APIC id mismatch. Firmware: 0 APIC: 4
Feb 19 14:34:46 Tyria kernel: cpu 4 spinlock event irq 58
Feb 19 14:34:46 Tyria kernel: installing Xen timer for CPU 5
Feb 19 14:34:46 Tyria kernel: [Firmware Bug]: CPU5: APIC id mismatch. Firmware: 0 APIC: 5
Feb 19 14:34:46 Tyria kernel: cpu 5 spinlock event irq 65
Feb 19 14:34:46 Tyria kernel: installing Xen timer for CPU 6
Feb 19 14:34:46 Tyria kernel: [Firmware Bug]: CPU6: APIC id mismatch. Firmware: 0 APIC: 6
Feb 19 14:34:46 Tyria kernel: cpu 6 spinlock event irq 72
Feb 19 14:34:46 Tyria kernel: installing Xen timer for CPU 7
Feb 19 14:34:46 Tyria kernel: [Firmware Bug]: CPU7: APIC id mismatch. Firmware: 0 APIC: 7
Feb 19 14:34:46 Tyria kernel: cpu 7 spinlock event irq 79
Feb 19 14:34:46 Tyria kernel: x86: Booted up 1 node, 8 CPUs

I don't know if there's something else that might cause this behavior, so I'll provide some other things that might be useful
Full journalctl report: http://ix.io/nu2
lscpu: http://ix.io/ntX

What should I do to fix this? Thank you.

Edit: I'm able to login to user, but the display is still not changing, it only give the booting messages

Last edited by dancinggrass (2017-02-20 03:47:22)

Offline

Board footer

Powered by FluxBB