Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Sven Köhler]

Also asking the devel-list for help:

Sven Köhler schrieb:
> Hi,
> 
> I cannot execute any 32-bit executables. Same problem with 2.6.29-rc7.
> 
> I compiled and linked them statically on another machine where they work
> just fine! But inside the xen domU, they just segfault:
> 
> 
> a.out[32093] general protection ip:f7f7042f sp:ffc6f2d4 error:0
> 
> 
> Is this a knows problem? CONFIG_IA32_EMULATION is turned on!
> 
> 
> Regards,
>   Sven

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

Sven Köhler wrote:
> Also asking the devel-list for help:
>
> Sven Köhler schrieb:
>> Hi,
>>
>> I cannot execute any 32-bit executables. Same problem with 2.6.29-rc7.
>>
>> I compiled and linked them statically on another machine where they work
>> just fine! But inside the xen domU, they just segfault:
>>
>>
>> a.out[32093] general protection ip:f7f7042f sp:ffc6f2d4 error:0
>>
>>
>> Is this a knows problem? CONFIG_IA32_EMULATION is turned on!

Hm, it works for me.  Can you give more detail about what you're trying 
to run, the kernel .config and the distro?  dmesg output would have some 
clues too.

Thanks,
    J

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

Jeremy Fitzhardinge wrote:
> Sven Köhler wrote:
>> Also asking the devel-list for help:
>>
>> Sven Köhler schrieb:
>>> Hi,
>>>
>>> I cannot execute any 32-bit executables. Same problem with 2.6.29-rc7.
>>>
>>> I compiled and linked them statically on another machine where they 
>>> work
>>> just fine! But inside the xen domU, they just segfault:
>>>
>>>
>>> a.out[32093] general protection ip:f7f7042f sp:ffc6f2d4 error:0
>>>
>>>
>>> Is this a knows problem? CONFIG_IA32_EMULATION is turned on!
>
> Hm, it works for me.  Can you give more detail about what you're 
> trying to run, the kernel .config and the distro?  dmesg output would 
> have some clues too. 

Oh, and what's the CPU?  AMD?

    J

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Sven Köhler]

[-- Attachment #1: Type: text/plain, Size: 2436 bytes --]

Jeremy Fitzhardinge schrieb:
> Jeremy Fitzhardinge wrote:
>> Sven Köhler wrote:
>>> Also asking the devel-list for help:
>>>
>>> Sven Köhler schrieb:
>>>> Hi,
>>>>
>>>> I cannot execute any 32-bit executables. Same problem with 2.6.29-rc7.
>>>>
>>>> I compiled and linked them statically on another machine where they 
>>>> work
>>>> just fine! But inside the xen domU, they just segfault:
>>>>
>>>>
>>>> a.out[32093] general protection ip:f7f7042f sp:ffc6f2d4 error:0
>>>>
>>>>
>>>> Is this a knows problem? CONFIG_IA32_EMULATION is turned on!
>>
>> Hm, it works for me.  Can you give more detail about what you're 
>> trying to run, the kernel .config and the distro?  dmesg output would 
>> have some clues too. 
> 
> Oh, and what's the CPU?  AMD?

The host is running Xen version 3.3.0.
The host CPU is:

# cat /proc/cpuinfo
processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 15
model		: 47
model name	: AMD Athlon(tm) 64 Processor 3800+
stepping	: 2
cpu MHz		: 2399.822
cache size	: 512 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu de tsc msr pae cx8 apic mtrr cmov pat clflush mmx fxsr sse 
sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm
bogomips	: 4800.70
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc

The kernel is vanilla (except for the xen/blkfront: use blk_rq_map_sg to 
generate ring entries patch). The config of my 2.6.28.7 is attached.

The program I'm trying to run is:
$ cat test.c
#include <stdio.h>

int main(void)
{
   printf("Hallo Welt!\n");
   return 0;
}

I compiled it with "gcc --static test.c" on other box where the program 
runs fine and copied the output to my domU. I checked with ldd, that it 
really isn't a dynamic executable.

The dmesg output on the domU is this mysterious:
a.out[32093] general protection ip:f7f7042f sp:ffc6f2d4 error:0

The line appears each time, that the program segfaults.


On the host, I'm using Gentoo and xen has been compiled using the 
following settings:
[ebuild   R   ] app-emulation/xen-tools-3.3.0  USE="screen -acm -api 
-custom-cflags -debug -doc -flask (-hvm) -pygrub" 0 kB
[ebuild   R   ] app-emulation/xen-3.3.0  USE="pae -acm -custom-cflags 
-debug -flask -xsm" 0 kB


If you need more info just ask.


Regards,
   Sven

[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 26847 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.28.7
# Wed Mar 11 22:31:04 2009
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_FAST_CMPXCHG_LOCAL=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
# CONFIG_HAVE_SETUP_PER_CPU_AREA is not set
# CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
# CONFIG_KTIME_SCALAR is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_CGROUPS is not set
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_GROUP_SCHED is not set
# CONFIG_SYSFS_DEPRECATED_V2 is not set
# CONFIG_RELAY is not set
CONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_IPC_NS is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_COMPAT_BRK=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not set
# CONFIG_MARKERS is not set
CONFIG_HAVE_OPROFILE=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_MODULES is not set
CONFIG_BLOCK=y
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_BLK_DEV_INTEGRITY is not set
CONFIG_BLOCK_COMPAT=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_CLASSIC_RCU=y
# CONFIG_FREEZER is not set

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
# CONFIG_SMP is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_VSMP is not set
CONFIG_PARAVIRT_GUEST=y
CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=32
# CONFIG_KVM_CLOCK is not set
# CONFIG_KVM_GUEST is not set
CONFIG_PARAVIRT=y
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_MEMTEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_CPU=y
CONFIG_X86_L1_CACHE_BYTES=128
CONFIG_X86_INTERNODE_CACHE_BYTES=128
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_WP_WORKS_OK=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_64=y
# CONFIG_X86_DS is not set
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=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_MCE is not set
# 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_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_MEMORY_PROBE=y
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
# CONFIG_DISCONTIGMEM_MANUAL is not set
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y
CONFIG_MEMORY_HOTPLUG=y
CONFIG_MEMORY_HOTPLUG_SPARSE=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_UNEVICTABLE_LRU=y
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
# CONFIG_X86_RESERVE_LOW_64K is not set
CONFIG_MTRR=y
# CONFIG_MTRR_SANITIZER is not set
CONFIG_X86_PAT=y
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=0x200000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x200000
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management and ACPI options
#
# CONFIG_PM is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_IDLE is not set

#
# Memory power savings
#
# CONFIG_I7300_IDLE is not set

#
# Bus options (PCI etc.)
#
# CONFIG_PCI is not set
# CONFIG_ARCH_SUPPORTS_MSI is not set
CONFIG_ISA_DMA_API=y
# CONFIG_PCCARD 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_HAVE_AOUT is not set
CONFIG_BINFMT_MISC=y
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES 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 is not set
# 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=y
CONFIG_INET_TCP_DIAG=y
# 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 is not set
# CONFIG_NETWORK_SECMARK is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_NETLINK_QUEUE=y
CONFIG_NETFILTER_NETLINK_LOG=y
CONFIG_NF_CONNTRACK=y
CONFIG_NF_CT_ACCT=y
CONFIG_NF_CONNTRACK_MARK=y
# CONFIG_NF_CONNTRACK_EVENTS is not set
# CONFIG_NF_CT_PROTO_DCCP is not set
CONFIG_NF_CT_PROTO_GRE=y
# CONFIG_NF_CT_PROTO_SCTP is not set
CONFIG_NF_CT_PROTO_UDPLITE=y
CONFIG_NF_CONNTRACK_AMANDA=y
CONFIG_NF_CONNTRACK_FTP=y
CONFIG_NF_CONNTRACK_H323=y
CONFIG_NF_CONNTRACK_IRC=y
CONFIG_NF_CONNTRACK_NETBIOS_NS=y
CONFIG_NF_CONNTRACK_PPTP=y
# CONFIG_NF_CONNTRACK_SANE is not set
CONFIG_NF_CONNTRACK_SIP=y
CONFIG_NF_CONNTRACK_TFTP=y
CONFIG_NF_CT_NETLINK=y
# CONFIG_NETFILTER_TPROXY is not set
CONFIG_NETFILTER_XTABLES=y
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=y
CONFIG_NETFILTER_XT_TARGET_CONNMARK=y
CONFIG_NETFILTER_XT_TARGET_DSCP=y
CONFIG_NETFILTER_XT_TARGET_MARK=y
CONFIG_NETFILTER_XT_TARGET_NFLOG=y
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=y
CONFIG_NETFILTER_XT_TARGET_RATEEST=y
CONFIG_NETFILTER_XT_TARGET_TCPMSS=y
# CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set
CONFIG_NETFILTER_XT_MATCH_COMMENT=y
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=y
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=y
CONFIG_NETFILTER_XT_MATCH_CONNMARK=y
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
CONFIG_NETFILTER_XT_MATCH_DCCP=y
CONFIG_NETFILTER_XT_MATCH_DSCP=y
CONFIG_NETFILTER_XT_MATCH_ESP=y
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=y
CONFIG_NETFILTER_XT_MATCH_HELPER=y
CONFIG_NETFILTER_XT_MATCH_IPRANGE=y
CONFIG_NETFILTER_XT_MATCH_LENGTH=y
CONFIG_NETFILTER_XT_MATCH_LIMIT=y
CONFIG_NETFILTER_XT_MATCH_MAC=y
CONFIG_NETFILTER_XT_MATCH_MARK=y
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=y
CONFIG_NETFILTER_XT_MATCH_OWNER=y
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=y
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=y
CONFIG_NETFILTER_XT_MATCH_QUOTA=y
CONFIG_NETFILTER_XT_MATCH_RATEEST=y
CONFIG_NETFILTER_XT_MATCH_REALM=y
CONFIG_NETFILTER_XT_MATCH_RECENT=y
# CONFIG_NETFILTER_XT_MATCH_RECENT_PROC_COMPAT is not set
# CONFIG_NETFILTER_XT_MATCH_SCTP is not set
CONFIG_NETFILTER_XT_MATCH_STATE=y
CONFIG_NETFILTER_XT_MATCH_STATISTIC=y
CONFIG_NETFILTER_XT_MATCH_STRING=y
CONFIG_NETFILTER_XT_MATCH_TCPMSS=y
CONFIG_NETFILTER_XT_MATCH_TIME=y
CONFIG_NETFILTER_XT_MATCH_U32=y
# CONFIG_IP_VS is not set

#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=y
CONFIG_NF_CONNTRACK_IPV4=y
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_ADDRTYPE=y
CONFIG_IP_NF_MATCH_AH=y
CONFIG_IP_NF_MATCH_ECN=y
CONFIG_IP_NF_MATCH_TTL=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
# CONFIG_IP_NF_TARGET_ULOG is not set
CONFIG_NF_NAT=y
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_IP_NF_TARGET_NETMAP=y
CONFIG_IP_NF_TARGET_REDIRECT=y
# CONFIG_NF_NAT_SNMP_BASIC is not set
CONFIG_NF_NAT_PROTO_GRE=y
CONFIG_NF_NAT_PROTO_UDPLITE=y
CONFIG_NF_NAT_FTP=y
CONFIG_NF_NAT_IRC=y
CONFIG_NF_NAT_TFTP=y
CONFIG_NF_NAT_AMANDA=y
CONFIG_NF_NAT_PPTP=y
CONFIG_NF_NAT_H323=y
CONFIG_NF_NAT_SIP=y
CONFIG_IP_NF_MANGLE=y
# CONFIG_IP_NF_TARGET_CLUSTERIP is not set
CONFIG_IP_NF_TARGET_ECN=y
CONFIG_IP_NF_TARGET_TTL=y
# CONFIG_IP_NF_RAW is not set
CONFIG_IP_NF_ARPTABLES=y
CONFIG_IP_NF_ARPFILTER=y
CONFIG_IP_NF_ARP_MANGLE=y
CONFIG_BRIDGE_NF_EBTABLES=y
CONFIG_BRIDGE_EBT_BROUTE=y
CONFIG_BRIDGE_EBT_T_FILTER=y
CONFIG_BRIDGE_EBT_T_NAT=y
CONFIG_BRIDGE_EBT_802_3=y
CONFIG_BRIDGE_EBT_AMONG=y
CONFIG_BRIDGE_EBT_ARP=y
CONFIG_BRIDGE_EBT_IP=y
CONFIG_BRIDGE_EBT_LIMIT=y
CONFIG_BRIDGE_EBT_MARK=y
CONFIG_BRIDGE_EBT_PKTTYPE=y
CONFIG_BRIDGE_EBT_STP=y
CONFIG_BRIDGE_EBT_VLAN=y
CONFIG_BRIDGE_EBT_ARPREPLY=y
CONFIG_BRIDGE_EBT_DNAT=y
CONFIG_BRIDGE_EBT_MARK_T=y
CONFIG_BRIDGE_EBT_REDIRECT=y
CONFIG_BRIDGE_EBT_SNAT=y
CONFIG_BRIDGE_EBT_LOG=y
# CONFIG_BRIDGE_EBT_ULOG is not set
CONFIG_BRIDGE_EBT_NFLOG=y
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
CONFIG_STP=y
CONFIG_BRIDGE=y
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
CONFIG_LLC=y
# 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_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set
CONFIG_NET_CLS_ROUTE=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_PHONET is not set
# CONFIG_WIRELESS is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=y
# 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_MISC_DEVICES is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set

#
# SCSI device support
#
# 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_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=y
# CONFIG_DM_SNAPSHOT is not set
# CONFIG_DM_MIRROR 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_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=y
# CONFIG_VETH is not set
# CONFIG_NET_ETHERNET is not set
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
# CONFIG_IWLWIFI_LEDS is not set
# CONFIG_WAN is not set
CONFIG_XEN_NETDEV_FRONTEND=y
CONFIG_PPP=y
# CONFIG_PPP_MULTILINK is not set
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_PPP_DEFLATE=y
CONFIG_PPP_BSDCOMP=y
# CONFIG_PPP_MPPE is not set
# CONFIG_PPPOE is not set
# CONFIG_PPPOL2TP is not set
# CONFIG_SLIP is not set
CONFIG_SLHC=y
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
CONFIG_XEN_KBDDEV_FRONTEND=y

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY 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 is not set

#
# Hardware I/O ports
#
CONFIG_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_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
# CONFIG_DEVKMEM is not set
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
CONFIG_FIX_EARLYCON_MEM=y

#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_XEN=y
# CONFIG_IPMI_HANDLER is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_R3964 is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HANGCHECK_TIMER=y
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
# CONFIG_I2C is not set
# CONFIG_SPI is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_HWMON is not set
# CONFIG_THERMAL is not set
# CONFIG_THERMAL_HWMON is not set
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_REGULATOR is not set

#
# Multimedia devices
#

#
# Multimedia core support
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_VIDEO_MEDIA is not set

#
# Multimedia drivers
#
# CONFIG_DAB is not set

#
# Graphics support
#
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
# 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_S1D13XXX is not set
# CONFIG_FB_VIRTUAL is not set
CONFIG_XEN_FBDEV_FRONTEND=y
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_LOGO is not set
# CONFIG_SOUND is not set
# CONFIG_HID_SUPPORT is not set
# CONFIG_USB_SUPPORT 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 is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
# CONFIG_UIO is not set
# CONFIG_XEN_BALLOON is not set
# CONFIG_STAGING 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_ISCSI_IBFT_FIND is not set

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT2_FS_XIP=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=y
# CONFIG_EXT4DEV_COMPAT is not set
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
CONFIG_FS_XIP=y
CONFIG_JBD=y
CONFIG_JBD2=y
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_FILE_LOCKING=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_DNOTIFY is not set
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
CONFIG_FUSE_FS=y
CONFIG_GENERIC_ACL=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# 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_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_CONFIGFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
# CONFIG_NFS_V4 is not set
CONFIG_NFSD=y
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
# CONFIG_NFSD_V4 is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_REGISTER_V4 is not set
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
CONFIG_CIFS=y
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=y
CONFIG_NLS_CODEPAGE_775=y
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_CODEPAGE_852=y
CONFIG_NLS_CODEPAGE_855=y
CONFIG_NLS_CODEPAGE_857=y
CONFIG_NLS_CODEPAGE_860=y
CONFIG_NLS_CODEPAGE_861=y
CONFIG_NLS_CODEPAGE_862=y
CONFIG_NLS_CODEPAGE_863=y
CONFIG_NLS_CODEPAGE_864=y
CONFIG_NLS_CODEPAGE_865=y
CONFIG_NLS_CODEPAGE_866=y
CONFIG_NLS_CODEPAGE_869=y
CONFIG_NLS_CODEPAGE_936=y
CONFIG_NLS_CODEPAGE_950=y
CONFIG_NLS_CODEPAGE_932=y
CONFIG_NLS_CODEPAGE_949=y
CONFIG_NLS_CODEPAGE_874=y
CONFIG_NLS_ISO8859_8=y
CONFIG_NLS_CODEPAGE_1250=y
CONFIG_NLS_CODEPAGE_1251=y
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=y
CONFIG_NLS_ISO8859_3=y
CONFIG_NLS_ISO8859_4=y
CONFIG_NLS_ISO8859_5=y
CONFIG_NLS_ISO8859_6=y
CONFIG_NLS_ISO8859_7=y
CONFIG_NLS_ISO8859_9=y
CONFIG_NLS_ISO8859_13=y
CONFIG_NLS_ISO8859_14=y
CONFIG_NLS_ISO8859_15=y
CONFIG_NLS_KOI8_R=y
CONFIG_NLS_KOI8_U=y
CONFIG_NLS_UTF8=y
# CONFIG_DLM is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_FRAME_WARN=2048
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_KERNEL is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_LATENCYTOP is not set
CONFIG_SYSCTL_SYSCALL_CHECK=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y

#
# Tracers
#
# CONFIG_SYSPROF_TRACER is not set
# CONFIG_DYNAMIC_PRINTK_DEBUG 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_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

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
CONFIG_CRYPTO_FIPS=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_GF128MUL=y
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_CRYPTD=y
CONFIG_CRYPTO_AUTHENC=y

#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=y
CONFIG_CRYPTO_GCM=y
CONFIG_CRYPTO_SEQIV=y

#
# Block modes
#
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_CTR=y
CONFIG_CRYPTO_CTS=y
CONFIG_CRYPTO_ECB=y
# CONFIG_CRYPTO_LRW is not set
CONFIG_CRYPTO_PCBC=y
# CONFIG_CRYPTO_XTS is not set

#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=y

#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
CONFIG_CRYPTO_CRC32C_INTEL=y
CONFIG_CRYPTO_MD4=y
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_MICHAEL_MIC=y
CONFIG_CRYPTO_RMD128=y
CONFIG_CRYPTO_RMD160=y
CONFIG_CRYPTO_RMD256=y
CONFIG_CRYPTO_RMD320=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
CONFIG_CRYPTO_TGR192=y
CONFIG_CRYPTO_WP512=y

#
# Ciphers
#
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_X86_64=y
CONFIG_CRYPTO_ANUBIS=y
CONFIG_CRYPTO_ARC4=y
CONFIG_CRYPTO_BLOWFISH=y
CONFIG_CRYPTO_CAMELLIA=y
CONFIG_CRYPTO_CAST5=y
CONFIG_CRYPTO_CAST6=y
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_FCRYPT=y
CONFIG_CRYPTO_KHAZAD=y
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_X86_64 is not set
CONFIG_CRYPTO_SEED=y
CONFIG_CRYPTO_SERPENT=y
CONFIG_CRYPTO_TEA=y
CONFIG_CRYPTO_TWOFISH=y
CONFIG_CRYPTO_TWOFISH_COMMON=y
CONFIG_CRYPTO_TWOFISH_X86_64=y

#
# Compression
#
CONFIG_CRYPTO_DEFLATE=y
CONFIG_CRYPTO_LZO=y

#
# Random Number Generation
#
CONFIG_CRYPTO_ANSI_CPRNG=y
# CONFIG_CRYPTO_HW is not set
CONFIG_HAVE_KVM=y
# CONFIG_VIRTUALIZATION is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_CRC_CCITT=y
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
CONFIG_CRC_ITU_T=y
CONFIG_CRC32=y
CONFIG_CRC7=y
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=y
CONFIG_TEXTSEARCH_BM=y
CONFIG_TEXTSEARCH_FSM=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: [Xen-devel] Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Sven Köhler]

[-- Attachment #1: Type: text/plain, Size: 759 bytes --]

Jeremy Fitzhardinge schrieb:
> Sven Köhler wrote:
>> Also asking the devel-list for help:
>>
>> Sven Köhler schrieb:
>>> Hi,
>>>
>>> I cannot execute any 32-bit executables. Same problem with 2.6.29-rc7.
>>>
>>> I compiled and linked them statically on another machine where they work
>>> just fine! But inside the xen domU, they just segfault:
>>>
>>>
>>> a.out[32093] general protection ip:f7f7042f sp:ffc6f2d4 error:0
>>>
>>>
>>> Is this a knows problem? CONFIG_IA32_EMULATION is turned on!
> 
> Hm, it works for me.  Can you give more detail about what you're trying 
> to run, the kernel .config and the distro?  dmesg output would have some 
> clues too.

xm dmesg shows nothing.

A full dmesg of the domU kernel is attached.


[-- Attachment #2: fulldmesg.txt --]
[-- Type: text/plain, Size: 8934 bytes --]

Mar 13 13:09:49 xen-sk1 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Mar 13 13:09:49 xen-sk1 kernel: Cannot find map file.
Mar 13 13:09:49 xen-sk1 kernel: Linux version 2.6.28.7 (root@xen-host.dnsalias.com) (gcc version 4.1.2 (Gentoo 4.1.2)) #7 Fri Mar 13 13:08:54 CET 2009
Mar 13 13:09:49 xen-sk1 kernel: Command line: root=/dev/xvda1 ro
Mar 13 13:09:49 xen-sk1 kernel: KERNEL supported cpus:
Mar 13 13:09:49 xen-sk1 kernel:   Intel GenuineIntel
Mar 13 13:09:49 xen-sk1 kernel:   AMD AuthenticAMD
Mar 13 13:09:49 xen-sk1 kernel:   Centaur CentaurHauls
Mar 13 13:09:49 xen-sk1 kernel: BIOS-provided physical RAM map:
Mar 13 13:09:49 xen-sk1 kernel:  Xen: 0000000000000000 - 00000000000a0000 (usable)
Mar 13 13:09:49 xen-sk1 kernel:  Xen: 00000000000a0000 - 0000000000100000 (reserved)
Mar 13 13:09:49 xen-sk1 kernel:  Xen: 0000000000100000 - 00000000007c6000 (usable)
Mar 13 13:09:49 xen-sk1 kernel:  Xen: 00000000007c6000 - 00000000008a0000 (reserved)
Mar 13 13:09:49 xen-sk1 kernel:  Xen: 00000000008a0000 - 000000001ae00000 (usable)
Mar 13 13:09:49 xen-sk1 kernel: DMI not present or invalid.
Mar 13 13:09:49 xen-sk1 kernel: last_pfn = 0x1ae00 max_arch_pfn = 0x3ffffffff
Mar 13 13:09:49 xen-sk1 kernel: init_memory_mapping: 0000000000000000-000000001ae00000
Mar 13 13:09:49 xen-sk1 kernel: last_map_addr: 1ae00000 end: 1ae00000
Mar 13 13:09:49 xen-sk1 kernel: (4 early reservations) ==> bootmem [0000000000 - 001ae00000]
Mar 13 13:09:49 xen-sk1 kernel:   #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
Mar 13 13:09:49 xen-sk1 kernel:   #1 [00008a0000 - 00008a9000]   XEN PAGETABLES ==> [00008a0000 - 00008a9000]
Mar 13 13:09:49 xen-sk1 kernel:   #2 [0000200000 - 00007c5468]    TEXT DATA BSS ==> [0000200000 - 00007c5468]
Mar 13 13:09:49 xen-sk1 kernel:   #3 [0000100000 - 00001cd000]          PGTABLE ==> [0000100000 - 00001cd000]
Mar 13 13:09:49 xen-sk1 kernel: Zone PFN ranges:
Mar 13 13:09:49 xen-sk1 kernel:   DMA      0x00000000 -> 0x00001000
Mar 13 13:09:49 xen-sk1 kernel:   DMA32    0x00001000 -> 0x00100000
Mar 13 13:09:49 xen-sk1 kernel:   Normal   0x00100000 -> 0x00100000
Mar 13 13:09:49 xen-sk1 kernel: Movable zone start PFN for each node
Mar 13 13:09:49 xen-sk1 kernel: early_node_map[3] active PFN ranges
Mar 13 13:09:49 xen-sk1 kernel:     0: 0x00000000 -> 0x000000a0
Mar 13 13:09:49 xen-sk1 kernel:     0: 0x00000100 -> 0x000007c6
Mar 13 13:09:49 xen-sk1 kernel:     0: 0x000008a0 -> 0x0001ae00
Mar 13 13:09:49 xen-sk1 kernel: No local APIC present
Mar 13 13:09:49 xen-sk1 kernel: Allocating PCI resources starting at 20000000 (gap: 1ae00000:e5200000)
Mar 13 13:09:49 xen-sk1 kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 106569
Mar 13 13:09:49 xen-sk1 kernel: Kernel command line: root=/dev/xvda1 ro
Mar 13 13:09:49 xen-sk1 kernel: Initializing CPU#0
Mar 13 13:09:49 xen-sk1 kernel: PID hash table entries: 2048 (order: 11, 16384 bytes)
Mar 13 13:09:49 xen-sk1 kernel: Detected 2399.726 MHz processor.
Mar 13 13:09:49 xen-sk1 kernel: Console: colour dummy device 80x25
Mar 13 13:09:49 xen-sk1 kernel: console [tty0] enabled
Mar 13 13:09:49 xen-sk1 kernel: console [hvc0] enabled
Mar 13 13:09:49 xen-sk1 kernel: Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Mar 13 13:09:49 xen-sk1 kernel: Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Mar 13 13:09:49 xen-sk1 kernel: Memory: 423588k/440320k available (3176k kernel code, 1256k absent, 14908k reserved, 1836k data, 272k init)
Mar 13 13:09:49 xen-sk1 kernel: installing Xen timer for CPU 0
Mar 13 13:09:49 xen-sk1 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4799.45 BogoMIPS (lpj=23997260)
Mar 13 13:09:49 xen-sk1 kernel: Mount-cache hash table entries: 256
Mar 13 13:09:49 xen-sk1 kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
Mar 13 13:09:49 xen-sk1 kernel: CPU: L2 Cache: 512K (64 bytes/line)
Mar 13 13:09:49 xen-sk1 kernel: CPU: AMD Athlon(tm) 64 Processor 3800+ stepping 02
Mar 13 13:09:49 xen-sk1 kernel: Apic disabled by BIOS
Mar 13 13:09:49 xen-sk1 kernel: net_namespace: 888 bytes
Mar 13 13:09:49 xen-sk1 kernel: Booting paravirtualized kernel on Xen
Mar 13 13:09:49 xen-sk1 kernel: Xen version: 3.3.0 (preserve-AD)
Mar 13 13:09:49 xen-sk1 kernel: Grant table initialized
Mar 13 13:09:49 xen-sk1 kernel: NET: Registered protocol family 16
Mar 13 13:09:49 xen-sk1 kernel: NET: Registered protocol family 2
Mar 13 13:09:49 xen-sk1 kernel: IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
Mar 13 13:09:49 xen-sk1 kernel: TCP established hash table entries: 16384 (order: 6, 262144 bytes)
Mar 13 13:09:49 xen-sk1 kernel: TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
Mar 13 13:09:49 xen-sk1 kernel: TCP: Hash tables configured (established 16384 bind 16384)
Mar 13 13:09:49 xen-sk1 kernel: TCP reno registered
Mar 13 13:09:49 xen-sk1 kernel: NET: Registered protocol family 1
Mar 13 13:09:49 xen-sk1 kernel: platform rtc_cmos: registered platform RTC device (no PNP device found)
Mar 13 13:09:49 xen-sk1 kernel: 00000000: 00 01 02 03 04 05 06 07 08 08 08 08 08 08 08 08 
Mar 13 13:09:49 xen-sk1 kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Mar 13 13:09:49 xen-sk1 kernel: fuse init (API version 7.10)
Mar 13 13:09:49 xen-sk1 kernel: msgmni has been set to 828
Mar 13 13:09:49 xen-sk1 kernel: alg: No test for cipher_null (cipher_null-generic)
Mar 13 13:09:49 xen-sk1 kernel: alg: No test for digest_null (digest_null-generic)
Mar 13 13:09:49 xen-sk1 kernel: alg: No test for compress_null (compress_null-generic)
Mar 13 13:09:49 xen-sk1 kernel: alg: No test for fcrypt (fcrypt-generic)
Mar 13 13:09:49 xen-sk1 kernel: alg: No test for stdrng (krng)
Mar 13 13:09:49 xen-sk1 kernel: alg: No test for stdrng (ansi_cprng)
Mar 13 13:09:49 xen-sk1 kernel: io scheduler noop registered
Mar 13 13:09:49 xen-sk1 kernel: io scheduler anticipatory registered
Mar 13 13:09:49 xen-sk1 kernel: io scheduler deadline registered
Mar 13 13:09:49 xen-sk1 kernel: io scheduler cfq registered (default)
Mar 13 13:09:49 xen-sk1 kernel: Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
Mar 13 13:09:49 xen-sk1 kernel: Hangcheck: Using get_cycles().
Mar 13 13:09:49 xen-sk1 kernel: loop: module loaded
Mar 13 13:09:49 xen-sk1 kernel: PPP generic driver version 2.4.2
Mar 13 13:09:49 xen-sk1 kernel: PPP Deflate Compression module registered
Mar 13 13:09:49 xen-sk1 kernel: PPP BSD Compression module registered
Mar 13 13:09:49 xen-sk1 kernel: Initialising Xen virtual ethernet driver.
Mar 13 13:09:49 xen-sk1 kernel: blkfront: xvda1: barriers enabled
Mar 13 13:09:49 xen-sk1 kernel: blkfront: xvda2: barriers enabled
Mar 13 13:09:49 xen-sk1 kernel: tun: Universal TUN/TAP device driver, 1.6
Mar 13 13:09:49 xen-sk1 kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Mar 13 13:09:49 xen-sk1 kernel: mice: PS/2 mouse device common for all mice
Mar 13 13:09:49 xen-sk1 kernel: device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
Mar 13 13:09:49 xen-sk1 kernel: Netfilter messages via NETLINK v0.30.
Mar 13 13:09:49 xen-sk1 kernel: nf_conntrack version 0.5.0 (3440 buckets, 13760 max)
Mar 13 13:09:49 xen-sk1 kernel: CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
Mar 13 13:09:49 xen-sk1 kernel: nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack module option or
Mar 13 13:09:49 xen-sk1 kernel: sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
Mar 13 13:09:49 xen-sk1 kernel: ctnetlink v0.93: registering with nfnetlink.
Mar 13 13:09:49 xen-sk1 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Mar 13 13:09:49 xen-sk1 kernel: arp_tables: (C) 2002 David S. Miller
Mar 13 13:09:49 xen-sk1 kernel: TCP cubic registered
Mar 13 13:09:49 xen-sk1 kernel: NET: Registered protocol family 17
Mar 13 13:09:49 xen-sk1 kernel: Bridge firewalling registered
Mar 13 13:09:49 xen-sk1 kernel: Ebtables v2.0 registered
Mar 13 13:09:49 xen-sk1 kernel: RPC: Registered udp transport module.
Mar 13 13:09:49 xen-sk1 kernel: RPC: Registered tcp transport module.
Mar 13 13:09:49 xen-sk1 kernel: XENBUS: Device with no driver: device/console/0
Mar 13 13:09:49 xen-sk1 kernel: kjournald starting.  Commit interval 5 seconds
Mar 13 13:09:49 xen-sk1 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Mar 13 13:09:49 xen-sk1 kernel: VFS: Mounted root (ext3 filesystem) readonly.
Mar 13 13:09:49 xen-sk1 kernel: Freeing unused kernel memory: 272k freed
Mar 13 13:09:49 xen-sk1 kernel: EXT3 FS on xvda1, internal journal
Mar 13 13:09:49 xen-sk1 kernel: Adding 995988k swap on /dev/xvda2.  Priority:-1 extents:1 across:995988k
Mar 13 17:20:12 xen-sk1 kernel: a.out[1792] general protection ip:f7fd942f sp:ffed6934 error:0
Mar 14 03:10:59 xen-sk1 syslogd 1.4.1: restart.
Mar 14 10:06:40 xen-sk1 kernel: a.out[6030] general protection ip:f7ffa42f sp:ff8f9354 error:0

[-- Attachment #3: Type: text/plain, Size: 137 bytes --]

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

Sven Köhler wrote:
> Jeremy Fitzhardinge schrieb:
>> Jeremy Fitzhardinge wrote:
>>> Sven Köhler wrote:
>>>> Also asking the devel-list for help:
>>>>
>>>> Sven Köhler schrieb:
>>>>> Hi,
>>>>>
>>>>> I cannot execute any 32-bit executables. Same problem with 
>>>>> 2.6.29-rc7.
>>>>>
>>>>> I compiled and linked them statically on another machine where 
>>>>> they work
>>>>> just fine! But inside the xen domU, they just segfault:
>>>>>
>>>>>
>>>>> a.out[32093] general protection ip:f7f7042f sp:ffc6f2d4 error:0
>>>>>
>>>>>
>>>>> Is this a knows problem? CONFIG_IA32_EMULATION is turned on!
>>>
>>> Hm, it works for me.  Can you give more detail about what you're 
>>> trying to run, the kernel .config and the distro?  dmesg output 
>>> would have some clues too. 
>>
>> Oh, and what's the CPU?  AMD?
>
> The host is running Xen version 3.3.0.
> The host CPU is:
>
> # cat /proc/cpuinfo
> processor    : 0
> vendor_id    : AuthenticAMD
> cpu family    : 15
> model        : 47
> model name    : AMD Athlon(tm) 64 Processor 3800+
> stepping    : 2
> cpu MHz        : 2399.822
> cache size    : 512 KB
> fpu        : yes
> fpu_exception    : yes
> cpuid level    : 1
> wp        : yes
> flags        : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush mmx 
> fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm
> bogomips    : 4800.70
> TLB size    : 1024 4K pages
> clflush size    : 64
> cache_alignment    : 64
> address sizes    : 40 bits physical, 48 bits virtual
> power management: ts fid vid ttp tm stc
>
> The kernel is vanilla (except for the xen/blkfront: use blk_rq_map_sg 
> to generate ring entries patch). The config of my 2.6.28.7 is attached.
>
> The program I'm trying to run is:
> $ cat test.c
> #include <stdio.h>
>
> int main(void)
> {
>   printf("Hallo Welt!\n");
>   return 0;
> }
>
> I compiled it with "gcc --static test.c" on other box where the 
> program runs fine and copied the output to my domU. I checked with 
> ldd, that it really isn't a dynamic executable.
>
> The dmesg output on the domU is this mysterious:
> a.out[32093] general protection ip:f7f7042f sp:ffc6f2d4 error:0
>
> The line appears each time, that the program segfaults.

Has it ever worked?  If so, what kernel version did it stop working at?  
Does it fail with all 32-bit executables or just your "hello world"?

Can you get a coredump from the fault and see what the faulting 
instruction was?

    J

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Sven Köhler]

[-- Attachment #1.1: Type: text/plain, Size: 876 bytes --]

Jeremy Fitzhardinge schrieb:
> Has it ever worked?  If so, what kernel version did it stop working at? 
> Does it fail with all 32-bit executables or just your "hello world"?

I discovered the bug as I tried to compile glibc inside the domU.
glibc's configure tries to compile a test program to determine the
sizeof the long datatype or something simple like that. So at least this
is another program that fails.

I did quick test, whether the empty program (just a main with return 0;
in it) segfaults - but it doesn't segfault. The moment I add a printf,
it segfaults again.

> Can you get a coredump from the fault and see what the faulting
> instruction was?

How do I do that?
Sorry for the stupid question, but unfortunatly this is beyond my
knowledge of the tooldchain :-(

I didn't find any automatically generated file.


Regards,
  Sven



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Sven Köhler]

[-- Attachment #1.1: Type: text/plain, Size: 431 bytes --]

Jeremy Fitzhardinge schrieb:
> Has it ever worked?  If so, what kernel version did it stop working at? 

I've just tried a good old non-pv_ops 2.6.18 kernel:

I ran the same binary file, that segfaults on 2.6.28.7.
It runs just fine on 2.6.18.

I haven't tested any other pc_ops kernel version. I'm not sure, that it
ever worked with these kernel. Which was the first kernel version, that
had domU support? 2.6.28.0 ?


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: [Xen-users] Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 1252 bytes --]



--- On Sun, 3/15/09, Sven Köhler <sven.koehler@gmail.com> wrote:
From: Sven Köhler <sven.koehler@gmail.com>
Subject: [Xen-users] Re: [Xen-devel] Re: 2.6.28.7 domU: 32-bit emulation seems to be broken
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Date: Sunday, March 15, 2009, 8:24 AM

Jeremy Fitzhardinge schrieb:
> Has it ever worked?  If so, what kernel version did it stop working at? 

I've just tried a good old non-pv_ops 2.6.18 kernel:

I ran the same binary file, that segfaults on 2.6.28.7.
It runs just fine on 2.6.18.

I haven't tested any other pc_ops kernel version. I'm not sure, that it
ever worked with these kernel. Which was the first kernel version, that
had domU support? 2.6.28.0 ?
******************************************************
Yes, 2.6.28 has pvops support for DomU. It's for sure
But, i believe 2.6.27 as well . That's version
of Ubuntu Intrepid (8.10) Server.
View:-
http://wiki.xensource.com/xenwiki/XenParavirtOps
******************************************************


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users


      

[-- Attachment #1.2: Type: text/html, Size: 1605 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

Sven Köhler wrote:
>> Can you get a coredump from the fault and see what the faulting
>> instruction was?
>>     
>
> How do I do that?
> Sorry for the stupid question, but unfortunatly this is beyond my
> knowledge of the tooldchain :-(

$ ulimit -c unlimited
$ ./a.out
Segmentation Fault (core dumped)
$ ls core.*
core.XXXXX
$ gdb ./a.out core.*
[...]
(gdb) x/i $eip-2

It will help to compile your a.out with -g.

	J

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

Sven Köhler wrote:
> I haven't tested any other pc_ops kernel version. I'm not sure, that it
> ever worked with these kernel. Which was the first kernel version, that
> had domU support? 2.6.28.0 ?
>   

2.6.27 was the first version with x86-64 domU support.

    J

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

Sven Köhler wrote:
> Jeremy Fitzhardinge schrieb:
>   
>> Has it ever worked?  If so, what kernel version did it stop working at? 
>>     
>
> I've just tried a good old non-pv_ops 2.6.18 kernel:
>
> I ran the same binary file, that segfaults on 2.6.28.7.
> It runs just fine on 2.6.18.
>
> I haven't tested any other pc_ops kernel version. I'm not sure, that it
> ever worked with these kernel. Which was the first kernel version, that
> had domU support? 2.6.28.0 ?
>
>   
Does this patch help?

diff --git a/arch/x86/ia32/ia32entry.S b/arch/x86/ia32/ia32entry.S
index e4baa06..3ea8299 100644
--- a/arch/x86/ia32/ia32entry.S
+++ b/arch/x86/ia32/ia32entry.S
@@ -400,7 +400,6 @@ ENTRY(ia32_syscall)
 	/*CFI_REL_OFFSET	rflags,EFLAGS-RIP*/
 	/*CFI_REL_OFFSET	cs,CS-RIP*/
 	CFI_REL_OFFSET	rip,RIP-RIP
-	PARAVIRT_ADJUST_EXCEPTION_FRAME
 	SWAPGS
 	/*
 	 * No need to follow this irqs on/off section: the syscall

	J

Re: [Xen-devel] Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Sven Köhler]

[-- Attachment #1.1: Type: text/plain, Size: 1065 bytes --]

Jeremy Fitzhardinge schrieb:
> Sven Köhler wrote:
>> Jeremy Fitzhardinge schrieb:
>>  
>>> Has it ever worked?  If so, what kernel version did it stop working
>>> at?     
>>
>> I've just tried a good old non-pv_ops 2.6.18 kernel:
>>
>> I ran the same binary file, that segfaults on 2.6.28.7.
>> It runs just fine on 2.6.18.
>>
>> I haven't tested any other pc_ops kernel version. I'm not sure, that it
>> ever worked with these kernel. Which was the first kernel version, that
>> had domU support? 2.6.28.0 ?
>>
>>   
> Does this patch help?
> 
> diff --git a/arch/x86/ia32/ia32entry.S b/arch/x86/ia32/ia32entry.S
> index e4baa06..3ea8299 100644
> --- a/arch/x86/ia32/ia32entry.S
> +++ b/arch/x86/ia32/ia32entry.S
> @@ -400,7 +400,6 @@ ENTRY(ia32_syscall)
>     /*CFI_REL_OFFSET    rflags,EFLAGS-RIP*/
>     /*CFI_REL_OFFSET    cs,CS-RIP*/
>     CFI_REL_OFFSET    rip,RIP-RIP
> -    PARAVIRT_ADJUST_EXCEPTION_FRAME
>     SWAPGS
>     /*
>      * No need to follow this irqs on/off section: the syscall

No, still segfaults :-(



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

[-- Attachment #2: Type: text/plain, Size: 137 bytes --]

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Sven Köhler]

[-- Attachment #1.1: Type: text/plain, Size: 1198 bytes --]

Jeremy Fitzhardinge schrieb:
> Sven Köhler wrote:
>>> Can you get a coredump from the fault and see what the faulting
>>> instruction was?
>>>     
>>
>> How do I do that?
>> Sorry for the stupid question, but unfortunatly this is beyond my
>> knowledge of the tooldchain :-(
> 
> $ ulimit -c unlimited
> $ ./a.out
> Segmentation Fault (core dumped)
> $ ls core.*
> core.XXXXX
> $ gdb ./a.out core.*
> [...]
> (gdb) x/i $eip-2
> 
> It will help to compile your a.out with -g.

# ulimit -c unlimited
# ./a.out
Segmentation fault (core dumped)
# gdb a.out core
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu"...
Core was generated by `./a.out'.
Program terminated with signal 11, Segmentation fault.
[New process 13256]
#0  0xf7f3642f in __kernel_vsyscall ()
(gdb) x/i $eip-2
0xf7f3642d <__kernel_vsyscall+13>:      jmp    0x25f4278f
(gdb)



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

Sven Köhler wrote:
> Jeremy Fitzhardinge schrieb:
>   
>> Sven Köhler wrote:
>>     
>>>> Can you get a coredump from the fault and see what the faulting
>>>> instruction was?
>>>>     
>>>>         
>>> How do I do that?
>>> Sorry for the stupid question, but unfortunatly this is beyond my
>>> knowledge of the tooldchain :-(
>>>       
>> $ ulimit -c unlimited
>> $ ./a.out
>> Segmentation Fault (core dumped)
>> $ ls core.*
>> core.XXXXX
>> $ gdb ./a.out core.*
>> [...]
>> (gdb) x/i $eip-2
>>
>> It will help to compile your a.out with -g.
>>     
>
> # ulimit -c unlimited
> # ./a.out
> Segmentation fault (core dumped)
> # gdb a.out core
> GNU gdb 6.8
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-pc-linux-gnu"...
> Core was generated by `./a.out'.
> Program terminated with signal 11, Segmentation fault.
> [New process 13256]
> #0  0xf7f3642f in __kernel_vsyscall ()
> (gdb) x/i $eip-2
> 0xf7f3642d <__kernel_vsyscall+13>:      jmp    0x25f4278f
> (gdb)
>   

Hm.  How about "x/30i __kernel_vsyscall"?

    J

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

Sven Köhler wrote:
> (gdb) x/i $eip-2
> 0xf7f3642d <__kernel_vsyscall+13>:      jmp    0x25f4278f
> (gdb)

Oh, and "x/i <whatever appears after ip: in the kernel dmesg>"

    J

Re: [Xen-devel] Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Sven Köhler]

Jeremy Fitzhardinge schrieb:
> Hm.  How about "x/30i __kernel_vsyscall"?

# export LANG=C
# ulimit -c unlimited
# ./a.out
Segmentation fault (core dumped)
# dmesg|grep "ip:"
a.out[18031] general protection ip:f7f4642f sp:ff943d74 error:0
a.out[18038] general protection ip:f7f0042f sp:ff8fd534 error:0
# gdb ./a.out core
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu"...
Core was generated by `./a.out'.
Program terminated with signal 11, Segmentation fault.
[New process 18038]
#0  0xf7f0042f in __kernel_vsyscall ()
(gdb) x/i f7f0042f
No symbol "f7f0042f" in current context.
(gdb) x/i $eip-2
0xf7f0042d <__kernel_vsyscall+13>:	jmp    0x25f0c78f
(gdb) x/30i __kernel_vsyscall
0xf7f00420 <__kernel_vsyscall>:	push   %ebp
0xf7f00421 <__kernel_vsyscall+1>:	mov    %ecx,%ebp
0xf7f00423 <__kernel_vsyscall+3>:	syscall
0xf7f00425 <__kernel_vsyscall+5>:	mov    $0x2b,%ecx
0xf7f0042a <__kernel_vsyscall+10>:	mov    %ecx,%ss
0xf7f0042c <__kernel_vsyscall+12>:	mov    %ebp,%ecx
0xf7f0042e <__kernel_vsyscall+14>:	pop    %ebp
0xf7f0042f <__kernel_vsyscall+15>:	ret
0xf7f00430:	add    %ch,(%esi)
0xf7f00432:	jae    0xf7f0049c
0xf7f00434:	jae    0xf7f004aa
0xf7f00436:	jb     0xf7f004ac
0xf7f00438:	popa
0xf7f00439:	bound  %eax,(%eax)
0xf7f0043b:	cs
0xf7f0043c:	push   $0x687361
0xf7f00441:	cs
0xf7f00442:	fs
0xf7f00443:	jns    0xf7f004b3
0xf7f00445:	jae    0xf7f004c0
0xf7f00447:	insl   (%dx),%es:(%edi)
0xf7f00448:	add    %ch,(%esi)
0xf7f0044a:	fs
---Type <return> to continue, or q <return> to quit---
0xf7f0044b:	jns    0xf7f004bb
0xf7f0044d:	jae    0xf7f004c3
0xf7f0044f:	jb     0xf7f00451
0xf7f00451:	addr16 outsb %cs:(%si),(%dx)
0xf7f00454:	jne    0xf7f00484
0xf7f00456:	jbe    0xf7f004bd
0xf7f00458:	jb     0xf7f004cd
(gdb)

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Sven Köhler]

Sven Köhler schrieb:
> (gdb) x/i f7f0042f
> No symbol "f7f0042f" in current context.

Doh! Silly me. Here's the correct thing:

(gdb) x/i 0xf7f0042f
0xf7f0042f <__kernel_vsyscall+15>:	ret

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

Sven Köhler wrote:
> Jeremy Fitzhardinge schrieb:
>   
>> Sven Köhler wrote:
>>     
>>> Jeremy Fitzhardinge schrieb:
>>>  
>>>       
>>>> Has it ever worked?  If so, what kernel version did it stop working
>>>> at?     
>>>>         
>>> I've just tried a good old non-pv_ops 2.6.18 kernel:
>>>
>>> I ran the same binary file, that segfaults on 2.6.28.7.
>>> It runs just fine on 2.6.18.
>>>
>>> I haven't tested any other pc_ops kernel version. I'm not sure, that it
>>> ever worked with these kernel. Which was the first kernel version, that
>>> had domU support? 2.6.28.0 ?
>>>
>>>   
>>>       
>> Does this patch help?
>>
>> diff --git a/arch/x86/ia32/ia32entry.S b/arch/x86/ia32/ia32entry.S
>> index e4baa06..3ea8299 100644
>> --- a/arch/x86/ia32/ia32entry.S
>> +++ b/arch/x86/ia32/ia32entry.S
>> @@ -400,7 +400,6 @@ ENTRY(ia32_syscall)
>>     /*CFI_REL_OFFSET    rflags,EFLAGS-RIP*/
>>     /*CFI_REL_OFFSET    cs,CS-RIP*/
>>     CFI_REL_OFFSET    rip,RIP-RIP
>> -    PARAVIRT_ADJUST_EXCEPTION_FRAME
>>     SWAPGS
>>     /*
>>      * No need to follow this irqs on/off section: the syscall
>>     
>
> No, still segfaults :-(
>   

Do you have auditing enabled?

    J

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

Jeremy Fitzhardinge wrote:
>
> Do you have auditing enabled?
(No)

    J

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Sven Köhler]

Jeremy Fitzhardinge schrieb:
> Jeremy Fitzhardinge wrote:
>>
>> Do you have auditing enabled?
> (No)

You answered yourself, right?
(yes, CONFIG_AUDIT is disabled)

Can I supply you with any further information?

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

Sven Köhler wrote:
> Jeremy Fitzhardinge schrieb:
>> Jeremy Fitzhardinge wrote:
>>>
>>> Do you have auditing enabled?
>> (No)
>
> You answered yourself, right?
> (yes, CONFIG_AUDIT is disabled)
>
> Can I supply you with any further information?

I need to find/set up an AMD system to try to repro it I think.  I think 
the problem is actually the return from the syscall, rather than the 
syscall entry itself.  What happens if you run the program under either 
strace or gdb?

    J

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Sven Köhler]

[-- Attachment #1.1: Type: text/plain, Size: 1263 bytes --]

Jeremy Fitzhardinge schrieb:
> Sven Köhler wrote:
>> Jeremy Fitzhardinge schrieb:
>>> Jeremy Fitzhardinge wrote:
>>>>
>>>> Do you have auditing enabled?
>>> (No)
>>
>> You answered yourself, right?
>> (yes, CONFIG_AUDIT is disabled)
>>
>> Can I supply you with any further information?
> 
> I need to find/set up an AMD system to try to repro it I think.  I think
> the problem is actually the return from the syscall, rather than the
> syscall entry itself.  What happens if you run the program under either
> strace or gdb?

The program just works:

# strace ./a.out
execve("./a.out", ["./a.out"], [/* 24 vars */]) = 0
[ Process PID=8968 runs in 32 bit mode. ]
uname({sys="Linux", node="xen-to1", ...}) = 0
brk(0)                                  = 0x80c3000
brk(0x80c3cb0)                          = 0x80c3cb0
set_thread_area(0xffa5182c)             = 0
brk(0x80e4cb0)                          = 0x80e4cb0
brk(0x80e5000)                          = 0x80e5000
fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xfffffffff7f51000
write(1, "Hallo Welt!\n"..., 12Hallo Welt!
)        = 12
exit_group(0)                           = ?


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

Sven Köhler wrote:
> Jeremy Fitzhardinge schrieb:
>   
>> Sven Köhler wrote:
>>     
>>> Jeremy Fitzhardinge schrieb:
>>>       
>>>> Jeremy Fitzhardinge wrote:
>>>>         
>>>>> Do you have auditing enabled?
>>>>>           
>>>> (No)
>>>>         
>>> You answered yourself, right?
>>> (yes, CONFIG_AUDIT is disabled)
>>>
>>> Can I supply you with any further information?
>>>       
>> I need to find/set up an AMD system to try to repro it I think.  I think
>> the problem is actually the return from the syscall, rather than the
>> syscall entry itself.  What happens if you run the program under either
>> strace or gdb?
>>     
>
> The program just works:
>
> # strace ./a.out
> execve("./a.out", ["./a.out"], [/* 24 vars */]) = 0
> [ Process PID=8968 runs in 32 bit mode. ]
> uname({sys="Linux", node="xen-to1", ...}) = 0
> brk(0)                                  = 0x80c3000
> brk(0x80c3cb0)                          = 0x80c3cb0
> set_thread_area(0xffa5182c)             = 0
> brk(0x80e4cb0)                          = 0x80e4cb0
> brk(0x80e5000)                          = 0x80e5000
> fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0xfffffffff7f51000
> write(1, "Hallo Welt!\n"..., 12Hallo Welt!
> )        = 12
> exit_group(0)                           = ?
>   

OK, that confirms that its sysret32 that's failing.  vdso32=0 on the 
kernel command line should be the workaround until we've got a proper fix.

    J

Re: [Xen-devel] Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Sven Köhler]

Jeremy Fitzhardinge schrieb:
> OK, that confirms that its sysret32 that's failing.  vdso32=0 on the 
> kernel command line should be the workaround until we've got a proper fix.

vdso32=0 works. Thank you for your help!

But i wonder: what's the drawback of this workaround? Performance loss? 
Or something more dramatic?


Regards,
   Sven

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

Sven Köhler wrote:
> Jeremy Fitzhardinge schrieb:
>> OK, that confirms that its sysret32 that's failing.  vdso32=0 on the 
>> kernel command line should be the workaround until we've got a proper 
>> fix.
>
> vdso32=0 works. Thank you for your help!
>
> But i wonder: what's the drawback of this workaround? Performance 
> loss? Or something more dramatic? 

Slight performance loss, probably only measurable with micro-benchmarks.

    J

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Milan Holzäpfel]

[-- Attachment #1.1: Type: text/plain, Size: 840 bytes --]

On Tue, 17 Mar 2009 09:52:59 -0700
Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> Sven Köhler wrote:
> > Jeremy Fitzhardinge schrieb:
> > 
> >> I need to find/set up an AMD system to try to repro it I think.  I think
> >> the problem is actually the return from the syscall, rather than the
> >> syscall entry itself.  What happens if you run the program under either
> >> strace or gdb?
> >>     
> >
> > The program just works:
> >
> > # strace ./a.out
> > [...]
> 
> OK, that confirms that its sysret32 that's failing.  vdso32=0 on the 
> kernel command line should be the workaround until we've got a proper fix.

Hi, 

I still notice this problem with vanilla 2.6.30.4 domU under Xen 3.3.2
(32 bit binaries on a 64 bit domU kernel segfault, AMD CPU).  vdso32=0
still helps. 

Any news? 

Regards,
Milan 

[-- Attachment #1.2: Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Christoph Egger]

On Monday 10 August 2009 13:21:21 Milan Holzäpfel wrote:
> On Tue, 17 Mar 2009 09:52:59 -0700
>
> Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> > Sven Köhler wrote:
> > > Jeremy Fitzhardinge schrieb:
> > >> I need to find/set up an AMD system to try to repro it I think.  I
> > >> think the problem is actually the return from the syscall, rather than
> > >> the syscall entry itself.  What happens if you run the program under
> > >> either strace or gdb?
> > >
> > > The program just works:
> > >
> > > # strace ./a.out
> > > [...]
> >
> > OK, that confirms that its sysret32 that's failing.  vdso32=0 on the
> > kernel command line should be the workaround until we've got a proper
> > fix.
>
> Hi,
>
> I still notice this problem with vanilla 2.6.30.4 domU under Xen 3.3.2
> (32 bit binaries on a 64 bit domU kernel segfault, AMD CPU).  vdso32=0
> still helps.
>
> Any news?

What does Linux use w/o vdso32=0 on your box ? Does it use sysenter, syscall
or int 0x80 ?

Do you boot the DomU directly or does this happen after migration from
an Intel box ?

Christoph


-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Milan Holzäpfel]

[-- Attachment #1.1: Type: text/plain, Size: 4365 bytes --]

On Mon, 10 Aug 2009 14:59:31 +0200
Christoph Egger <Christoph.Egger@amd.com> wrote:

> On Monday 10 August 2009 13:21:21 Milan Holzäpfel wrote:
> > On Tue, 17 Mar 2009 09:52:59 -0700
> >
> > Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> > > Sven Köhler wrote:
> > > > Jeremy Fitzhardinge schrieb:
> > > >> I need to find/set up an AMD system to try to repro it I think.  I
> > > >> think the problem is actually the return from the syscall, rather than
> > > >> the syscall entry itself.  What happens if you run the program under
> > > >> either strace or gdb?
> > > >
> > > > The program just works:
> > > >
> > > > # strace ./a.out
> > > > [...]
> > >
> > > OK, that confirms that its sysret32 that's failing.  vdso32=0 on the
> > > kernel command line should be the workaround until we've got a proper
> > > fix.
> >
> > Hi,
> >
> > I still notice this problem with vanilla 2.6.30.4 domU under Xen 3.3.2
> > (32 bit binaries on a 64 bit domU kernel segfault, AMD CPU).  vdso32=0
> > still helps.
> >
> > Any news?
> 
> What does Linux use w/o vdso32=0 on your box ? Does it use sysenter, syscall
> or int 0x80 ?

I'm not quite sure.  I collected the same gdb output as Sven Köhler did
in March, see below. 

> Do you boot the DomU directly or does this happen after migration from
> an Intel box ?

The DomU was booted directly on the AMD CPU, no migration was used. 

Here's the GDB output:

server64d ~ # uname -a
Linux server64d 2.6.30.4-9nfs #1 SMP Mon Aug 10 12:25:11 CEST 2009 x86_64 AMD Athlon(tm) X2 Dual Core Processor BE-2400 AuthenticAMD GNU/Linux
server64d ~ # cat test1.c 
#include <stdio.h>
int main() {
  printf("Hello, World\n");
}

server64d ~ # gcc -g -m32 test1.c -o test1
server64d ~ # ulimit -c unlimited
server64d ~ # rm -f core 
server64d ~ # ./test1
Segmentation fault (core dumped)
server64d ~ # dmesg | grep ip:
[  102.223656] test1[2313] general protection ip:ffffe42f sp:ffdb0dc0 error:0
[  265.468057] test1[2318] general protection ip:ffffe42f sp:ffec3880 error:0
[  758.153330] test1[11120] general protection ip:ffffe42f sp:ffe7ea20 error:0
[  791.662222] test1[11129] general protection ip:ffffe42f sp:ff9a5990 error:0
[ 1188.283930] test1[11136] general protection ip:ffffe42f sp:ffb06650 error:0
server64d ~ # gdb test1 core 
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu"...

warning: Can't read pathname for load map: Input/output error.
Loaded symbols for /root/test1
Reading symbols from /lib32/libc.so.6...done.
Loaded symbols for /lib32/libc.so.6
Reading symbols from /lib64/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Core was generated by `./test1'.
Program terminated with signal 11, Segmentation fault.
[New process 11136]
#0  0xffffe42f in __kernel_vsyscall ()
(gdb) x/i 0xffffe42f
0xffffe42f <__kernel_vsyscall+15>:	ret    
(gdb) x/i $eip-2
0xffffe42d <__kernel_vsyscall+13>:	jmp    0x2e00a78f
(gdb) x/30i __kernel_vsyscall
0xffffe420 <__kernel_vsyscall>:	push   %ebp
0xffffe421 <__kernel_vsyscall+1>:	mov    %ecx,%ebp
0xffffe423 <__kernel_vsyscall+3>:	syscall 
0xffffe425 <__kernel_vsyscall+5>:	mov    $0x2b,%ecx
0xffffe42a <__kernel_vsyscall+10>:	mov    %ecx,%ss
0xffffe42c <__kernel_vsyscall+12>:	mov    %ebp,%ecx
0xffffe42e <__kernel_vsyscall+14>:	pop    %ebp
0xffffe42f <__kernel_vsyscall+15>:	ret    
0xffffe430:	add    %ch,(%esi)
0xffffe432:	jae    0xffffe49c
0xffffe434:	jae    0xffffe4aa
0xffffe436:	jb     0xffffe4ac
0xffffe438:	popa   
0xffffe439:	bound  %eax,(%eax)
0xffffe43b:	cs
0xffffe43c:	push   $0x687361
0xffffe441:	cs
0xffffe442:	fs
0xffffe443:	jns    0xffffe4b3
0xffffe445:	jae    0xffffe4c0
0xffffe447:	insl   (%dx),%es:(%edi)
0xffffe448:	add    %ch,(%esi)
0xffffe44a:	fs
0xffffe44b:	jns    0xffffe4bb
0xffffe44d:	jae    0xffffe4c3
0xffffe44f:	jb     0xffffe451
0xffffe451:	addr16 outsb %cs:(%si),(%dx)
0xffffe454:	jne    0xffffe484
0xffffe456:	jbe    0xffffe4bd
0xffffe458:	jb     0xffffe4cd
(gdb) quit
server64d ~ # 


Regards,
Milan

[-- Attachment #1.2: Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge]

On 08/10/09 05:59, Christoph Egger wrote:
>> I still notice this problem with vanilla 2.6.30.4 domU under Xen 3.3.2
>> (32 bit binaries on a 64 bit domU kernel segfault, AMD CPU).  vdso32=0
>> still helps.
>>
>> Any news?
>>     
>
> What does Linux use w/o vdso32=0 on your box ? Does it use sysenter, syscall
> or int 0x80 ?
>
> Do you boot the DomU directly or does this happen after migration from
> an Intel box ?
>   

There appears to be a bug in the 64-bit xen_sysret32, which attempts to
take the sysret environment and turn it into an iret hypercall (since
iret is the only way to do a 64-bit kernel -> 32-bit user return).

I don't have an AMD test machine on hand, so I haven't had a chance to
work out what's actually failing.  I couldn't see anything wrong by
staring at the code, but that probably means I was either starting hard
at the bug, or looking right next to the bug...

Could you try looking at this?

    J