* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure [not found] ` <9fc0a827-b452-50bb-6923-3a650b104b56@gmail.com> @ 2016-09-27 5:31 ` Juergen Gross 2016-09-27 11:13 ` Sven Köhler 0 siblings, 1 reply; 16+ messages in thread From: Juergen Gross @ 2016-09-27 5:31 UTC (permalink / raw) To: Sven Köhler, xen-devel Continuing the thread on xen-devel. On 27/09/16 00:48, Sven Köhler wrote: > Am 26.09.2016 um 07:43 schrieb Juergen Gross: >> On 25/09/16 18:04, Sven Köhler wrote: >>> Hi, >>> >>> I'm experiencing the bug below which was discussed on xen-devel December >>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>> >>> The bug only seems to occur with the last domU booted on my machine. >>> Where do I find a patch that fixes that? >> >> The issue back in December was fixed by commit >> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >> Either gentoo didn't update to the official Xen 4.7 release (including >> pvgrub) or you are seeing a new issue. > > From the looks of it, the Gentoo package is using the grub from the > xen-4.7.0 tarball. > > I downgraded to pvgrub 4.6.3 and the problem went away. > > So I assume I'm seeing a new issue. How do I debug it? Interesting. Just tested it on upstream Xen and saw the same problem with a rather old guest kernel (3.0 based, xen flavor), while a newer kernel (4.1, pvops) is working. Can you give me some more details about the kernel you are trying to boot? I'll investigate further. In case you feel adventurous and want to do some debugging yourself: You need to build Xen from the sources. Your scenario includes debugging of Xen tools (probably the domain builder in tools/libxc), Mini-OS (extras/mini-os-remote) and grub (stubdom/grub-upstream). All paths mentioned are in the xen tree, some might be created only during first build. Juergen >>> Once I find a patch to address the issue, I will also forward it to the >>> Gentoo maintainers via their bugzilla. >>> >>> >>> Kind Regards, >>> Sven >>> >>> >>> output of xl create -c: >>> >>> Booting 'Gentoo' >>> >>> root (hd0) >>> Filesystem type is ext2fs, using whole disk >>> kernel /boot/vmlinuz ro root=/dev/xvda1 rootfstype=ext4 >>> >>> ============= Init TPM Front ================ >>> Tpmfront:Error Unable to read device/vtpm/0/backend-id during tpmfront >>> initialization! error = ENOENT >>> Tpmfront:Info Shutting down tpmfront >>> pin_table(x) returned 28993 >>> >>> Error 9: Unknown boot failure >>> >>> Press any key to continue... >>> >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> https://lists.xen.org/xen-users >>> >> > _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure 2016-09-27 5:31 ` [Xen-users] pvgrub: Error 9: Unknown boot failure Juergen Gross @ 2016-09-27 11:13 ` Sven Köhler 2016-09-27 12:02 ` Juergen Gross 0 siblings, 1 reply; 16+ messages in thread From: Sven Köhler @ 2016-09-27 11:13 UTC (permalink / raw) To: Juergen Gross, xen-devel [-- Attachment #1: Type: text/plain, Size: 2577 bytes --] Am 27.09.2016 um 07:31 schrieb Juergen Gross: > On 27/09/16 00:48, Sven Köhler wrote: >> Am 26.09.2016 um 07:43 schrieb Juergen Gross: >>> On 25/09/16 18:04, Sven Köhler wrote: >>>> Hi, >>>> >>>> I'm experiencing the bug below which was discussed on xen-devel December >>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>>> >>>> The bug only seems to occur with the last domU booted on my machine. >>>> Where do I find a patch that fixes that? >>> >>> The issue back in December was fixed by commit >>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >>> Either gentoo didn't update to the official Xen 4.7 release (including >>> pvgrub) or you are seeing a new issue. >> >> From the looks of it, the Gentoo package is using the grub from the >> xen-4.7.0 tarball. >> >> I downgraded to pvgrub 4.6.3 and the problem went away. >> >> So I assume I'm seeing a new issue. How do I debug it? > > Interesting. Just tested it on upstream Xen and saw the same problem > with a rather old guest kernel (3.0 based, xen flavor), while a newer > kernel (4.1, pvops) is working. > > Can you give me some more details about the kernel you are trying to > boot? It's an unmodified 4.4.21 kernel which I compile by hand. The config is attached. Does that help? > I'll investigate further. > > In case you feel adventurous and want to do some debugging yourself: > You need to build Xen from the sources. Your scenario includes debugging > of Xen tools (probably the domain builder in tools/libxc), Mini-OS > (extras/mini-os-remote) and grub (stubdom/grub-upstream). All paths > mentioned are in the xen tree, some might be created only during first > build. > > > Juergen > >>>> Once I find a patch to address the issue, I will also forward it to the >>>> Gentoo maintainers via their bugzilla. >>>> >>>> >>>> Kind Regards, >>>> Sven >>>> >>>> >>>> output of xl create -c: >>>> >>>> Booting 'Gentoo' >>>> >>>> root (hd0) >>>> Filesystem type is ext2fs, using whole disk >>>> kernel /boot/vmlinuz ro root=/dev/xvda1 rootfstype=ext4 >>>> >>>> ============= Init TPM Front ================ >>>> Tpmfront:Error Unable to read device/vtpm/0/backend-id during tpmfront >>>> initialization! error = ENOENT >>>> Tpmfront:Info Shutting down tpmfront >>>> pin_table(x) returned 28993 >>>> >>>> Error 9: Unknown boot failure >>>> >>>> Press any key to continue... >>>> >>>> >>>> >>>> _______________________________________________ >>>> Xen-users mailing list >>>> Xen-users@lists.xen.org >>>> https://lists.xen.org/xen-users >>>> >>> >> > [-- Attachment #2: config-4.4.21 --] [-- Type: text/plain, Size: 47849 bytes --] # # Automatically generated file; DO NOT EDIT. # Linux/x86 4.4.21 Kernel Configuration # CONFIG_64BIT=y CONFIG_X86_64=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_MMU=y CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_ARCH_WANT_GENERAL_HUGETLB=y CONFIG_ZONE_DMA32=y CONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_X86_64_SMP=y CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_PGTABLE_LEVELS=4 CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_EXTABLE_SORT=y # # General setup # CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE="" # CONFIG_COMPILE_TEST is not set CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_HAVE_KERNEL_LZ4=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set # CONFIG_KERNEL_XZ is not set # CONFIG_KERNEL_LZO is not set # CONFIG_KERNEL_LZ4 is not set CONFIG_DEFAULT_HOSTNAME="(none)" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y CONFIG_CROSS_MEMORY_ATTACH=y CONFIG_FHANDLE=y # CONFIG_USELIB is not set # CONFIG_AUDIT is not set CONFIG_HAVE_ARCH_AUDITSYSCALL=y # # IRQ subsystem # CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_IRQ_DOMAIN=y CONFIG_IRQ_DOMAIN_HIERARCHY=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_ARCH_CLOCKSOURCE_DATA=y CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y CONFIG_GENERIC_CMOS_UPDATE=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ_COMMON=y # CONFIG_HZ_PERIODIC is not set CONFIG_NO_HZ_IDLE=y # CONFIG_NO_HZ_FULL is not set # CONFIG_NO_HZ is not set CONFIG_HIGH_RES_TIMERS=y # # CPU/Task time and stats accounting # CONFIG_VIRT_CPU_ACCOUNTING=y # CONFIG_TICK_CPU_ACCOUNTING is not set CONFIG_VIRT_CPU_ACCOUNTING_GEN=y # CONFIG_IRQ_TIME_ACCOUNTING is not set # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y # # RCU Subsystem # CONFIG_TREE_RCU=y # CONFIG_RCU_EXPERT is not set CONFIG_SRCU=y # CONFIG_TASKS_RCU is not set CONFIG_RCU_STALL_COMMON=y CONFIG_CONTEXT_TRACKING=y CONFIG_CONTEXT_TRACKING_FORCE=y # CONFIG_TREE_RCU_TRACE is not set # CONFIG_RCU_EXPEDITE_BOOT is not set CONFIG_BUILD_BIN2C=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=16 CONFIG_LOG_CPU_MAX_BUF_SHIFT=13 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=y CONFIG_ARCH_SUPPORTS_INT128=y # CONFIG_CGROUPS is not set # CONFIG_CHECKPOINT_RESTORE is not set CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y # CONFIG_SCHED_AUTOGROUP is not set # CONFIG_SYSFS_DEPRECATED is not set # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y CONFIG_HAVE_UID16=y CONFIG_SYSCTL_EXCEPTION_TRACE=y CONFIG_HAVE_PCSPKR_PLATFORM=y CONFIG_BPF=y # CONFIG_EXPERT is not set CONFIG_UID16=y CONFIG_MULTIUSER=y CONFIG_SGETMASK_SYSCALL=y CONFIG_SYSFS_SYSCALL=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y # CONFIG_BPF_SYSCALL is not set CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_ADVISE_SYSCALLS=y # CONFIG_USERFAULTFD is not set CONFIG_MEMBARRIER=y # CONFIG_EMBEDDED is not set CONFIG_HAVE_PERF_EVENTS=y # # Kernel Performance Events And Counters # CONFIG_PERF_EVENTS=y CONFIG_VM_EVENT_COUNTERS=y # CONFIG_COMPAT_BRK is not set CONFIG_SLAB=y # CONFIG_SLUB is not set # CONFIG_SYSTEM_DATA_VERIFICATION is not set # CONFIG_PROFILING is not set CONFIG_HAVE_OPROFILE=y CONFIG_OPROFILE_NMI_TIMER=y # CONFIG_KPROBES is not set # CONFIG_JUMP_LABEL is not set # CONFIG_UPROBES is not set # CONFIG_HAVE_64BIT_ALIGNED_ACCESS is not set CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_ARCH_USE_BUILTIN_BSWAP=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_OPTPROBES=y CONFIG_HAVE_KPROBES_ON_FTRACE=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_ATTRS=y CONFIG_HAVE_DMA_CONTIGUOUS=y CONFIG_GENERIC_SMP_IDLE_THREAD=y CONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT=y CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y CONFIG_HAVE_DMA_API_DEBUG=y CONFIG_HAVE_HW_BREAKPOINT=y CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y CONFIG_HAVE_USER_RETURN_NOTIFIER=y CONFIG_HAVE_PERF_EVENTS_NMI=y CONFIG_HAVE_PERF_REGS=y CONFIG_HAVE_PERF_USER_STACK_DUMP=y CONFIG_HAVE_ARCH_JUMP_LABEL=y CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y CONFIG_HAVE_CMPXCHG_LOCAL=y CONFIG_HAVE_CMPXCHG_DOUBLE=y CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=y CONFIG_ARCH_WANT_OLD_COMPAT_IPC=y CONFIG_HAVE_ARCH_SECCOMP_FILTER=y CONFIG_SECCOMP_FILTER=y CONFIG_HAVE_CC_STACKPROTECTOR=y # CONFIG_CC_STACKPROTECTOR is not set CONFIG_CC_STACKPROTECTOR_NONE=y # CONFIG_CC_STACKPROTECTOR_REGULAR is not set # CONFIG_CC_STACKPROTECTOR_STRONG is not set CONFIG_HAVE_CONTEXT_TRACKING=y CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y CONFIG_HAVE_ARCH_HUGE_VMAP=y CONFIG_HAVE_ARCH_SOFT_DIRTY=y CONFIG_MODULES_USE_ELF_RELA=y CONFIG_HAVE_IRQ_EXIT_ON_IRQ_STACK=y CONFIG_ARCH_HAS_ELF_RANDOMIZE=y CONFIG_HAVE_COPY_THREAD_TLS=y CONFIG_OLD_SIGSUSPEND3=y CONFIG_COMPAT_OLD_SIGACTION=y # # GCOV-based kernel profiling # CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 CONFIG_MODULES=y # CONFIG_MODULE_FORCE_LOAD is not set CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set # CONFIG_MODULE_SIG is not set # CONFIG_MODULE_COMPRESS is not set CONFIG_MODULES_TREE_LOOKUP=y CONFIG_BLOCK=y CONFIG_BLK_DEV_BSG=y # CONFIG_BLK_DEV_BSGLIB is not set CONFIG_BLK_DEV_INTEGRITY=y # CONFIG_BLK_CMDLINE_PARSER is not set # # Partition Types # # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=y CONFIG_EFI_PARTITION=y CONFIG_BLOCK_COMPAT=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" CONFIG_PADATA=y CONFIG_ASN1=m CONFIG_INLINE_SPIN_UNLOCK_IRQ=y CONFIG_INLINE_READ_UNLOCK=y CONFIG_INLINE_READ_UNLOCK_IRQ=y CONFIG_INLINE_WRITE_UNLOCK=y CONFIG_INLINE_WRITE_UNLOCK_IRQ=y CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y CONFIG_MUTEX_SPIN_ON_OWNER=y CONFIG_RWSEM_SPIN_ON_OWNER=y CONFIG_LOCK_SPIN_ON_OWNER=y CONFIG_ARCH_USE_QUEUED_SPINLOCKS=y CONFIG_QUEUED_SPINLOCKS=y CONFIG_ARCH_USE_QUEUED_RWLOCKS=y CONFIG_QUEUED_RWLOCKS=y CONFIG_FREEZER=y # # Processor type and features # CONFIG_ZONE_DMA=y CONFIG_SMP=y CONFIG_X86_FEATURE_NAMES=y # CONFIG_X86_X2APIC is not set CONFIG_X86_MPPARSE=y # CONFIG_X86_EXTENDED_PLATFORM is not set CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_HYPERVISOR_GUEST=y CONFIG_PARAVIRT=y CONFIG_PARAVIRT_SPINLOCKS=y CONFIG_XEN=y CONFIG_XEN_512GB=y CONFIG_XEN_SAVE_RESTORE=y # CONFIG_KVM_GUEST is not set CONFIG_PARAVIRT_TIME_ACCOUNTING=y CONFIG_PARAVIRT_CLOCK=y CONFIG_NO_BOOTMEM=y # CONFIG_MK8 is not set # CONFIG_MPSC is not set CONFIG_MCORE2=y # CONFIG_MATOM is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_INTERNODE_CACHE_SHIFT=6 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_P6_NOP=y CONFIG_X86_TSC=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_DEBUGCTLMSR=y CONFIG_CPU_SUP_INTEL=y CONFIG_CPU_SUP_AMD=y CONFIG_CPU_SUP_CENTAUR=y CONFIG_HPET_TIMER=y CONFIG_DMI=y CONFIG_SWIOTLB=y CONFIG_IOMMU_HELPER=y CONFIG_NR_CPUS=16 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y # CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set # CONFIG_X86_MCE is not set # CONFIG_VM86 is not set CONFIG_X86_16BIT=y CONFIG_X86_ESPFIX64=y CONFIG_X86_VSYSCALL_EMULATION=y # CONFIG_I8K is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set CONFIG_ARCH_PHYS_ADDR_T_64BIT=y CONFIG_ARCH_DMA_ADDR_T_64BIT=y CONFIG_X86_DIRECT_GBPAGES=y # CONFIG_NUMA is not set CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_MEMORY_PROBE=y CONFIG_ARCH_PROC_KCORE_TEXT=y CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000 CONFIG_SELECT_MEMORY_MODEL=y CONFIG_SPARSEMEM_MANUAL=y CONFIG_SPARSEMEM=y CONFIG_HAVE_MEMORY_PRESENT=y CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y CONFIG_SPARSEMEM_VMEMMAP=y CONFIG_HAVE_MEMBLOCK=y CONFIG_HAVE_MEMBLOCK_NODE_MAP=y CONFIG_ARCH_DISCARD_MEMBLOCK=y CONFIG_MEMORY_ISOLATION=y CONFIG_HAVE_BOOTMEM_INFO_NODE=y CONFIG_MEMORY_HOTPLUG=y CONFIG_MEMORY_HOTPLUG_SPARSE=y CONFIG_MEMORY_HOTREMOVE=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=y CONFIG_COMPACTION=y CONFIG_MIGRATION=y CONFIG_PHYS_ADDR_T_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y # CONFIG_KSM is not set CONFIG_DEFAULT_MMAP_MIN_ADDR=4096 CONFIG_TRANSPARENT_HUGEPAGE=y CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y # CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not set # CONFIG_CLEANCACHE is not set # CONFIG_FRONTSWAP is not set # CONFIG_CMA is not set # CONFIG_ZPOOL is not set # CONFIG_ZBUD is not set # CONFIG_ZSMALLOC is not set CONFIG_GENERIC_EARLY_IOREMAP=y CONFIG_ARCH_SUPPORTS_DEFERRED_STRUCT_PAGE_INIT=y # CONFIG_DEFERRED_STRUCT_PAGE_INIT is not set # CONFIG_IDLE_PAGE_TRACKING is not set # CONFIG_X86_PMEM_LEGACY is not set # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set CONFIG_X86_RESERVE_LOW=64 CONFIG_MTRR=y # CONFIG_MTRR_SANITIZER is not set CONFIG_X86_PAT=y CONFIG_ARCH_USES_PG_UNCACHED=y CONFIG_ARCH_RANDOM=y CONFIG_X86_SMAP=y # CONFIG_X86_INTEL_MPX is not set CONFIG_SECCOMP=y CONFIG_HZ_100=y # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set # CONFIG_HZ_1000 is not set CONFIG_HZ=100 CONFIG_SCHED_HRTICK=y # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x1000000 # CONFIG_RELOCATABLE is not set CONFIG_PHYSICAL_ALIGN=0x1000000 CONFIG_HOTPLUG_CPU=y # CONFIG_BOOTPARAM_HOTPLUG_CPU0 is not set # CONFIG_DEBUG_HOTPLUG_CPU0 is not set # CONFIG_COMPAT_VDSO is not set # CONFIG_LEGACY_VSYSCALL_NATIVE is not set CONFIG_LEGACY_VSYSCALL_EMULATE=y # CONFIG_LEGACY_VSYSCALL_NONE is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_MODIFY_LDT_SYSCALL=y CONFIG_HAVE_LIVEPATCH=y CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y # # Power management and ACPI options # # CONFIG_SUSPEND is not set CONFIG_HIBERNATE_CALLBACKS=y # CONFIG_HIBERNATION is not set CONFIG_PM_SLEEP=y CONFIG_PM_SLEEP_SMP=y # CONFIG_PM_AUTOSLEEP is not set # CONFIG_PM_WAKELOCKS is not set CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set # CONFIG_SFI is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # CPU Idle # # CONFIG_CPU_IDLE is not set # CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not set # # Memory power savings # # CONFIG_I7300_IDLE is not set # # Bus options (PCI etc.) # # CONFIG_PCI is not set CONFIG_PCI_LABEL=y CONFIG_ISA_DMA_API=y # CONFIG_PCCARD is not set # CONFIG_X86_SYSFB is not set # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_COMPAT_BINFMT_ELF=y # CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set CONFIG_BINFMT_SCRIPT=y # CONFIG_HAVE_AOUT is not set CONFIG_BINFMT_MISC=y CONFIG_COREDUMP=y CONFIG_IA32_EMULATION=y CONFIG_IA32_AOUT=y # CONFIG_X86_X32 is not set CONFIG_COMPAT=y CONFIG_COMPAT_FOR_U64_ALIGNMENT=y CONFIG_SYSVIPC_COMPAT=y CONFIG_KEYS_COMPAT=y CONFIG_X86_DEV_DMA_OPS=y CONFIG_NET=y CONFIG_NET_INGRESS=y # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_DIAG=m CONFIG_UNIX=y CONFIG_UNIX_DIAG=m CONFIG_XFRM=y CONFIG_XFRM_ALGO=m # CONFIG_XFRM_USER is not set # CONFIG_XFRM_SUB_POLICY is not set # CONFIG_XFRM_MIGRATE is not set # CONFIG_XFRM_STATISTICS is not set CONFIG_XFRM_IPCOMP=m # CONFIG_NET_KEY is not set CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y # CONFIG_IP_FIB_TRIE_STATS is not set CONFIG_IP_MULTIPLE_TABLES=y # CONFIG_IP_ROUTE_MULTIPATH is not set # CONFIG_IP_ROUTE_VERBOSE is not set CONFIG_IP_ROUTE_CLASSID=y # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE_DEMUX is not set CONFIG_NET_IP_TUNNEL=m # CONFIG_IP_MROUTE is not set CONFIG_SYN_COOKIES=y # CONFIG_NET_UDP_TUNNEL is not set # CONFIG_NET_FOU is not set # CONFIG_NET_FOU_IP_TUNNELS is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_XFRM_TUNNEL is not set CONFIG_INET_TUNNEL=m # CONFIG_INET_XFRM_MODE_TRANSPORT is not set # CONFIG_INET_XFRM_MODE_TUNNEL is not set # CONFIG_INET_XFRM_MODE_BEET is not set # CONFIG_INET_LRO is not set CONFIG_INET_DIAG=m CONFIG_INET_TCP_DIAG=m CONFIG_INET_UDP_DIAG=m # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_CUBIC=y CONFIG_DEFAULT_TCP_CONG="cubic" # CONFIG_TCP_MD5SIG is not set CONFIG_IPV6=m # CONFIG_IPV6_ROUTER_PREF is not set # CONFIG_IPV6_OPTIMISTIC_DAD is not set CONFIG_INET6_AH=m CONFIG_INET6_ESP=m CONFIG_INET6_IPCOMP=m CONFIG_IPV6_MIP6=m # CONFIG_IPV6_ILA is not set CONFIG_INET6_XFRM_TUNNEL=m CONFIG_INET6_TUNNEL=m CONFIG_INET6_XFRM_MODE_TRANSPORT=m CONFIG_INET6_XFRM_MODE_TUNNEL=m CONFIG_INET6_XFRM_MODE_BEET=m CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m CONFIG_IPV6_VTI=m CONFIG_IPV6_SIT=m # CONFIG_IPV6_SIT_6RD is not set CONFIG_IPV6_NDISC_NODETYPE=y CONFIG_IPV6_TUNNEL=m CONFIG_IPV6_GRE=m # CONFIG_IPV6_MULTIPLE_TABLES is not set # CONFIG_IPV6_MROUTE is not set # CONFIG_NETWORK_SECMARK is not set # CONFIG_NET_PTP_CLASSIFY is not set # CONFIG_NETWORK_PHY_TIMESTAMPING is not set CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set CONFIG_NETFILTER_ADVANCED=y # CONFIG_BRIDGE_NETFILTER is not set # # Core Netfilter Configuration # CONFIG_NETFILTER_INGRESS=y CONFIG_NETFILTER_NETLINK=m CONFIG_NETFILTER_NETLINK_ACCT=m CONFIG_NETFILTER_NETLINK_QUEUE=m CONFIG_NETFILTER_NETLINK_LOG=m CONFIG_NF_CONNTRACK=m CONFIG_NF_LOG_COMMON=m CONFIG_NF_CONNTRACK_MARK=y # CONFIG_NF_CONNTRACK_ZONES is not set # CONFIG_NF_CONNTRACK_PROCFS is not set # CONFIG_NF_CONNTRACK_EVENTS is not set CONFIG_NF_CONNTRACK_TIMEOUT=y # CONFIG_NF_CONNTRACK_TIMESTAMP is not set CONFIG_NF_CONNTRACK_LABELS=y CONFIG_NF_CT_PROTO_DCCP=m CONFIG_NF_CT_PROTO_GRE=m CONFIG_NF_CT_PROTO_SCTP=m CONFIG_NF_CT_PROTO_UDPLITE=m CONFIG_NF_CONNTRACK_AMANDA=m CONFIG_NF_CONNTRACK_FTP=m CONFIG_NF_CONNTRACK_H323=m CONFIG_NF_CONNTRACK_IRC=m CONFIG_NF_CONNTRACK_BROADCAST=m CONFIG_NF_CONNTRACK_NETBIOS_NS=m CONFIG_NF_CONNTRACK_SNMP=m CONFIG_NF_CONNTRACK_PPTP=m CONFIG_NF_CONNTRACK_SANE=m CONFIG_NF_CONNTRACK_SIP=m CONFIG_NF_CONNTRACK_TFTP=m CONFIG_NF_CT_NETLINK=m CONFIG_NF_CT_NETLINK_TIMEOUT=m CONFIG_NF_CT_NETLINK_HELPER=m CONFIG_NETFILTER_NETLINK_GLUE_CT=y CONFIG_NF_NAT=m CONFIG_NF_NAT_NEEDED=y CONFIG_NF_NAT_PROTO_DCCP=m CONFIG_NF_NAT_PROTO_UDPLITE=m CONFIG_NF_NAT_PROTO_SCTP=m CONFIG_NF_NAT_AMANDA=m CONFIG_NF_NAT_FTP=m CONFIG_NF_NAT_IRC=m CONFIG_NF_NAT_SIP=m CONFIG_NF_NAT_TFTP=m CONFIG_NF_NAT_REDIRECT=m CONFIG_NETFILTER_SYNPROXY=m CONFIG_NF_TABLES=m CONFIG_NF_TABLES_INET=m CONFIG_NF_TABLES_NETDEV=m CONFIG_NFT_EXTHDR=m CONFIG_NFT_META=m CONFIG_NFT_CT=m CONFIG_NFT_RBTREE=m CONFIG_NFT_HASH=m CONFIG_NFT_COUNTER=m CONFIG_NFT_LOG=m CONFIG_NFT_LIMIT=m CONFIG_NFT_MASQ=m CONFIG_NFT_REDIR=m CONFIG_NFT_NAT=m CONFIG_NFT_QUEUE=m CONFIG_NFT_REJECT=m CONFIG_NFT_REJECT_INET=m CONFIG_NFT_COMPAT=m CONFIG_NETFILTER_XTABLES=m # # Xtables combined modules # CONFIG_NETFILTER_XT_MARK=m CONFIG_NETFILTER_XT_CONNMARK=m CONFIG_NETFILTER_XT_SET=m # # Xtables targets # CONFIG_NETFILTER_XT_TARGET_CHECKSUM=m CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m CONFIG_NETFILTER_XT_TARGET_CONNMARK=m CONFIG_NETFILTER_XT_TARGET_CT=m CONFIG_NETFILTER_XT_TARGET_DSCP=m CONFIG_NETFILTER_XT_TARGET_HL=m CONFIG_NETFILTER_XT_TARGET_HMARK=m CONFIG_NETFILTER_XT_TARGET_IDLETIMER=m CONFIG_NETFILTER_XT_TARGET_LOG=m CONFIG_NETFILTER_XT_TARGET_MARK=m CONFIG_NETFILTER_XT_NAT=m CONFIG_NETFILTER_XT_TARGET_NETMAP=m CONFIG_NETFILTER_XT_TARGET_NFLOG=m CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m # CONFIG_NETFILTER_XT_TARGET_NOTRACK is not set CONFIG_NETFILTER_XT_TARGET_RATEEST=m CONFIG_NETFILTER_XT_TARGET_REDIRECT=m CONFIG_NETFILTER_XT_TARGET_TEE=m CONFIG_NETFILTER_XT_TARGET_TPROXY=m CONFIG_NETFILTER_XT_TARGET_TRACE=m CONFIG_NETFILTER_XT_TARGET_TCPMSS=m CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m # # Xtables matches # CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=m CONFIG_NETFILTER_XT_MATCH_BPF=m CONFIG_NETFILTER_XT_MATCH_CLUSTER=m CONFIG_NETFILTER_XT_MATCH_COMMENT=m CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m CONFIG_NETFILTER_XT_MATCH_CONNLABEL=m CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m CONFIG_NETFILTER_XT_MATCH_CONNMARK=m CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m CONFIG_NETFILTER_XT_MATCH_CPU=m CONFIG_NETFILTER_XT_MATCH_DCCP=m CONFIG_NETFILTER_XT_MATCH_DEVGROUP=m CONFIG_NETFILTER_XT_MATCH_DSCP=m CONFIG_NETFILTER_XT_MATCH_ECN=m CONFIG_NETFILTER_XT_MATCH_ESP=m CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m CONFIG_NETFILTER_XT_MATCH_HELPER=m CONFIG_NETFILTER_XT_MATCH_HL=m CONFIG_NETFILTER_XT_MATCH_IPCOMP=m CONFIG_NETFILTER_XT_MATCH_IPRANGE=m CONFIG_NETFILTER_XT_MATCH_L2TP=m CONFIG_NETFILTER_XT_MATCH_LENGTH=m CONFIG_NETFILTER_XT_MATCH_LIMIT=m CONFIG_NETFILTER_XT_MATCH_MAC=m CONFIG_NETFILTER_XT_MATCH_MARK=m CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m CONFIG_NETFILTER_XT_MATCH_NFACCT=m CONFIG_NETFILTER_XT_MATCH_OSF=m CONFIG_NETFILTER_XT_MATCH_OWNER=m CONFIG_NETFILTER_XT_MATCH_POLICY=m CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m CONFIG_NETFILTER_XT_MATCH_QUOTA=m CONFIG_NETFILTER_XT_MATCH_RATEEST=m CONFIG_NETFILTER_XT_MATCH_REALM=m CONFIG_NETFILTER_XT_MATCH_RECENT=m CONFIG_NETFILTER_XT_MATCH_SCTP=m CONFIG_NETFILTER_XT_MATCH_SOCKET=m CONFIG_NETFILTER_XT_MATCH_STATE=m CONFIG_NETFILTER_XT_MATCH_STATISTIC=m CONFIG_NETFILTER_XT_MATCH_STRING=m CONFIG_NETFILTER_XT_MATCH_TCPMSS=m CONFIG_NETFILTER_XT_MATCH_TIME=m CONFIG_NETFILTER_XT_MATCH_U32=m CONFIG_IP_SET=m CONFIG_IP_SET_MAX=256 CONFIG_IP_SET_BITMAP_IP=m CONFIG_IP_SET_BITMAP_IPMAC=m CONFIG_IP_SET_BITMAP_PORT=m CONFIG_IP_SET_HASH_IP=m CONFIG_IP_SET_HASH_IPMARK=m CONFIG_IP_SET_HASH_IPPORT=m CONFIG_IP_SET_HASH_IPPORTIP=m CONFIG_IP_SET_HASH_IPPORTNET=m CONFIG_IP_SET_HASH_MAC=m CONFIG_IP_SET_HASH_NETPORTNET=m CONFIG_IP_SET_HASH_NET=m CONFIG_IP_SET_HASH_NETNET=m CONFIG_IP_SET_HASH_NETPORT=m CONFIG_IP_SET_HASH_NETIFACE=m CONFIG_IP_SET_LIST_SET=m # CONFIG_IP_VS is not set # # IP: Netfilter Configuration # CONFIG_NF_DEFRAG_IPV4=m CONFIG_NF_CONNTRACK_IPV4=m CONFIG_NF_TABLES_IPV4=m CONFIG_NFT_CHAIN_ROUTE_IPV4=m CONFIG_NFT_REJECT_IPV4=m CONFIG_NFT_DUP_IPV4=m CONFIG_NF_TABLES_ARP=m CONFIG_NF_DUP_IPV4=m CONFIG_NF_LOG_ARP=m CONFIG_NF_LOG_IPV4=m CONFIG_NF_REJECT_IPV4=m CONFIG_NF_NAT_IPV4=m CONFIG_NFT_CHAIN_NAT_IPV4=m CONFIG_NF_NAT_MASQUERADE_IPV4=m CONFIG_NFT_MASQ_IPV4=m CONFIG_NFT_REDIR_IPV4=m CONFIG_NF_NAT_SNMP_BASIC=m CONFIG_NF_NAT_PROTO_GRE=m CONFIG_NF_NAT_PPTP=m CONFIG_NF_NAT_H323=m CONFIG_IP_NF_IPTABLES=m CONFIG_IP_NF_MATCH_AH=m CONFIG_IP_NF_MATCH_ECN=m CONFIG_IP_NF_MATCH_RPFILTER=m CONFIG_IP_NF_MATCH_TTL=m CONFIG_IP_NF_FILTER=m CONFIG_IP_NF_TARGET_REJECT=m CONFIG_IP_NF_TARGET_SYNPROXY=m CONFIG_IP_NF_NAT=m CONFIG_IP_NF_TARGET_MASQUERADE=m CONFIG_IP_NF_TARGET_NETMAP=m CONFIG_IP_NF_TARGET_REDIRECT=m CONFIG_IP_NF_MANGLE=m CONFIG_IP_NF_TARGET_CLUSTERIP=m CONFIG_IP_NF_TARGET_ECN=m CONFIG_IP_NF_TARGET_TTL=m CONFIG_IP_NF_RAW=m CONFIG_IP_NF_ARPTABLES=m CONFIG_IP_NF_ARPFILTER=m CONFIG_IP_NF_ARP_MANGLE=m # # IPv6: Netfilter Configuration # CONFIG_NF_DEFRAG_IPV6=m CONFIG_NF_CONNTRACK_IPV6=m CONFIG_NF_TABLES_IPV6=m CONFIG_NFT_CHAIN_ROUTE_IPV6=m CONFIG_NFT_REJECT_IPV6=m CONFIG_NFT_DUP_IPV6=m CONFIG_NF_DUP_IPV6=m CONFIG_NF_REJECT_IPV6=m CONFIG_NF_LOG_IPV6=m CONFIG_NF_NAT_IPV6=m CONFIG_NFT_CHAIN_NAT_IPV6=m CONFIG_NF_NAT_MASQUERADE_IPV6=m CONFIG_NFT_MASQ_IPV6=m CONFIG_NFT_REDIR_IPV6=m CONFIG_IP6_NF_IPTABLES=m CONFIG_IP6_NF_MATCH_AH=m CONFIG_IP6_NF_MATCH_EUI64=m CONFIG_IP6_NF_MATCH_FRAG=m CONFIG_IP6_NF_MATCH_OPTS=m CONFIG_IP6_NF_MATCH_HL=m CONFIG_IP6_NF_MATCH_IPV6HEADER=m CONFIG_IP6_NF_MATCH_MH=m CONFIG_IP6_NF_MATCH_RPFILTER=m CONFIG_IP6_NF_MATCH_RT=m CONFIG_IP6_NF_TARGET_HL=m CONFIG_IP6_NF_FILTER=m CONFIG_IP6_NF_TARGET_REJECT=m CONFIG_IP6_NF_TARGET_SYNPROXY=m CONFIG_IP6_NF_MANGLE=m CONFIG_IP6_NF_RAW=m CONFIG_IP6_NF_NAT=m CONFIG_IP6_NF_TARGET_MASQUERADE=m CONFIG_IP6_NF_TARGET_NPT=m CONFIG_NF_TABLES_BRIDGE=m CONFIG_NFT_BRIDGE_META=m CONFIG_NFT_BRIDGE_REJECT=m CONFIG_NF_LOG_BRIDGE=m CONFIG_BRIDGE_NF_EBTABLES=m CONFIG_BRIDGE_EBT_BROUTE=m CONFIG_BRIDGE_EBT_T_FILTER=m CONFIG_BRIDGE_EBT_T_NAT=m CONFIG_BRIDGE_EBT_802_3=m CONFIG_BRIDGE_EBT_AMONG=m CONFIG_BRIDGE_EBT_ARP=m CONFIG_BRIDGE_EBT_IP=m CONFIG_BRIDGE_EBT_IP6=m CONFIG_BRIDGE_EBT_LIMIT=m CONFIG_BRIDGE_EBT_MARK=m CONFIG_BRIDGE_EBT_PKTTYPE=m CONFIG_BRIDGE_EBT_STP=m CONFIG_BRIDGE_EBT_VLAN=m CONFIG_BRIDGE_EBT_ARPREPLY=m CONFIG_BRIDGE_EBT_DNAT=m CONFIG_BRIDGE_EBT_MARK_T=m CONFIG_BRIDGE_EBT_REDIRECT=m CONFIG_BRIDGE_EBT_SNAT=m CONFIG_BRIDGE_EBT_LOG=m CONFIG_BRIDGE_EBT_NFLOG=m # CONFIG_IP_DCCP is not set # CONFIG_IP_SCTP is not set # CONFIG_RDS is not set # CONFIG_TIPC is not set # CONFIG_ATM is not set # CONFIG_L2TP is not set CONFIG_STP=m CONFIG_BRIDGE=m CONFIG_BRIDGE_IGMP_SNOOPING=y CONFIG_HAVE_NET_DSA=y # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set CONFIG_LLC=m # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_PHONET is not set # CONFIG_6LOWPAN is not set # CONFIG_IEEE802154 is not set # CONFIG_NET_SCHED is not set # CONFIG_DCB is not set CONFIG_DNS_RESOLVER=y # CONFIG_BATMAN_ADV is not set # CONFIG_OPENVSWITCH is not set # CONFIG_VSOCKETS is not set CONFIG_NETLINK_MMAP=y CONFIG_NETLINK_DIAG=m # CONFIG_MPLS is not set # CONFIG_HSR is not set # CONFIG_NET_SWITCHDEV is not set # CONFIG_NET_L3_MASTER_DEV is not set CONFIG_RPS=y CONFIG_RFS_ACCEL=y CONFIG_XPS=y CONFIG_NET_RX_BUSY_POLL=y CONFIG_BQL=y # CONFIG_BPF_JIT is not set CONFIG_NET_FLOW_LIMIT=y # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_CAN is not set # CONFIG_IRDA is not set # CONFIG_BT is not set # CONFIG_AF_RXRPC is not set CONFIG_FIB_RULES=y # CONFIG_WIRELESS is not set # CONFIG_WIMAX is not set # CONFIG_RFKILL is not set # CONFIG_NET_9P is not set # CONFIG_CAIF is not set # CONFIG_CEPH_LIB is not set # CONFIG_NFC is not set # CONFIG_LWTUNNEL is not set CONFIG_HAVE_BPF_JIT=y # # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER=y CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug" CONFIG_DEVTMPFS=y # CONFIG_DEVTMPFS_MOUNT is not set CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="" # CONFIG_FW_LOADER_USER_HELPER_FALLBACK is not set CONFIG_ALLOW_DEV_COREDUMP=y CONFIG_SYS_HYPERVISOR=y # CONFIG_GENERIC_CPU_DEVICES is not set CONFIG_GENERIC_CPU_AUTOPROBE=y # CONFIG_DMA_SHARED_BUFFER is not set # # Bus devices # # CONFIG_CONNECTOR is not set # CONFIG_MTD is not set # CONFIG_OF is not set CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y # CONFIG_PARPORT is not set CONFIG_BLK_DEV=y # CONFIG_BLK_DEV_NULL_BLK is not set # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=m CONFIG_BLK_DEV_LOOP_MIN_COUNT=8 CONFIG_BLK_DEV_CRYPTOLOOP=m # CONFIG_BLK_DEV_DRBD is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_CDROM_PKTCDVD is not set # CONFIG_ATA_OVER_ETH is not set CONFIG_XEN_BLKDEV_FRONTEND=y # CONFIG_BLK_DEV_HD is not set # CONFIG_BLK_DEV_RBD is not set # # Misc devices # # CONFIG_SENSORS_LIS3LV02D is not set # CONFIG_DUMMY_IRQ is not set # CONFIG_ENCLOSURE_SERVICES is not set # CONFIG_SRAM is not set # CONFIG_C2PORT is not set # # EEPROM support # # CONFIG_EEPROM_93CX6 is not set # # Texas Instruments shared transport line discipline # # # Altera FPGA firmware download module # # # Intel MIC Bus Driver # # # SCIF Bus Driver # # # Intel MIC Host Driver # # # Intel MIC Card Driver # # # SCIF Driver # # # Intel MIC Coprocessor State Management (COSM) Drivers # # CONFIG_ECHO is not set # CONFIG_CXL_BASE is not set # CONFIG_CXL_KERNEL_API is not set # CONFIG_CXL_EEH is not set CONFIG_HAVE_IDE=y # CONFIG_IDE is not set # # SCSI device support # CONFIG_SCSI_MOD=y # CONFIG_RAID_ATTRS is not set # CONFIG_SCSI is not set # CONFIG_SCSI_DMA is not set # CONFIG_SCSI_NETLINK is not set # CONFIG_ATA is not set CONFIG_MD=y # CONFIG_BLK_DEV_MD is not set # CONFIG_BCACHE is not set CONFIG_BLK_DEV_DM_BUILTIN=y CONFIG_BLK_DEV_DM=m # CONFIG_DM_MQ_DEFAULT is not set # CONFIG_DM_DEBUG is not set CONFIG_DM_CRYPT=m # CONFIG_DM_SNAPSHOT is not set # CONFIG_DM_THIN_PROVISIONING is not set # CONFIG_DM_CACHE is not set # CONFIG_DM_ERA is not set # CONFIG_DM_MIRROR is not set # CONFIG_DM_RAID is not set # CONFIG_DM_ZERO is not set # CONFIG_DM_MULTIPATH is not set # CONFIG_DM_DELAY is not set # CONFIG_DM_UEVENT is not set # CONFIG_DM_FLAKEY is not set # CONFIG_DM_VERITY is not set # CONFIG_DM_SWITCH is not set # CONFIG_DM_LOG_WRITES is not set # CONFIG_MACINTOSH_DRIVERS is not set CONFIG_NETDEVICES=y CONFIG_NET_CORE=y # CONFIG_BONDING is not set # CONFIG_DUMMY is not set # CONFIG_EQUALIZER is not set # CONFIG_NET_TEAM is not set # CONFIG_MACVLAN is not set # CONFIG_IPVLAN is not set # CONFIG_VXLAN is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set CONFIG_TUN=m # CONFIG_TUN_VNET_CROSS_LE is not set # CONFIG_VETH is not set # CONFIG_NLMON is not set # # CAIF transport drivers # # # Distributed Switch Architecture drivers # # CONFIG_NET_DSA_MV88E6XXX is not set # CONFIG_NET_DSA_MV88E6XXX_NEED_PPU is not set # CONFIG_ETHERNET is not set # CONFIG_PHYLIB is not set CONFIG_PPP=m CONFIG_PPP_BSDCOMP=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_FILTER=y # CONFIG_PPP_MPPE is not set # CONFIG_PPP_MULTILINK is not set # CONFIG_PPPOE is not set CONFIG_PPP_ASYNC=m CONFIG_PPP_SYNC_TTY=m # CONFIG_SLIP is not set CONFIG_SLHC=m # # Host-side USB support is needed for USB Network Adapter support # # CONFIG_WLAN is not set # # Enable WiMAX (Networking options) to see the WiMAX drivers # # CONFIG_WAN is not set CONFIG_XEN_NETDEV_FRONTEND=y # CONFIG_ISDN is not set # CONFIG_NVM is not set # # Input device support # CONFIG_INPUT=y # CONFIG_INPUT_FF_MEMLESS is not set # CONFIG_INPUT_POLLDEV is not set # CONFIG_INPUT_SPARSEKMAP is not set # CONFIG_INPUT_MATRIXKMAP is not set # # Userland interfaces # # CONFIG_INPUT_MOUSEDEV is not set # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_EVDEV is not set # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # # CONFIG_INPUT_KEYBOARD is not set # CONFIG_INPUT_MOUSE is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TABLET is not set # CONFIG_INPUT_TOUCHSCREEN is not set CONFIG_INPUT_MISC=y # CONFIG_INPUT_AD714X is not set # CONFIG_INPUT_E3X0_BUTTON is not set # CONFIG_INPUT_PCSPKR is not set # CONFIG_INPUT_UINPUT is not set # CONFIG_INPUT_ADXL34X is not set # CONFIG_INPUT_CMA3000 is not set CONFIG_INPUT_XEN_KBDDEV_FRONTEND=y # CONFIG_INPUT_IDEAPAD_SLIDEBAR is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_ARCH_MIGHT_HAVE_PC_SERIO=y CONFIG_SERIO_I8042=y # CONFIG_SERIO_SERPORT is not set # CONFIG_SERIO_CT82C710 is not set CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # CONFIG_SERIO_ALTERA_PS2 is not set # CONFIG_SERIO_PS2MULT is not set # CONFIG_SERIO_ARC_PS2 is not set # CONFIG_USERIO is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_TTY=y CONFIG_VT=y CONFIG_CONSOLE_TRANSLATIONS=y CONFIG_VT_CONSOLE=y CONFIG_VT_CONSOLE_SLEEP=y CONFIG_HW_CONSOLE=y CONFIG_VT_HW_CONSOLE_BINDING=y CONFIG_UNIX98_PTYS=y # CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set # CONFIG_LEGACY_PTYS is not set # CONFIG_SERIAL_NONSTANDARD is not set # CONFIG_N_GSM is not set # CONFIG_TRACE_SINK is not set CONFIG_DEVMEM=y # CONFIG_DEVKMEM is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # # CONFIG_SERIAL_UARTLITE is not set # CONFIG_SERIAL_SCCNXP is not set # CONFIG_SERIAL_ALTERA_JTAGUART is not set # CONFIG_SERIAL_ALTERA_UART is not set # CONFIG_SERIAL_ARC is not set # CONFIG_SERIAL_FSL_LPUART is not set CONFIG_HVC_DRIVER=y CONFIG_HVC_IRQ=y CONFIG_HVC_XEN=y CONFIG_HVC_XEN_FRONTEND=y # CONFIG_IPMI_HANDLER is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set # CONFIG_R3964 is not set # CONFIG_MWAVE is not set # CONFIG_RAW_DRIVER is not set CONFIG_HANGCHECK_TIMER=m # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set # # I2C support # # CONFIG_I2C is not set # CONFIG_SPI is not set # CONFIG_SPMI is not set # CONFIG_HSI is not set # # PPS support # # CONFIG_PPS is not set # # PPS generators support # # # PTP clock support # # CONFIG_PTP_1588_CLOCK is not set # # Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks. # CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y # CONFIG_GPIOLIB is not set # CONFIG_W1 is not set # CONFIG_POWER_SUPPLY is not set # CONFIG_POWER_AVS is not set # CONFIG_HWMON is not set # CONFIG_THERMAL is not set # CONFIG_WATCHDOG is not set CONFIG_SSB_POSSIBLE=y # # Sonics Silicon Backplane # # CONFIG_SSB is not set CONFIG_BCMA_POSSIBLE=y # # Broadcom specific AMBA # # CONFIG_BCMA is not set # # Multifunction device drivers # # CONFIG_MFD_CORE is not set # CONFIG_MFD_CROS_EC is not set # CONFIG_HTC_PASIC3 is not set # CONFIG_MFD_KEMPLD is not set # CONFIG_MFD_MT6397 is not set # CONFIG_MFD_SM501 is not set # CONFIG_ABX500_CORE is not set # CONFIG_MFD_SYSCON is not set # CONFIG_MFD_TI_AM335X_TSCADC is not set # CONFIG_MFD_TMIO is not set # CONFIG_REGULATOR is not set # CONFIG_MEDIA_SUPPORT is not set # # Graphics support # # CONFIG_DRM is not set # # Frame buffer Devices # CONFIG_FB=y # CONFIG_FIRMWARE_EDID is not set CONFIG_FB_CMDLINE=y # CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set # CONFIG_FB_CFB_FILLRECT is not set # CONFIG_FB_CFB_COPYAREA is not set # CONFIG_FB_CFB_IMAGEBLIT is not set # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set CONFIG_FB_SYS_FILLRECT=y CONFIG_FB_SYS_COPYAREA=y CONFIG_FB_SYS_IMAGEBLIT=y # CONFIG_FB_FOREIGN_ENDIAN is not set CONFIG_FB_SYS_FOPS=y CONFIG_FB_DEFERRED_IO=y # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # # Frame buffer hardware drivers # # CONFIG_FB_ARC is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_VESA is not set # CONFIG_FB_N411 is not set # CONFIG_FB_HGA is not set # CONFIG_FB_OPENCORES is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_IBM_GXT4500 is not set # CONFIG_FB_VIRTUAL is not set CONFIG_XEN_FBDEV_FRONTEND=y # CONFIG_FB_METRONOME is not set # CONFIG_FB_BROADSHEET is not set # CONFIG_FB_AUO_K190X is not set # CONFIG_FB_SIMPLE is not set # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # CONFIG_VGASTATE is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_VGACON_SOFT_SCROLLBACK is not set CONFIG_DUMMY_CONSOLE=y CONFIG_DUMMY_CONSOLE_COLUMNS=80 CONFIG_DUMMY_CONSOLE_ROWS=25 CONFIG_FRAMEBUFFER_CONSOLE=y # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set # CONFIG_LOGO is not set # CONFIG_SOUND is not set # # HID support # # CONFIG_HID is not set CONFIG_USB_OHCI_LITTLE_ENDIAN=y # CONFIG_USB_SUPPORT is not set # CONFIG_UWB is not set # CONFIG_MMC is not set # CONFIG_MEMSTICK is not set # CONFIG_NEW_LEDS is not set # CONFIG_ACCESSIBILITY is not set CONFIG_EDAC_ATOMIC_SCRUB=y CONFIG_EDAC_SUPPORT=y # CONFIG_EDAC is not set CONFIG_RTC_LIB=y # CONFIG_RTC_CLASS is not set # CONFIG_DMADEVICES is not set # CONFIG_AUXDISPLAY is not set # CONFIG_UIO is not set # CONFIG_VIRT_DRIVERS is not set # # Virtio drivers # # CONFIG_VIRTIO_MMIO is not set # # Microsoft Hyper-V guest support # # # Xen driver support # # CONFIG_XEN_BALLOON is not set # CONFIG_XEN_DEV_EVTCHN is not set CONFIG_XENFS=y CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=y # CONFIG_XEN_GNTDEV is not set # CONFIG_XEN_GRANT_DEV_ALLOC is not set CONFIG_SWIOTLB_XEN=y CONFIG_XEN_PRIVCMD=y CONFIG_XEN_HAVE_PVMMU=y CONFIG_XEN_HAVE_VPMU=y # CONFIG_STAGING is not set # CONFIG_X86_PLATFORM_DEVICES is not set # CONFIG_CHROME_PLATFORMS is not set # # Hardware Spinlock drivers # # # Clock Source drivers # CONFIG_CLKEVT_I8253=y CONFIG_I8253_LOCK=y CONFIG_CLKBLD_I8253=y # CONFIG_ATMEL_PIT is not set # CONFIG_SH_TIMER_CMT is not set # CONFIG_SH_TIMER_MTU2 is not set # CONFIG_SH_TIMER_TMU is not set # CONFIG_EM_TIMER_STI is not set # CONFIG_MAILBOX is not set # CONFIG_IOMMU_SUPPORT is not set # # Remoteproc drivers # # CONFIG_STE_MODEM_RPROC is not set # # Rpmsg drivers # # # SOC (System On Chip) specific Drivers # # CONFIG_SUNXI_SRAM is not set # CONFIG_SOC_TI is not set # CONFIG_PM_DEVFREQ is not set # CONFIG_EXTCON is not set # CONFIG_MEMORY is not set # CONFIG_IIO is not set # CONFIG_PWM is not set # CONFIG_IPACK_BUS is not set # CONFIG_RESET_CONTROLLER is not set # CONFIG_FMC is not set # # PHY Subsystem # # CONFIG_GENERIC_PHY is not set # CONFIG_PHY_PXA_28NM_HSIC is not set # CONFIG_PHY_PXA_28NM_USB2 is not set # CONFIG_BCM_KONA_USB2_PHY is not set # CONFIG_POWERCAP is not set # CONFIG_MCB is not set # # Performance monitor support # # CONFIG_RAS is not set # # Android # # CONFIG_ANDROID is not set # CONFIG_LIBNVDIMM is not set # CONFIG_NVMEM is not set # CONFIG_STM is not set # CONFIG_STM_DUMMY is not set # CONFIG_STM_SOURCE_CONSOLE is not set # CONFIG_INTEL_TH is not set # # FPGA Configuration Support # # CONFIG_FPGA is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_FIRMWARE_MEMMAP=y # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set # CONFIG_DMIID is not set # CONFIG_DMI_SYSFS is not set CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y # CONFIG_GOOGLE_FIRMWARE is not set # # File systems # CONFIG_DCACHE_WORD_ACCESS=y # CONFIG_EXT2_FS is not set # CONFIG_EXT3_FS is not set CONFIG_EXT4_FS=y CONFIG_EXT4_USE_FOR_EXT2=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y # CONFIG_EXT4_ENCRYPTION is not set # CONFIG_EXT4_DEBUG is not set CONFIG_JBD2=y # CONFIG_JBD2_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set # CONFIG_XFS_FS is not set # CONFIG_GFS2_FS is not set # CONFIG_BTRFS_FS is not set # CONFIG_NILFS2_FS is not set # CONFIG_F2FS_FS is not set # CONFIG_FS_DAX is not set CONFIG_FS_POSIX_ACL=y CONFIG_EXPORTFS=y CONFIG_FILE_LOCKING=y CONFIG_FSNOTIFY=y # CONFIG_DNOTIFY is not set CONFIG_INOTIFY_USER=y CONFIG_FANOTIFY=y # CONFIG_QUOTA is not set # CONFIG_QUOTACTL is not set CONFIG_AUTOFS4_FS=m CONFIG_FUSE_FS=m CONFIG_CUSE=m # CONFIG_OVERLAY_FS is not set # # Caches # CONFIG_FSCACHE=m # CONFIG_FSCACHE_STATS is not set # CONFIG_FSCACHE_HISTOGRAM is not set # CONFIG_FSCACHE_DEBUG is not set # CONFIG_FSCACHE_OBJECT_LIST is not set # CONFIG_CACHEFILES is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=m CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_UDF_FS=m CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=m # CONFIG_MSDOS_FS is not set CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_CHILDREN=y CONFIG_KERNFS=y CONFIG_SYSFS=y CONFIG_TMPFS=y CONFIG_TMPFS_POSIX_ACL=y CONFIG_TMPFS_XATTR=y # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set # CONFIG_CONFIGFS_FS is not set # CONFIG_MISC_FILESYSTEMS is not set CONFIG_NETWORK_FILESYSTEMS=y CONFIG_NFS_FS=m CONFIG_NFS_V2=m CONFIG_NFS_V3=m CONFIG_NFS_V3_ACL=y # CONFIG_NFS_V4 is not set # CONFIG_NFS_SWAP is not set # CONFIG_NFS_FSCACHE is not set CONFIG_NFSD=m CONFIG_NFSD_V2_ACL=y CONFIG_NFSD_V3=y CONFIG_NFSD_V3_ACL=y # CONFIG_NFSD_V4 is not set CONFIG_GRACE_PERIOD=m CONFIG_LOCKD=m CONFIG_LOCKD_V4=y CONFIG_NFS_ACL_SUPPORT=m CONFIG_NFS_COMMON=y CONFIG_SUNRPC=m # CONFIG_RPCSEC_GSS_KRB5 is not set # CONFIG_SUNRPC_DEBUG is not set # CONFIG_CEPH_FS is not set CONFIG_CIFS=m # CONFIG_CIFS_STATS is not set # CONFIG_CIFS_WEAK_PW_HASH is not set CONFIG_CIFS_UPCALL=y CONFIG_CIFS_XATTR=y CONFIG_CIFS_POSIX=y CONFIG_CIFS_ACL=y # CONFIG_CIFS_DEBUG is not set CONFIG_CIFS_DFS_UPCALL=y CONFIG_CIFS_SMB2=y # CONFIG_CIFS_SMB311 is not set # CONFIG_CIFS_FSCACHE is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=m CONFIG_NLS_CODEPAGE_737=m CONFIG_NLS_CODEPAGE_775=m CONFIG_NLS_CODEPAGE_850=m CONFIG_NLS_CODEPAGE_852=m CONFIG_NLS_CODEPAGE_855=m CONFIG_NLS_CODEPAGE_857=m CONFIG_NLS_CODEPAGE_860=m CONFIG_NLS_CODEPAGE_861=m CONFIG_NLS_CODEPAGE_862=m CONFIG_NLS_CODEPAGE_863=m CONFIG_NLS_CODEPAGE_864=m CONFIG_NLS_CODEPAGE_865=m CONFIG_NLS_CODEPAGE_866=m CONFIG_NLS_CODEPAGE_869=m CONFIG_NLS_CODEPAGE_936=m CONFIG_NLS_CODEPAGE_950=m CONFIG_NLS_CODEPAGE_932=m CONFIG_NLS_CODEPAGE_949=m CONFIG_NLS_CODEPAGE_874=m CONFIG_NLS_ISO8859_8=m CONFIG_NLS_CODEPAGE_1250=m CONFIG_NLS_CODEPAGE_1251=m CONFIG_NLS_ASCII=m CONFIG_NLS_ISO8859_1=m CONFIG_NLS_ISO8859_2=m CONFIG_NLS_ISO8859_3=m CONFIG_NLS_ISO8859_4=m CONFIG_NLS_ISO8859_5=m CONFIG_NLS_ISO8859_6=m CONFIG_NLS_ISO8859_7=m CONFIG_NLS_ISO8859_9=m CONFIG_NLS_ISO8859_13=m CONFIG_NLS_ISO8859_14=m CONFIG_NLS_ISO8859_15=m CONFIG_NLS_KOI8_R=m CONFIG_NLS_KOI8_U=m CONFIG_NLS_MAC_ROMAN=m CONFIG_NLS_MAC_CELTIC=m CONFIG_NLS_MAC_CENTEURO=m CONFIG_NLS_MAC_CROATIAN=m CONFIG_NLS_MAC_CYRILLIC=m CONFIG_NLS_MAC_GAELIC=m CONFIG_NLS_MAC_GREEK=m CONFIG_NLS_MAC_ICELAND=m CONFIG_NLS_MAC_INUIT=m CONFIG_NLS_MAC_ROMANIAN=m CONFIG_NLS_MAC_TURKISH=m CONFIG_NLS_UTF8=m # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # # printk and dmesg options # CONFIG_PRINTK_TIME=y CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4 # # Compile-time checks and compiler options # CONFIG_ENABLE_WARN_DEPRECATED=y # CONFIG_ENABLE_MUST_CHECK is not set CONFIG_FRAME_WARN=2048 # CONFIG_STRIP_ASM_SYMS is not set # CONFIG_UNUSED_SYMBOLS is not set # CONFIG_DEBUG_FS is not set # CONFIG_HEADERS_CHECK is not set # CONFIG_DEBUG_SECTION_MISMATCH is not set # CONFIG_SECTION_MISMATCH_WARN_ONLY is not set CONFIG_ARCH_WANT_FRAME_POINTERS=y CONFIG_FRAME_POINTER=y # CONFIG_MAGIC_SYSRQ is not set # CONFIG_DEBUG_KERNEL is not set # # Memory Debugging # # CONFIG_PAGE_EXTENSION is not set CONFIG_HAVE_DEBUG_KMEMLEAK=y CONFIG_DEBUG_MEMORY_INIT=y CONFIG_HAVE_DEBUG_STACKOVERFLOW=y CONFIG_HAVE_ARCH_KMEMCHECK=y CONFIG_HAVE_ARCH_KASAN=y # # Debug Lockups and Hangs # # CONFIG_PANIC_ON_OOPS is not set CONFIG_PANIC_ON_OOPS_VALUE=0 CONFIG_PANIC_TIMEOUT=10 CONFIG_SCHED_INFO=y # CONFIG_DEBUG_TIMEKEEPING is not set # # Lock Debugging (spinlocks, mutexes, etc...) # # CONFIG_STACKTRACE is not set CONFIG_DEBUG_BUGVERBOSE=y # # RCU Debugging # # CONFIG_PROVE_RCU is not set # CONFIG_SPARSE_RCU_POINTER is not set # CONFIG_TORTURE_TEST is not set CONFIG_RCU_CPU_STALL_TIMEOUT=60 CONFIG_ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS=y CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_SYSCALL_TRACEPOINTS=y CONFIG_HAVE_FENTRY=y CONFIG_HAVE_C_RECORDMCOUNT=y CONFIG_TRACING_SUPPORT=y # CONFIG_FTRACE is not set # # Runtime Testing # # CONFIG_ATOMIC64_SELFTEST is not set # CONFIG_TEST_HEXDUMP is not set # CONFIG_TEST_STRING_HELPERS is not set # CONFIG_TEST_KSTRTOX is not set # CONFIG_TEST_PRINTF is not set # CONFIG_TEST_RHASHTABLE is not set # CONFIG_DMA_API_DEBUG is not set # CONFIG_TEST_LKM is not set # CONFIG_TEST_USER_COPY is not set # CONFIG_TEST_BPF is not set # CONFIG_TEST_FIRMWARE is not set # CONFIG_TEST_UDELAY is not set # CONFIG_MEMTEST is not set # CONFIG_TEST_STATIC_KEYS is not set # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y # CONFIG_STRICT_DEVMEM is not set CONFIG_X86_VERBOSE_BOOTUP=y CONFIG_EARLY_PRINTK=y # CONFIG_X86_PTDUMP_CORE is not set # CONFIG_DEBUG_SET_MODULE_RONX is not set CONFIG_DOUBLEFAULT=y # CONFIG_IOMMU_STRESS is not set CONFIG_HAVE_MMIOTRACE_SUPPORT=y CONFIG_IO_DELAY_TYPE_0X80=0 CONFIG_IO_DELAY_TYPE_0XED=1 CONFIG_IO_DELAY_TYPE_UDELAY=2 CONFIG_IO_DELAY_TYPE_NONE=3 CONFIG_IO_DELAY_0X80=y # CONFIG_IO_DELAY_0XED is not set # CONFIG_IO_DELAY_UDELAY is not set # CONFIG_IO_DELAY_NONE is not set CONFIG_DEFAULT_IO_DELAY_TYPE=0 # CONFIG_OPTIMIZE_INLINING is not set # CONFIG_PUNIT_ATOM_DEBUG is not set # # Security options # CONFIG_KEYS=y # CONFIG_PERSISTENT_KEYRINGS is not set # CONFIG_BIG_KEYS is not set CONFIG_ENCRYPTED_KEYS=m # CONFIG_SECURITY_DMESG_RESTRICT is not set # CONFIG_SECURITY is not set # CONFIG_SECURITYFS is not set CONFIG_DEFAULT_SECURITY_DAC=y CONFIG_DEFAULT_SECURITY="" CONFIG_CRYPTO=y # # Crypto core or helper # CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=m CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=m CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG=m CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_RNG_DEFAULT=m CONFIG_CRYPTO_PCOMP=m CONFIG_CRYPTO_PCOMP2=y CONFIG_CRYPTO_AKCIPHER2=y CONFIG_CRYPTO_AKCIPHER=m CONFIG_CRYPTO_RSA=m CONFIG_CRYPTO_MANAGER=m CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_USER=m CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y CONFIG_CRYPTO_GF128MUL=m CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_NULL2=y CONFIG_CRYPTO_PCRYPT=m CONFIG_CRYPTO_WORKQUEUE=y CONFIG_CRYPTO_CRYPTD=m CONFIG_CRYPTO_MCRYPTD=m CONFIG_CRYPTO_AUTHENC=m # CONFIG_CRYPTO_TEST is not set CONFIG_CRYPTO_ABLK_HELPER=m CONFIG_CRYPTO_GLUE_HELPER_X86=m # # Authenticated Encryption with Associated Data # CONFIG_CRYPTO_CCM=m CONFIG_CRYPTO_GCM=m CONFIG_CRYPTO_CHACHA20POLY1305=m CONFIG_CRYPTO_SEQIV=m CONFIG_CRYPTO_ECHAINIV=m # # Block modes # CONFIG_CRYPTO_CBC=m CONFIG_CRYPTO_CTR=m CONFIG_CRYPTO_CTS=m CONFIG_CRYPTO_ECB=m CONFIG_CRYPTO_LRW=m CONFIG_CRYPTO_PCBC=m CONFIG_CRYPTO_XTS=m CONFIG_CRYPTO_KEYWRAP=m # # Hash modes # CONFIG_CRYPTO_CMAC=m CONFIG_CRYPTO_HMAC=m CONFIG_CRYPTO_XCBC=m CONFIG_CRYPTO_VMAC=m # # Digest # CONFIG_CRYPTO_CRC32C=y CONFIG_CRYPTO_CRC32C_INTEL=m CONFIG_CRYPTO_CRC32=m CONFIG_CRYPTO_CRC32_PCLMUL=m CONFIG_CRYPTO_CRCT10DIF=y CONFIG_CRYPTO_CRCT10DIF_PCLMUL=m CONFIG_CRYPTO_GHASH=m CONFIG_CRYPTO_POLY1305=m CONFIG_CRYPTO_POLY1305_X86_64=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=m CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_RMD128=m CONFIG_CRYPTO_RMD160=m CONFIG_CRYPTO_RMD256=m CONFIG_CRYPTO_RMD320=m CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA1_SSSE3=m CONFIG_CRYPTO_SHA256_SSSE3=m CONFIG_CRYPTO_SHA512_SSSE3=m # CONFIG_CRYPTO_SHA1_MB is not set CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL=m # # Ciphers # CONFIG_CRYPTO_AES=y CONFIG_CRYPTO_AES_X86_64=m CONFIG_CRYPTO_AES_NI_INTEL=m CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_BLOWFISH_COMMON=m CONFIG_CRYPTO_BLOWFISH_X86_64=m CONFIG_CRYPTO_CAMELLIA=m CONFIG_CRYPTO_CAMELLIA_X86_64=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64=m CONFIG_CRYPTO_CAST_COMMON=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST5_AVX_X86_64=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_CAST6_AVX_X86_64=m CONFIG_CRYPTO_DES=m CONFIG_CRYPTO_DES3_EDE_X86_64=m CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_KHAZAD=m CONFIG_CRYPTO_SALSA20=m CONFIG_CRYPTO_SALSA20_X86_64=m CONFIG_CRYPTO_CHACHA20=m CONFIG_CRYPTO_CHACHA20_X86_64=m CONFIG_CRYPTO_SEED=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_SERPENT_SSE2_X86_64=m CONFIG_CRYPTO_SERPENT_AVX_X86_64=m CONFIG_CRYPTO_SERPENT_AVX2_X86_64=m CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_TWOFISH_COMMON=m CONFIG_CRYPTO_TWOFISH_X86_64=m CONFIG_CRYPTO_TWOFISH_X86_64_3WAY=m CONFIG_CRYPTO_TWOFISH_AVX_X86_64=m # # Compression # CONFIG_CRYPTO_DEFLATE=m CONFIG_CRYPTO_ZLIB=m CONFIG_CRYPTO_LZO=m CONFIG_CRYPTO_842=m CONFIG_CRYPTO_LZ4=m CONFIG_CRYPTO_LZ4HC=m # # Random Number Generation # CONFIG_CRYPTO_ANSI_CPRNG=m CONFIG_CRYPTO_DRBG_MENU=m CONFIG_CRYPTO_DRBG_HMAC=y CONFIG_CRYPTO_DRBG_HASH=y CONFIG_CRYPTO_DRBG_CTR=y CONFIG_CRYPTO_DRBG=m CONFIG_CRYPTO_JITTERENTROPY=m CONFIG_CRYPTO_USER_API=m CONFIG_CRYPTO_USER_API_HASH=m CONFIG_CRYPTO_USER_API_SKCIPHER=m CONFIG_CRYPTO_USER_API_RNG=m CONFIG_CRYPTO_USER_API_AEAD=m CONFIG_CRYPTO_HASH_INFO=y # CONFIG_CRYPTO_HW is not set CONFIG_ASYMMETRIC_KEY_TYPE=m CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=m CONFIG_PUBLIC_KEY_ALGO_RSA=m CONFIG_X509_CERTIFICATE_PARSER=m CONFIG_PKCS7_MESSAGE_PARSER=m CONFIG_PKCS7_TEST_KEY=m # # Certificates for signature checking # CONFIG_SYSTEM_TRUSTED_KEYRING=y CONFIG_SYSTEM_TRUSTED_KEYS="" CONFIG_HAVE_KVM=y # CONFIG_VIRTUALIZATION is not set # CONFIG_BINARY_PRINTF is not set # # Library routines # CONFIG_BITREVERSE=y # CONFIG_HAVE_ARCH_BITREVERSE is not set CONFIG_GENERIC_STRNCPY_FROM_USER=y CONFIG_GENERIC_STRNLEN_USER=y CONFIG_GENERIC_NET_UTILS=y CONFIG_GENERIC_FIND_FIRST_BIT=y CONFIG_GENERIC_PCI_IOMAP=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_IO=y CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y CONFIG_ARCH_HAS_FAST_MULTIPLIER=y CONFIG_CRC_CCITT=m CONFIG_CRC16=y CONFIG_CRC_T10DIF=y CONFIG_CRC_ITU_T=m CONFIG_CRC32=y # CONFIG_CRC32_SELFTEST is not set CONFIG_CRC32_SLICEBY8=y # CONFIG_CRC32_SLICEBY4 is not set # CONFIG_CRC32_SARWATE is not set # CONFIG_CRC32_BIT is not set CONFIG_CRC7=m CONFIG_LIBCRC32C=m CONFIG_CRC8=m # CONFIG_AUDIT_ARCH_COMPAT_GENERIC is not set # CONFIG_RANDOM32_SELFTEST is not set CONFIG_842_COMPRESS=m CONFIG_842_DECOMPRESS=m CONFIG_ZLIB_INFLATE=m CONFIG_ZLIB_DEFLATE=m CONFIG_LZO_COMPRESS=m CONFIG_LZO_DECOMPRESS=m CONFIG_LZ4_COMPRESS=m CONFIG_LZ4HC_COMPRESS=m CONFIG_LZ4_DECOMPRESS=m CONFIG_XZ_DEC=m CONFIG_XZ_DEC_X86=y CONFIG_XZ_DEC_POWERPC=y CONFIG_XZ_DEC_IA64=y CONFIG_XZ_DEC_ARM=y CONFIG_XZ_DEC_ARMTHUMB=y CONFIG_XZ_DEC_SPARC=y CONFIG_XZ_DEC_BCJ=y # CONFIG_XZ_DEC_TEST is not set CONFIG_TEXTSEARCH=y CONFIG_TEXTSEARCH_KMP=m CONFIG_TEXTSEARCH_BM=m CONFIG_TEXTSEARCH_FSM=m CONFIG_ASSOCIATIVE_ARRAY=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT_MAP=y CONFIG_HAS_DMA=y CONFIG_CPU_RMAP=y CONFIG_DQL=y CONFIG_NLATTR=y CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y CONFIG_CLZ_TAB=y CONFIG_CORDIC=m # CONFIG_DDR is not set CONFIG_MPILIB=m CONFIG_OID_REGISTRY=m CONFIG_FONT_SUPPORT=y # CONFIG_FONTS is not set CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_SG_SPLIT is not set CONFIG_ARCH_HAS_SG_CHAIN=y CONFIG_ARCH_HAS_PMEM_API=y CONFIG_ARCH_HAS_MMIO_FLUSH=y [-- Attachment #3: Type: text/plain, Size: 127 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure 2016-09-27 11:13 ` Sven Köhler @ 2016-09-27 12:02 ` Juergen Gross 2016-09-27 12:09 ` Sven Köhler 0 siblings, 1 reply; 16+ messages in thread From: Juergen Gross @ 2016-09-27 12:02 UTC (permalink / raw) To: Sven Köhler, xen-devel On 27/09/16 13:13, Sven Köhler wrote: > Am 27.09.2016 um 07:31 schrieb Juergen Gross: >> On 27/09/16 00:48, Sven Köhler wrote: >>> Am 26.09.2016 um 07:43 schrieb Juergen Gross: >>>> On 25/09/16 18:04, Sven Köhler wrote: >>>>> Hi, >>>>> >>>>> I'm experiencing the bug below which was discussed on xen-devel December >>>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>>>> >>>>> The bug only seems to occur with the last domU booted on my machine. >>>>> Where do I find a patch that fixes that? >>>> >>>> The issue back in December was fixed by commit >>>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >>>> Either gentoo didn't update to the official Xen 4.7 release (including >>>> pvgrub) or you are seeing a new issue. >>> >>> From the looks of it, the Gentoo package is using the grub from the >>> xen-4.7.0 tarball. >>> >>> I downgraded to pvgrub 4.6.3 and the problem went away. >>> >>> So I assume I'm seeing a new issue. How do I debug it? >> >> Interesting. Just tested it on upstream Xen and saw the same problem >> with a rather old guest kernel (3.0 based, xen flavor), while a newer >> kernel (4.1, pvops) is working. >> >> Can you give me some more details about the kernel you are trying to >> boot? > > It's an unmodified 4.4.21 kernel which I compile by hand. The config is > attached. Does that help? Not really. OTOH I think I don't need more help, as I've found a problem in pvgrub. I have a patch which seems to correct the issue. Are you fine with me adding you as the original reporter of the problem in the patch? Juergen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure 2016-09-27 12:02 ` Juergen Gross @ 2016-09-27 12:09 ` Sven Köhler 2016-09-27 12:52 ` Juergen Gross 0 siblings, 1 reply; 16+ messages in thread From: Sven Köhler @ 2016-09-27 12:09 UTC (permalink / raw) To: Juergen Gross, xen-devel Am 27.09.2016 um 14:02 schrieb Juergen Gross: > On 27/09/16 13:13, Sven Köhler wrote: >> Am 27.09.2016 um 07:31 schrieb Juergen Gross: >>> On 27/09/16 00:48, Sven Köhler wrote: >>>> Am 26.09.2016 um 07:43 schrieb Juergen Gross: >>>>> On 25/09/16 18:04, Sven Köhler wrote: >>>>>> Hi, >>>>>> >>>>>> I'm experiencing the bug below which was discussed on xen-devel December >>>>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>>>>> >>>>>> The bug only seems to occur with the last domU booted on my machine. >>>>>> Where do I find a patch that fixes that? >>>>> >>>>> The issue back in December was fixed by commit >>>>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >>>>> Either gentoo didn't update to the official Xen 4.7 release (including >>>>> pvgrub) or you are seeing a new issue. >>>> >>>> From the looks of it, the Gentoo package is using the grub from the >>>> xen-4.7.0 tarball. >>>> >>>> I downgraded to pvgrub 4.6.3 and the problem went away. >>>> >>>> So I assume I'm seeing a new issue. How do I debug it? >>> >>> Interesting. Just tested it on upstream Xen and saw the same problem >>> with a rather old guest kernel (3.0 based, xen flavor), while a newer >>> kernel (4.1, pvops) is working. >>> >>> Can you give me some more details about the kernel you are trying to >>> boot? >> >> It's an unmodified 4.4.21 kernel which I compile by hand. The config is >> attached. Does that help? > > Not really. OTOH I think I don't need more help, as I've found a problem > in pvgrub. I have a patch which seems to correct the issue. Are you fine > with me adding you as the original reporter of the problem in the patch? Yes, I'm fine with adding me as the reporter. Do you want me to test the patch first? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure 2016-09-27 12:09 ` Sven Köhler @ 2016-09-27 12:52 ` Juergen Gross 2016-09-27 23:33 ` Sven Köhler 0 siblings, 1 reply; 16+ messages in thread From: Juergen Gross @ 2016-09-27 12:52 UTC (permalink / raw) To: Sven Köhler, xen-devel [-- Attachment #1: Type: text/plain, Size: 1954 bytes --] On 27/09/16 14:09, Sven Köhler wrote: > Am 27.09.2016 um 14:02 schrieb Juergen Gross: >> On 27/09/16 13:13, Sven Köhler wrote: >>> Am 27.09.2016 um 07:31 schrieb Juergen Gross: >>>> On 27/09/16 00:48, Sven Köhler wrote: >>>>> Am 26.09.2016 um 07:43 schrieb Juergen Gross: >>>>>> On 25/09/16 18:04, Sven Köhler wrote: >>>>>>> Hi, >>>>>>> >>>>>>> I'm experiencing the bug below which was discussed on xen-devel December >>>>>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>>>>>> >>>>>>> The bug only seems to occur with the last domU booted on my machine. >>>>>>> Where do I find a patch that fixes that? >>>>>> >>>>>> The issue back in December was fixed by commit >>>>>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >>>>>> Either gentoo didn't update to the official Xen 4.7 release (including >>>>>> pvgrub) or you are seeing a new issue. >>>>> >>>>> From the looks of it, the Gentoo package is using the grub from the >>>>> xen-4.7.0 tarball. >>>>> >>>>> I downgraded to pvgrub 4.6.3 and the problem went away. >>>>> >>>>> So I assume I'm seeing a new issue. How do I debug it? >>>> >>>> Interesting. Just tested it on upstream Xen and saw the same problem >>>> with a rather old guest kernel (3.0 based, xen flavor), while a newer >>>> kernel (4.1, pvops) is working. >>>> >>>> Can you give me some more details about the kernel you are trying to >>>> boot? >>> >>> It's an unmodified 4.4.21 kernel which I compile by hand. The config is >>> attached. Does that help? >> >> Not really. OTOH I think I don't need more help, as I've found a problem >> in pvgrub. I have a patch which seems to correct the issue. Are you fine >> with me adding you as the original reporter of the problem in the patch? > > Yes, I'm fine with adding me as the reporter. > Do you want me to test the patch first? Sure. The attached patch is for Xen upstream, but I think it should apply to Xen 4.7, too. Juergen [-- Attachment #2: 0001-pvgrub-fix-crash-when-booting-kernel-with-p2m-list-o.patch --] [-- Type: text/x-patch, Size: 1383 bytes --] >From 62a69c20e2184a630efdaff87ddbb768d75c73be Mon Sep 17 00:00:00 2001 From: Juergen Gross <jgross@suse.com> Date: Tue, 27 Sep 2016 14:03:09 +0200 Subject: [PATCH] pvgrub: fix crash when booting kernel with p2m list outside kernel mapping When trying to boot a kernel with the p2m list not mapped by the initial kernel mapping it can happen that pvgrub is failing as it is keeping some page tables mapped. Unmap the additional page tables created for the special p2m mapping will avoid this failure. Reported-by: Sven Koehler <sven.koehler@gmail.com> Signed-off-by: Juergen Gross <jgross@suse.com> --- This is a backport candidate for 4.7 --- stubdom/grub/kexec.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/stubdom/grub/kexec.c b/stubdom/grub/kexec.c index 2ed4f6c..437a0a9 100644 --- a/stubdom/grub/kexec.c +++ b/stubdom/grub/kexec.c @@ -347,6 +347,8 @@ void kexec(void *kernel, long kernel_size, void *module, long module_size, char /* Unmap libxc's projection of the boot page table */ seg = xc_dom_seg_to_ptr(dom, &dom->pgtables_seg); munmap(seg, dom->pgtables_seg.vend - dom->pgtables_seg.vstart); + seg = xc_dom_seg_to_ptr(dom, &dom->p2m_seg); + munmap(seg, dom->p2m_seg.vend - dom->p2m_seg.vstart); /* Unmap day0 pages to avoid having a r/w mapping of the future page table */ for (pfn = 0; pfn < allocated; pfn++) -- 2.6.6 [-- Attachment #3: Type: text/plain, Size: 127 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply related [flat|nested] 16+ messages in thread
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure 2016-09-27 12:52 ` Juergen Gross @ 2016-09-27 23:33 ` Sven Köhler 2016-09-28 3:50 ` Juergen Gross 0 siblings, 1 reply; 16+ messages in thread From: Sven Köhler @ 2016-09-27 23:33 UTC (permalink / raw) To: Juergen Gross, xen-devel Am 27.09.2016 um 14:52 schrieb Juergen Gross: > On 27/09/16 14:09, Sven Köhler wrote: >> Am 27.09.2016 um 14:02 schrieb Juergen Gross: >>> On 27/09/16 13:13, Sven Köhler wrote: >>>> Am 27.09.2016 um 07:31 schrieb Juergen Gross: >>>>> On 27/09/16 00:48, Sven Köhler wrote: >>>>>> Am 26.09.2016 um 07:43 schrieb Juergen Gross: >>>>>>> On 25/09/16 18:04, Sven Köhler wrote: >>>>>>>> Hi, >>>>>>>> >>>>>>>> I'm experiencing the bug below which was discussed on xen-devel December >>>>>>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>>>>>>> >>>>>>>> The bug only seems to occur with the last domU booted on my machine. >>>>>>>> Where do I find a patch that fixes that? >>>>>>> >>>>>>> The issue back in December was fixed by commit >>>>>>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >>>>>>> Either gentoo didn't update to the official Xen 4.7 release (including >>>>>>> pvgrub) or you are seeing a new issue. >>>>>> >>>>>> From the looks of it, the Gentoo package is using the grub from the >>>>>> xen-4.7.0 tarball. >>>>>> >>>>>> I downgraded to pvgrub 4.6.3 and the problem went away. >>>>>> >>>>>> So I assume I'm seeing a new issue. How do I debug it? >>>>> >>>>> Interesting. Just tested it on upstream Xen and saw the same problem >>>>> with a rather old guest kernel (3.0 based, xen flavor), while a newer >>>>> kernel (4.1, pvops) is working. >>>>> >>>>> Can you give me some more details about the kernel you are trying to >>>>> boot? >>>> >>>> It's an unmodified 4.4.21 kernel which I compile by hand. The config is >>>> attached. Does that help? >>> >>> Not really. OTOH I think I don't need more help, as I've found a problem >>> in pvgrub. I have a patch which seems to correct the issue. Are you fine >>> with me adding you as the original reporter of the problem in the patch? >> >> Yes, I'm fine with adding me as the reporter. >> Do you want me to test the patch first? > > Sure. The attached patch is for Xen upstream, but I think it should > apply to Xen 4.7, too. This patch solved the issue for me. My domU boots fine again after recompiling pvgrub with the patch applied. Thanks! Regards, Sven _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure 2016-09-27 23:33 ` Sven Köhler @ 2016-09-28 3:50 ` Juergen Gross 2016-12-07 16:10 ` Sven Köhler 0 siblings, 1 reply; 16+ messages in thread From: Juergen Gross @ 2016-09-28 3:50 UTC (permalink / raw) To: Sven Köhler, xen-devel On 28/09/16 01:33, Sven Köhler wrote: > Am 27.09.2016 um 14:52 schrieb Juergen Gross: >> On 27/09/16 14:09, Sven Köhler wrote: >>> Am 27.09.2016 um 14:02 schrieb Juergen Gross: >>>> On 27/09/16 13:13, Sven Köhler wrote: >>>>> Am 27.09.2016 um 07:31 schrieb Juergen Gross: >>>>>> On 27/09/16 00:48, Sven Köhler wrote: >>>>>>> Am 26.09.2016 um 07:43 schrieb Juergen Gross: >>>>>>>> On 25/09/16 18:04, Sven Köhler wrote: >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I'm experiencing the bug below which was discussed on xen-devel December >>>>>>>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>>>>>>>> >>>>>>>>> The bug only seems to occur with the last domU booted on my machine. >>>>>>>>> Where do I find a patch that fixes that? >>>>>>>> >>>>>>>> The issue back in December was fixed by commit >>>>>>>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >>>>>>>> Either gentoo didn't update to the official Xen 4.7 release (including >>>>>>>> pvgrub) or you are seeing a new issue. >>>>>>> >>>>>>> From the looks of it, the Gentoo package is using the grub from the >>>>>>> xen-4.7.0 tarball. >>>>>>> >>>>>>> I downgraded to pvgrub 4.6.3 and the problem went away. >>>>>>> >>>>>>> So I assume I'm seeing a new issue. How do I debug it? >>>>>> >>>>>> Interesting. Just tested it on upstream Xen and saw the same problem >>>>>> with a rather old guest kernel (3.0 based, xen flavor), while a newer >>>>>> kernel (4.1, pvops) is working. >>>>>> >>>>>> Can you give me some more details about the kernel you are trying to >>>>>> boot? >>>>> >>>>> It's an unmodified 4.4.21 kernel which I compile by hand. The config is >>>>> attached. Does that help? >>>> >>>> Not really. OTOH I think I don't need more help, as I've found a problem >>>> in pvgrub. I have a patch which seems to correct the issue. Are you fine >>>> with me adding you as the original reporter of the problem in the patch? >>> >>> Yes, I'm fine with adding me as the reporter. >>> Do you want me to test the patch first? >> >> Sure. The attached patch is for Xen upstream, but I think it should >> apply to Xen 4.7, too. > > This patch solved the issue for me. My domU boots fine again after > recompiling pvgrub with the patch applied. > > Thanks! Thank you for the test! Juergen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure 2016-09-28 3:50 ` Juergen Gross @ 2016-12-07 16:10 ` Sven Köhler 2016-12-07 16:18 ` Juergen Gross ` (2 more replies) 0 siblings, 3 replies; 16+ messages in thread From: Sven Köhler @ 2016-12-07 16:10 UTC (permalink / raw) To: Juergen Gross, xen-devel Am 28.09.2016 um 05:50 schrieb Juergen Gross: > On 28/09/16 01:33, Sven Köhler wrote: >> Am 27.09.2016 um 14:52 schrieb Juergen Gross: >>> On 27/09/16 14:09, Sven Köhler wrote: >>>> Am 27.09.2016 um 14:02 schrieb Juergen Gross: >>>>> On 27/09/16 13:13, Sven Köhler wrote: >>>>>> Am 27.09.2016 um 07:31 schrieb Juergen Gross: >>>>>>> On 27/09/16 00:48, Sven Köhler wrote: >>>>>>>> Am 26.09.2016 um 07:43 schrieb Juergen Gross: >>>>>>>>> On 25/09/16 18:04, Sven Köhler wrote: >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> I'm experiencing the bug below which was discussed on xen-devel December >>>>>>>>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>>>>>>>>> >>>>>>>>>> The bug only seems to occur with the last domU booted on my machine. >>>>>>>>>> Where do I find a patch that fixes that? >>>>>>>>> >>>>>>>>> The issue back in December was fixed by commit >>>>>>>>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >>>>>>>>> Either gentoo didn't update to the official Xen 4.7 release (including >>>>>>>>> pvgrub) or you are seeing a new issue. >>>>>>>> >>>>>>>> From the looks of it, the Gentoo package is using the grub from the >>>>>>>> xen-4.7.0 tarball. >>>>>>>> >>>>>>>> I downgraded to pvgrub 4.6.3 and the problem went away. >>>>>>>> >>>>>>>> So I assume I'm seeing a new issue. How do I debug it? >>>>>>> >>>>>>> Interesting. Just tested it on upstream Xen and saw the same problem >>>>>>> with a rather old guest kernel (3.0 based, xen flavor), while a newer >>>>>>> kernel (4.1, pvops) is working. >>>>>>> >>>>>>> Can you give me some more details about the kernel you are trying to >>>>>>> boot? >>>>>> >>>>>> It's an unmodified 4.4.21 kernel which I compile by hand. The config is >>>>>> attached. Does that help? >>>>> >>>>> Not really. OTOH I think I don't need more help, as I've found a problem >>>>> in pvgrub. I have a patch which seems to correct the issue. Are you fine >>>>> with me adding you as the original reporter of the problem in the patch? >>>> >>>> Yes, I'm fine with adding me as the reporter. >>>> Do you want me to test the patch first? >>> >>> Sure. The attached patch is for Xen upstream, but I think it should >>> apply to Xen 4.7, too. >> >> This patch solved the issue for me. My domU boots fine again after >> recompiling pvgrub with the patch applied. >> >> Thanks! > > Thank you for the test! It seems this patch was not included in 4.7.1. That's a shame, cause I ran into the same issue after upgrading to 4.7.1. Regards, Sven _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure 2016-12-07 16:10 ` Sven Köhler @ 2016-12-07 16:18 ` Juergen Gross 2016-12-07 16:28 ` Jan Beulich [not found] ` <584846D402000078001266C3@suse.com> 2016-12-07 16:33 ` Jan Beulich [not found] ` <5848480702000078001266D5@suse.com> 2 siblings, 2 replies; 16+ messages in thread From: Juergen Gross @ 2016-12-07 16:18 UTC (permalink / raw) To: Sven Köhler, xen-devel, Jan Beulich On 07/12/16 17:10, Sven Köhler wrote: > Am 28.09.2016 um 05:50 schrieb Juergen Gross: >> On 28/09/16 01:33, Sven Köhler wrote: >>> Am 27.09.2016 um 14:52 schrieb Juergen Gross: >>>> On 27/09/16 14:09, Sven Köhler wrote: >>>>> Am 27.09.2016 um 14:02 schrieb Juergen Gross: >>>>>> On 27/09/16 13:13, Sven Köhler wrote: >>>>>>> Am 27.09.2016 um 07:31 schrieb Juergen Gross: >>>>>>>> On 27/09/16 00:48, Sven Köhler wrote: >>>>>>>>> Am 26.09.2016 um 07:43 schrieb Juergen Gross: >>>>>>>>>> On 25/09/16 18:04, Sven Köhler wrote: >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> I'm experiencing the bug below which was discussed on xen-devel December >>>>>>>>>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>>>>>>>>>> >>>>>>>>>>> The bug only seems to occur with the last domU booted on my machine. >>>>>>>>>>> Where do I find a patch that fixes that? >>>>>>>>>> >>>>>>>>>> The issue back in December was fixed by commit >>>>>>>>>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >>>>>>>>>> Either gentoo didn't update to the official Xen 4.7 release (including >>>>>>>>>> pvgrub) or you are seeing a new issue. >>>>>>>>> >>>>>>>>> From the looks of it, the Gentoo package is using the grub from the >>>>>>>>> xen-4.7.0 tarball. >>>>>>>>> >>>>>>>>> I downgraded to pvgrub 4.6.3 and the problem went away. >>>>>>>>> >>>>>>>>> So I assume I'm seeing a new issue. How do I debug it? >>>>>>>> >>>>>>>> Interesting. Just tested it on upstream Xen and saw the same problem >>>>>>>> with a rather old guest kernel (3.0 based, xen flavor), while a newer >>>>>>>> kernel (4.1, pvops) is working. >>>>>>>> >>>>>>>> Can you give me some more details about the kernel you are trying to >>>>>>>> boot? >>>>>>> >>>>>>> It's an unmodified 4.4.21 kernel which I compile by hand. The config is >>>>>>> attached. Does that help? >>>>>> >>>>>> Not really. OTOH I think I don't need more help, as I've found a problem >>>>>> in pvgrub. I have a patch which seems to correct the issue. Are you fine >>>>>> with me adding you as the original reporter of the problem in the patch? >>>>> >>>>> Yes, I'm fine with adding me as the reporter. >>>>> Do you want me to test the patch first? >>>> >>>> Sure. The attached patch is for Xen upstream, but I think it should >>>> apply to Xen 4.7, too. >>> >>> This patch solved the issue for me. My domU boots fine again after >>> recompiling pvgrub with the patch applied. >>> >>> Thanks! >> >> Thank you for the test! > > It seems this patch was not included in 4.7.1. That's a shame, cause I > ran into the same issue after upgrading to 4.7.1. Right. Jan, could you please include the patch for 4.7.2? Upstream commit was 9714f6b87e19b32d3a6663a20df6610265c4bfe5. Juergen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure 2016-12-07 16:18 ` Juergen Gross @ 2016-12-07 16:28 ` Jan Beulich 2016-12-07 16:38 ` Samuel Thibault [not found] ` <584846D402000078001266C3@suse.com> 1 sibling, 1 reply; 16+ messages in thread From: Jan Beulich @ 2016-12-07 16:28 UTC (permalink / raw) To: Samuel Thibault; +Cc: Juergen Gross, xen-devel, sven.koehler >>> On 07.12.16 at 17:18, <JGross@suse.com> wrote: > On 07/12/16 17:10, Sven Köhler wrote: >> Am 28.09.2016 um 05:50 schrieb Juergen Gross: >>> On 28/09/16 01:33, Sven Köhler wrote: >>>> Am 27.09.2016 um 14:52 schrieb Juergen Gross: >>>>> On 27/09/16 14:09, Sven Köhler wrote: >>>>>> Am 27.09.2016 um 14:02 schrieb Juergen Gross: >>>>>>> On 27/09/16 13:13, Sven Köhler wrote: >>>>>>>> Am 27.09.2016 um 07:31 schrieb Juergen Gross: >>>>>>>>> On 27/09/16 00:48, Sven Köhler wrote: >>>>>>>>>> Am 26.09.2016 um 07:43 schrieb Juergen Gross: >>>>>>>>>>> On 25/09/16 18:04, Sven Köhler wrote: >>>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> I'm experiencing the bug below which was discussed on xen-devel December >>>>>>>>>>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>>>>>>>>>>> >>>>>>>>>>>> The bug only seems to occur with the last domU booted on my machine. >>>>>>>>>>>> Where do I find a patch that fixes that? >>>>>>>>>>> >>>>>>>>>>> The issue back in December was fixed by commit >>>>>>>>>>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >>>>>>>>>>> Either gentoo didn't update to the official Xen 4.7 release (including >>>>>>>>>>> pvgrub) or you are seeing a new issue. >>>>>>>>>> >>>>>>>>>> From the looks of it, the Gentoo package is using the grub from the >>>>>>>>>> xen-4.7.0 tarball. >>>>>>>>>> >>>>>>>>>> I downgraded to pvgrub 4.6.3 and the problem went away. >>>>>>>>>> >>>>>>>>>> So I assume I'm seeing a new issue. How do I debug it? >>>>>>>>> >>>>>>>>> Interesting. Just tested it on upstream Xen and saw the same problem >>>>>>>>> with a rather old guest kernel (3.0 based, xen flavor), while a newer >>>>>>>>> kernel (4.1, pvops) is working. >>>>>>>>> >>>>>>>>> Can you give me some more details about the kernel you are trying to >>>>>>>>> boot? >>>>>>>> >>>>>>>> It's an unmodified 4.4.21 kernel which I compile by hand. The config is >>>>>>>> attached. Does that help? >>>>>>> >>>>>>> Not really. OTOH I think I don't need more help, as I've found a problem >>>>>>> in pvgrub. I have a patch which seems to correct the issue. Are you fine >>>>>>> with me adding you as the original reporter of the problem in the patch? >>>>>> >>>>>> Yes, I'm fine with adding me as the reporter. >>>>>> Do you want me to test the patch first? >>>>> >>>>> Sure. The attached patch is for Xen upstream, but I think it should >>>>> apply to Xen 4.7, too. >>>> >>>> This patch solved the issue for me. My domU boots fine again after >>>> recompiling pvgrub with the patch applied. >>>> >>>> Thanks! >>> >>> Thank you for the test! >> >> It seems this patch was not included in 4.7.1. That's a shame, cause I >> ran into the same issue after upgrading to 4.7.1. > > Right. Jan, could you please include the patch for 4.7.2? Upstream > commit was 9714f6b87e19b32d3a6663a20df6610265c4bfe5. Samuel, could you confirm that this is okay to backport. In which case the question then is whether 4.6.5 should get it too - with p2m_seg mentioned no-where else under stubdom/ I can't really tell where this is coming from. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure 2016-12-07 16:28 ` Jan Beulich @ 2016-12-07 16:38 ` Samuel Thibault 2016-12-07 16:54 ` Sven Köhler 0 siblings, 1 reply; 16+ messages in thread From: Samuel Thibault @ 2016-12-07 16:38 UTC (permalink / raw) To: Jan Beulich; +Cc: Juergen Gross, xen-devel, sven.koehler Hello, Jan Beulich, on Wed 07 Dec 2016 09:28:52 -0700, wrote: > > Right. Jan, could you please include the patch for 4.7.2? Upstream > > commit was 9714f6b87e19b32d3a6663a20df6610265c4bfe5. > > Samuel, could you confirm that this is okay to backport. For 4.7, yes. > In which case the question then is whether 4.6.5 should get it too - > with p2m_seg mentioned no-where else under stubdom/ I can't really > tell where this is coming from. For 4.6, I don't think so: Commit abdf3c5b2b971dc12e665e8e0cda184b416efffe ('libxc: create p2m list outside of kernel mapping if supported') introduced that new case, and it's not in 4.6. Samuel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure 2016-12-07 16:38 ` Samuel Thibault @ 2016-12-07 16:54 ` Sven Köhler 0 siblings, 0 replies; 16+ messages in thread From: Sven Köhler @ 2016-12-07 16:54 UTC (permalink / raw) To: Samuel Thibault, Jan Beulich, xen-devel, Juergen Gross Am 07.12.2016 um 17:38 schrieb Samuel Thibault: > Hello, > > Jan Beulich, on Wed 07 Dec 2016 09:28:52 -0700, wrote: >>> Right. Jan, could you please include the patch for 4.7.2? Upstream >>> commit was 9714f6b87e19b32d3a6663a20df6610265c4bfe5. >> >> Samuel, could you confirm that this is okay to backport. > > For 4.7, yes. > >> In which case the question then is whether 4.6.5 should get it too - >> with p2m_seg mentioned no-where else under stubdom/ I can't really >> tell where this is coming from. > > For 4.6, I don't think so: > > Commit abdf3c5b2b971dc12e665e8e0cda184b416efffe ('libxc: create p2m list > outside of kernel mapping if supported') introduced that new case, and > it's not in 4.6. For me, the problems started with 4.7.0. Prior to that, the domUs were booting fine. So I can confirm that 4.6.x was not affected. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
[parent not found: <584846D402000078001266C3@suse.com>]
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure [not found] ` <584846D402000078001266C3@suse.com> @ 2016-12-07 19:34 ` Juergen Gross 0 siblings, 0 replies; 16+ messages in thread From: Juergen Gross @ 2016-12-07 19:34 UTC (permalink / raw) To: Jan Beulich, Samuel Thibault; +Cc: xen-devel, sven.koehler On 07/12/16 17:28, Jan Beulich wrote: >>>> On 07.12.16 at 17:18, <JGross@suse.com> wrote: >> On 07/12/16 17:10, Sven Köhler wrote: >>> Am 28.09.2016 um 05:50 schrieb Juergen Gross: >>>> On 28/09/16 01:33, Sven Köhler wrote: >>>>> Am 27.09.2016 um 14:52 schrieb Juergen Gross: >>>>>> On 27/09/16 14:09, Sven Köhler wrote: >>>>>>> Am 27.09.2016 um 14:02 schrieb Juergen Gross: >>>>>>>> On 27/09/16 13:13, Sven Köhler wrote: >>>>>>>>> Am 27.09.2016 um 07:31 schrieb Juergen Gross: >>>>>>>>>> On 27/09/16 00:48, Sven Köhler wrote: >>>>>>>>>>> Am 26.09.2016 um 07:43 schrieb Juergen Gross: >>>>>>>>>>>> On 25/09/16 18:04, Sven Köhler wrote: >>>>>>>>>>>>> Hi, >>>>>>>>>>>>> >>>>>>>>>>>>> I'm experiencing the bug below which was discussed on xen-devel December >>>>>>>>>>>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>>>>>>>>>>>> >>>>>>>>>>>>> The bug only seems to occur with the last domU booted on my machine. >>>>>>>>>>>>> Where do I find a patch that fixes that? >>>>>>>>>>>> >>>>>>>>>>>> The issue back in December was fixed by commit >>>>>>>>>>>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >>>>>>>>>>>> Either gentoo didn't update to the official Xen 4.7 release (including >>>>>>>>>>>> pvgrub) or you are seeing a new issue. >>>>>>>>>>> >>>>>>>>>>> From the looks of it, the Gentoo package is using the grub from the >>>>>>>>>>> xen-4.7.0 tarball. >>>>>>>>>>> >>>>>>>>>>> I downgraded to pvgrub 4.6.3 and the problem went away. >>>>>>>>>>> >>>>>>>>>>> So I assume I'm seeing a new issue. How do I debug it? >>>>>>>>>> >>>>>>>>>> Interesting. Just tested it on upstream Xen and saw the same problem >>>>>>>>>> with a rather old guest kernel (3.0 based, xen flavor), while a newer >>>>>>>>>> kernel (4.1, pvops) is working. >>>>>>>>>> >>>>>>>>>> Can you give me some more details about the kernel you are trying to >>>>>>>>>> boot? >>>>>>>>> >>>>>>>>> It's an unmodified 4.4.21 kernel which I compile by hand. The config is >>>>>>>>> attached. Does that help? >>>>>>>> >>>>>>>> Not really. OTOH I think I don't need more help, as I've found a problem >>>>>>>> in pvgrub. I have a patch which seems to correct the issue. Are you fine >>>>>>>> with me adding you as the original reporter of the problem in the patch? >>>>>>> >>>>>>> Yes, I'm fine with adding me as the reporter. >>>>>>> Do you want me to test the patch first? >>>>>> >>>>>> Sure. The attached patch is for Xen upstream, but I think it should >>>>>> apply to Xen 4.7, too. >>>>> >>>>> This patch solved the issue for me. My domU boots fine again after >>>>> recompiling pvgrub with the patch applied. >>>>> >>>>> Thanks! >>>> >>>> Thank you for the test! >>> >>> It seems this patch was not included in 4.7.1. That's a shame, cause I >>> ran into the same issue after upgrading to 4.7.1. >> >> Right. Jan, could you please include the patch for 4.7.2? Upstream >> commit was 9714f6b87e19b32d3a6663a20df6610265c4bfe5. > > Samuel, could you confirm that this is okay to backport. In > which case the question then is whether 4.6.5 should get it > too - with p2m_seg mentioned no-where else under stubdom/ > I can't really tell where this is coming from. 4.6 is not affected. Juergen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure 2016-12-07 16:10 ` Sven Köhler 2016-12-07 16:18 ` Juergen Gross @ 2016-12-07 16:33 ` Jan Beulich 2016-12-07 16:39 ` Sven Köhler [not found] ` <5848480702000078001266D5@suse.com> 2 siblings, 1 reply; 16+ messages in thread From: Jan Beulich @ 2016-12-07 16:33 UTC (permalink / raw) To: Sven Köhler; +Cc: Juergen Gross, xen-devel >>> On 07.12.16 at 17:10, <sven.koehler@gmail.com> wrote: > Am 28.09.2016 um 05:50 schrieb Juergen Gross: >> On 28/09/16 01:33, Sven Köhler wrote: >>> Am 27.09.2016 um 14:52 schrieb Juergen Gross: >>>> On 27/09/16 14:09, Sven Köhler wrote: >>>>> Am 27.09.2016 um 14:02 schrieb Juergen Gross: >>>>>> On 27/09/16 13:13, Sven Köhler wrote: >>>>>>> Am 27.09.2016 um 07:31 schrieb Juergen Gross: >>>>>>>> On 27/09/16 00:48, Sven Köhler wrote: >>>>>>>>> Am 26.09.2016 um 07:43 schrieb Juergen Gross: >>>>>>>>>> On 25/09/16 18:04, Sven Köhler wrote: >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> I'm experiencing the bug below which was discussed on xen-devel December >>>>>>>>>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>>>>>>>>>> >>>>>>>>>>> The bug only seems to occur with the last domU booted on my machine. >>>>>>>>>>> Where do I find a patch that fixes that? >>>>>>>>>> >>>>>>>>>> The issue back in December was fixed by commit >>>>>>>>>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >>>>>>>>>> Either gentoo didn't update to the official Xen 4.7 release (including >>>>>>>>>> pvgrub) or you are seeing a new issue. >>>>>>>>> >>>>>>>>> From the looks of it, the Gentoo package is using the grub from the >>>>>>>>> xen-4.7.0 tarball. >>>>>>>>> >>>>>>>>> I downgraded to pvgrub 4.6.3 and the problem went away. >>>>>>>>> >>>>>>>>> So I assume I'm seeing a new issue. How do I debug it? >>>>>>>> >>>>>>>> Interesting. Just tested it on upstream Xen and saw the same problem >>>>>>>> with a rather old guest kernel (3.0 based, xen flavor), while a newer >>>>>>>> kernel (4.1, pvops) is working. >>>>>>>> >>>>>>>> Can you give me some more details about the kernel you are trying to >>>>>>>> boot? >>>>>>> >>>>>>> It's an unmodified 4.4.21 kernel which I compile by hand. The config is >>>>>>> attached. Does that help? >>>>>> >>>>>> Not really. OTOH I think I don't need more help, as I've found a problem >>>>>> in pvgrub. I have a patch which seems to correct the issue. Are you fine >>>>>> with me adding you as the original reporter of the problem in the patch? >>>>> >>>>> Yes, I'm fine with adding me as the reporter. >>>>> Do you want me to test the patch first? >>>> >>>> Sure. The attached patch is for Xen upstream, but I think it should >>>> apply to Xen 4.7, too. >>> >>> This patch solved the issue for me. My domU boots fine again after >>> recompiling pvgrub with the patch applied. >>> >>> Thanks! >> >> Thank you for the test! > > It seems this patch was not included in 4.7.1. That's a shame, cause I > ran into the same issue after upgrading to 4.7.1. I don't think anyone requested its inclusion - that process is in no way automatic. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure 2016-12-07 16:33 ` Jan Beulich @ 2016-12-07 16:39 ` Sven Köhler 0 siblings, 0 replies; 16+ messages in thread From: Sven Köhler @ 2016-12-07 16:39 UTC (permalink / raw) To: Jan Beulich; +Cc: Juergen Gross, xen-devel Am 07.12.2016 um 17:33 schrieb Jan Beulich: >>>> On 07.12.16 at 17:10, <sven.koehler@gmail.com> wrote: >> Am 28.09.2016 um 05:50 schrieb Juergen Gross: >>> On 28/09/16 01:33, Sven Köhler wrote: >>>> Am 27.09.2016 um 14:52 schrieb Juergen Gross: >>>>> On 27/09/16 14:09, Sven Köhler wrote: >>>>>> Am 27.09.2016 um 14:02 schrieb Juergen Gross: >>>>>>> On 27/09/16 13:13, Sven Köhler wrote: >>>>>>>> Am 27.09.2016 um 07:31 schrieb Juergen Gross: >>>>>>>>> On 27/09/16 00:48, Sven Köhler wrote: >>>>>>>>>> Am 26.09.2016 um 07:43 schrieb Juergen Gross: >>>>>>>>>>> On 25/09/16 18:04, Sven Köhler wrote: >>>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> I'm experiencing the bug below which was discussed on xen-devel December >>>>>>>>>>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>>>>>>>>>>> >>>>>>>>>>>> The bug only seems to occur with the last domU booted on my machine. >>>>>>>>>>>> Where do I find a patch that fixes that? >>>>>>>>>>> >>>>>>>>>>> The issue back in December was fixed by commit >>>>>>>>>>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >>>>>>>>>>> Either gentoo didn't update to the official Xen 4.7 release (including >>>>>>>>>>> pvgrub) or you are seeing a new issue. >>>>>>>>>> >>>>>>>>>> From the looks of it, the Gentoo package is using the grub from the >>>>>>>>>> xen-4.7.0 tarball. >>>>>>>>>> >>>>>>>>>> I downgraded to pvgrub 4.6.3 and the problem went away. >>>>>>>>>> >>>>>>>>>> So I assume I'm seeing a new issue. How do I debug it? >>>>>>>>> >>>>>>>>> Interesting. Just tested it on upstream Xen and saw the same problem >>>>>>>>> with a rather old guest kernel (3.0 based, xen flavor), while a newer >>>>>>>>> kernel (4.1, pvops) is working. >>>>>>>>> >>>>>>>>> Can you give me some more details about the kernel you are trying to >>>>>>>>> boot? >>>>>>>> >>>>>>>> It's an unmodified 4.4.21 kernel which I compile by hand. The config is >>>>>>>> attached. Does that help? >>>>>>> >>>>>>> Not really. OTOH I think I don't need more help, as I've found a problem >>>>>>> in pvgrub. I have a patch which seems to correct the issue. Are you fine >>>>>>> with me adding you as the original reporter of the problem in the patch? >>>>>> >>>>>> Yes, I'm fine with adding me as the reporter. >>>>>> Do you want me to test the patch first? >>>>> >>>>> Sure. The attached patch is for Xen upstream, but I think it should >>>>> apply to Xen 4.7, too. >>>> >>>> This patch solved the issue for me. My domU boots fine again after >>>> recompiling pvgrub with the patch applied. >>>> >>>> Thanks! >>> >>> Thank you for the test! >> >> It seems this patch was not included in 4.7.1. That's a shame, cause I >> ran into the same issue after upgrading to 4.7.1. > > I don't think anyone requested its inclusion - that process is in no > way automatic. I reported the error for 4.7.0, and I thought that Juergen might have suggested it for inclusion. I upgraded to 4.7.1 just a few days ago, so I thought I should point out that this patch was missed. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
[parent not found: <5848480702000078001266D5@suse.com>]
* Re: [Xen-users] pvgrub: Error 9: Unknown boot failure [not found] ` <5848480702000078001266D5@suse.com> @ 2016-12-07 19:34 ` Juergen Gross 0 siblings, 0 replies; 16+ messages in thread From: Juergen Gross @ 2016-12-07 19:34 UTC (permalink / raw) To: Jan Beulich, Sven Köhler; +Cc: xen-devel On 07/12/16 17:33, Jan Beulich wrote: >>>> On 07.12.16 at 17:10, <sven.koehler@gmail.com> wrote: >> Am 28.09.2016 um 05:50 schrieb Juergen Gross: >>> On 28/09/16 01:33, Sven Köhler wrote: >>>> Am 27.09.2016 um 14:52 schrieb Juergen Gross: >>>>> On 27/09/16 14:09, Sven Köhler wrote: >>>>>> Am 27.09.2016 um 14:02 schrieb Juergen Gross: >>>>>>> On 27/09/16 13:13, Sven Köhler wrote: >>>>>>>> Am 27.09.2016 um 07:31 schrieb Juergen Gross: >>>>>>>>> On 27/09/16 00:48, Sven Köhler wrote: >>>>>>>>>> Am 26.09.2016 um 07:43 schrieb Juergen Gross: >>>>>>>>>>> On 25/09/16 18:04, Sven Köhler wrote: >>>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> I'm experiencing the bug below which was discussed on xen-devel December >>>>>>>>>>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo. >>>>>>>>>>>> >>>>>>>>>>>> The bug only seems to occur with the last domU booted on my machine. >>>>>>>>>>>> Where do I find a patch that fixes that? >>>>>>>>>>> >>>>>>>>>>> The issue back in December was fixed by commit >>>>>>>>>>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7. >>>>>>>>>>> Either gentoo didn't update to the official Xen 4.7 release (including >>>>>>>>>>> pvgrub) or you are seeing a new issue. >>>>>>>>>> >>>>>>>>>> From the looks of it, the Gentoo package is using the grub from the >>>>>>>>>> xen-4.7.0 tarball. >>>>>>>>>> >>>>>>>>>> I downgraded to pvgrub 4.6.3 and the problem went away. >>>>>>>>>> >>>>>>>>>> So I assume I'm seeing a new issue. How do I debug it? >>>>>>>>> >>>>>>>>> Interesting. Just tested it on upstream Xen and saw the same problem >>>>>>>>> with a rather old guest kernel (3.0 based, xen flavor), while a newer >>>>>>>>> kernel (4.1, pvops) is working. >>>>>>>>> >>>>>>>>> Can you give me some more details about the kernel you are trying to >>>>>>>>> boot? >>>>>>>> >>>>>>>> It's an unmodified 4.4.21 kernel which I compile by hand. The config is >>>>>>>> attached. Does that help? >>>>>>> >>>>>>> Not really. OTOH I think I don't need more help, as I've found a problem >>>>>>> in pvgrub. I have a patch which seems to correct the issue. Are you fine >>>>>>> with me adding you as the original reporter of the problem in the patch? >>>>>> >>>>>> Yes, I'm fine with adding me as the reporter. >>>>>> Do you want me to test the patch first? >>>>> >>>>> Sure. The attached patch is for Xen upstream, but I think it should >>>>> apply to Xen 4.7, too. >>>> >>>> This patch solved the issue for me. My domU boots fine again after >>>> recompiling pvgrub with the patch applied. >>>> >>>> Thanks! >>> >>> Thank you for the test! >> >> It seems this patch was not included in 4.7.1. That's a shame, cause I >> ran into the same issue after upgrading to 4.7.1. > > I don't think anyone requested its inclusion - that process is in no > way automatic. I mentioned it in the patch. See https://lists.xen.org/archives/html/xen-devel/2016-09/msg02993.html Juergen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2016-12-07 19:34 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <ns8sjf$etc$1@blaine.gmane.org>
[not found] ` <53d7467a-5c5a-8f48-fae5-1b21b8e7459e@suse.com>
[not found] ` <9fc0a827-b452-50bb-6923-3a650b104b56@gmail.com>
2016-09-27 5:31 ` [Xen-users] pvgrub: Error 9: Unknown boot failure Juergen Gross
2016-09-27 11:13 ` Sven Köhler
2016-09-27 12:02 ` Juergen Gross
2016-09-27 12:09 ` Sven Köhler
2016-09-27 12:52 ` Juergen Gross
2016-09-27 23:33 ` Sven Köhler
2016-09-28 3:50 ` Juergen Gross
2016-12-07 16:10 ` Sven Köhler
2016-12-07 16:18 ` Juergen Gross
2016-12-07 16:28 ` Jan Beulich
2016-12-07 16:38 ` Samuel Thibault
2016-12-07 16:54 ` Sven Köhler
[not found] ` <584846D402000078001266C3@suse.com>
2016-12-07 19:34 ` Juergen Gross
2016-12-07 16:33 ` Jan Beulich
2016-12-07 16:39 ` Sven Köhler
[not found] ` <5848480702000078001266D5@suse.com>
2016-12-07 19:34 ` Juergen Gross
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).