| Summary: | app-emulation/xen-4.4.0 with kernel 3.14.1 in dom0 - fails to load modules / panic | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Another Mortal <a.m> |
| Component: | [OLD] Core system | Assignee: | Gentoo Xen Devs <xen> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
syslog excerpt
emerge —info xen config-3.14.1-gentoo config-3.14.1-hardened |
||
It would be great if you can provide 1) emerge --info app-emulation/xen 2) full kernel config file don't know the exact reason, but from "page allocation failure", which means it unable to load kernel module due to fail to allocate vm memory. how much memory do you reserve for dom0? try to switch to openrc? did systemd consume too much memory? Created attachment 376008 [details]
emerge —info xen
Created attachment 376010 [details]
config-3.14.1-gentoo
Created attachment 376012 [details]
config-3.14.1-hardened
The output from ‘emerge —info xen’ and the kernel config files are now attached. > how much memory do you reserve for dom0? 4GB > try to switch to openrc? did systemd consume too much memory? This box uses openrc already. Any trace of systemd must be due to udev. almost 2 months now, a.m. what's ths current status? No idea. Sorry... I did switch to KVM. Got fed up with all the cruft around Xen. Good luck! |
Created attachment 375582 [details] syslog excerpt Hmm… it looks like we have a _killer_ combination here. * xen-4.4.0 + hardened-sources-3.14.1 panic on one box unable to load modules on another * xen-4.4.0 + gentoo-sources-3.14.1 panic on the box that could not load modules I haven’t bothered trying on the other one Unfortunately, I could not capture output for the panics, but I’m attaching a syslog excerpt for the modprobe issue. Interestingly, xen-4.4.0 + hardened-sources-3.13.9 works fine on both. Also, both gentoo and hardened 3.14.1 kernels by themselves work fine. Here are the kernel settings relevant to Xen: ----- CONFIG_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=500 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_PVH is not set CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=m CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_NETDEV_BACKEND=y CONFIG_INPUT_XEN_KBDDEV_FRONTEND=m CONFIG_HVC_XEN=y CONFIG_HVC_XEN_FRONTEND=y CONFIG_TCG_XEN=m CONFIG_XEN_WDT=m CONFIG_XEN_FBDEV_FRONTEND=m # CONFIG_XEN_BALLOON is not set CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XENFS=y CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=y CONFIG_XEN_GNTDEV=y CONFIG_XEN_GRANT_DEV_ALLOC=y CONFIG_SWIOTLB_XEN=y CONFIG_XEN_TMEM=m CONFIG_XEN_PCIDEV_BACKEND=y CONFIG_XEN_PRIVCMD=y CONFIG_XEN_HAVE_PVMMU=y —— PS: I think I’ll just switch to KVM...