I'm working on booting Xen 4.5 on an opensuse 13.2 GRUB2+UEFI box. The system fully boots to non-Xen, kernel-default.
In the Xen case, Until Xen 4.6 comes available, I have grub2 chainloading xen.efi. The .efi is found, Xen loads, and hands off to the kernel-xen boot process. It gets fairly far then gets caught in a systemd-journal loop. Output at serial console is Xen 4.5.0_03-361 (c/s ) EFI loader Using configuration file 'xen.cfg' vmlinuz-xen: 0x000000008c0d1000-0x000000008c5aaf10 initrd-xen: 0x000000008b346000-0x000000008c0d0c78 0x0000:0x00:0x19.0x0: ROM: 0x10000 bytes at 0x92963018 0x0000:0x04:0x00.0x0: ROM: 0x8000 bytes at 0x92953018 0x0000:0x10:0x00.0x0: ROM: 0x10800 bytes at 0x9293b018 Xen 4.5.0_03-361 (XEN) Xen version 4.5.0_03-361 ([email protected]) (gcc (SUSE Linux) 4.8.3 20140627 [gcc-4_8-branch revision 212064]) debug=n Mon Mar 16 16:14:15 UTC 2015 ... (XEN) [2015-04-06 10:45:44] Xen is relinquishing VGA console. (XEN) [2015-04-06 10:45:44] *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) [2015-04-06 10:45:44] Freed 316kB init memory. [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.19.3-1.gf10e7fc-xen (geeko@buildhost) (gcc version 4.8.3 20141208 [gcc-4_8-branch revision 218481] (SUSE Linux) ) #1 SMP Thu Mar 26 17:34:34 UTC 2015 (f10e7fc) ... [ 218.221315] systemd[1]: Accepted new private connection. [ 218.238825] systemd[1]: Got message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/agent interface=org.freedesktop.systemd1.Agent member=Released cookie=1 reply_cookie=0 error=n/a [ 218.238841] systemd-journald[896]: Entry is too big with 8 properties and 16924204553027465025 bytes, ignoring. [ 218.331936] systemd[1]: Got disconnect on private connection. [ 240.000517] systemd[1]: Got notification message for unit systemd-journald.service [ 240.024839] systemd[1]: systemd-journald.service: Got notification message from PID 896 (WATCHDOG=1...) ... [ 478.806639] systemd[1]: systemd-journald.service: got WATCHDOG=1 [ 478.826279] systemd[1]: Got notification message for unit systemd-journald.service [ 478.850591] systemd[1]: systemd-journald.service: Got notification message from PID 896 (WATCHDOG=1...) [ 478.882226] systemd[1]: systemd-journald.service: got WATCHDOG=1 ... [ 820.076223] systemd[1]: Got notification message for unit systemd-journald.service [ 820.100546] systemd[1]: systemd-journald.service: Got notification message from PID 896 (WATCHDOG=1...) [ 820.132191] systemd[1]: systemd-journald.service: got WATCHDOG=1 Notice the ridiculously large 'bytes' value in [ 218.238841] systemd-journald[896]: Entry is too big with 8 properties and 16924204553027465025 bytes, ignoring. Usually I'd use systemd journal & serial console to debug this. But it looks like those are the problem here. How do I get more detail out of logs to figure out what's causing this problem? LT -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
