[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] CentOS 7 domU PV hang while booting after migration


the ext4 filesys in C7 defaults with the 64bit feature enabled, which is not supported by e2fsprogs in C6. This matters because pygrub in C6 needs to mount the domU filesys.

If your previous bootloader was different than pygrub, maybe you got away with the filesys conflict (maybe using pv-grub).

If you try and mount your domU from dom0 in a normal way (using mount) you can confirm if this is an issue.

You can check the ext4 features of a filesys with:
>dumpe2fs -h /dev/VG/LV

when the LVM is unmounted.
the relevant lines are below (ext4 with ^64bit, disabled):
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize

##xen-packaging on freenode IRC

On Wednesday, May 30, 2018, 5:13:13 AM PDT, Karl Johnson <karljohnson.it@xxxxxxxxx> wrote:


I've migrated a domU PV from a host to another using offline rsync (ext4 on LVM) and the domU fail to completely boot on the new host. It hangs at the following line but keep running and using 5% vCPU:

         Starting Switch Root...
[    2.570317] systemd-journald[91]: Received SIGTERM from PID 1 (systemd).
[    2.628091] random: crng init done
[    2.724668] SELinux:  Disabled at runtime.
[    2.754091] type=1404 audit(1527618117.711:2): selinux=0 auid=4294967295 ses=4294967295
[    2.803603] ip_tables: (C) 2000-2006 Netfilter Core Team

I have to xl destroy it. The only difference would be Xen 4.6.3 on the old host while the new is on 4.8.3. Is there any way to troubleshoot this issue?

Any suggestions would be appreciated. Thanks.


Xen-users mailing list
Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.