Hi,
I am trying to get X to work on Xen Dom0 running a custom 3.4.10 kernel. with a
Nvidia Gt220 card + 295.59 drivers.Although,the drivers get loaded and X
starts,but after some time its seems to get stuck in some kind of infinite loop
and starts taking up 100 % cpu. This is observed only when i boot up the machine
with the Xen hypervisor,otherwise X works well with out the hypervisor being
involved.
Is the Xen hypervisor which is acting up or is it the Nvidia drivers ? I dont
see anything suspicious in dmesg or Xorg.0.log,the only error i see is from kdm
in var log messages.
Os: Centos6.3
Xen hypervisor - 4.1.3
# Xorg -version
X.Org X Server 1.10.6Release Date: 2012-02-10X Protocol Version 11, Revision 0
# Grub title CentOS (3.4.10-custom2-Xen) root (hd0,0) kernel
/xen.gz dom0_mem=4096M iommu=on iommu=verbose module
/vmlinuz-3.4.10-custom2 ro root=/dev/mapper/vg_livecd-lv_root rd_NO_LUKS
LANG=en_US.UTF-8 rd_LVM_LV=vg_livecd/lv_swap rd_NO_MD
rd_LVM_LV=vg_livecd/lv_root SYSFONT=latarcyrheb-sun16 crashkernel=auto
KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet module
/initramfs-3.4.10-custom2.img
# /var/log/messages
ep 1 10:43:36 localhost acpid: client 24735[0:0] has disconnectedSep 1
10:43:36 localhost acpid: client connected from 25254[0:0]Sep 1 10:43:36
localhost acpid: 1 client rule loadedSep 1 10:43:53 localhost kdm[25248]: X
server startup timeout, terminatingSep 1 10:44:23 localhost kdm[25248]: X
server termination timeout, killingSep 1 10:44:33 localhost kdm[25248]: X
server is stuck in D state; leaving it aloneSep 1 10:44:33 localhost
kdm[25248]: X server for display :0 cannot be started, session disabled
# xm dmesg
(XEN) domain.c:655:d0 Attempt to change CR4 flags 00002660 -> 000026e0(XEN)
domain.c:655:d0 Attempt to change CR4 flags 00002660 -> 000026e0(XEN)
domain.c:655:d0 Attempt to change CR4 flags 00002660 -> 000026e0(XEN)
domain.c:655:d0 Attempt to change CR4 flags 00002660 -> 000026e0(XEN)
domain.c:655:d0 Attempt to change CR4 flags 00002660 -> 000026e0
# Dom0 Kernel config
# zgrep -i xen
/proc/config.gzCONFIG_XEN=yCONFIG_XEN_DOM0=yCONFIG_XEN_PRIVILEGED_GUEST=yCONFIG_XEN_PVHVM=yCONFIG_XEN_MAX_DOMAIN_MEMORY=500CONFIG_XEN_SAVE_RESTORE=y#
CONFIG_XEN_DEBUG_FS is not
setCONFIG_PCI_XEN=yCONFIG_XEN_PCIDEV_FRONTEND=yCONFIG_XEN_BLKDEV_FRONTEND=yCONFIG_XEN_BLKDEV_BACKEND=yCONFIG_NETXEN_NIC=mCONFIG_XEN_NETDEV_FRONTEND=yCONFIG_XEN_NETDEV_BACKEND=mCONFIG_INPUT_XEN_KBDDEV_FRONTEND=yCONFIG_HVC_XEN=yCONFIG_HVC_XEN_FRONTEND=y#
CONFIG_XEN_WDT is not setCONFIG_XEN_FBDEV_FRONTEND=y# Xen driver
supportCONFIG_XEN_BALLOON=y# CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is not
setCONFIG_XEN_SCRUB_PAGES=yCONFIG_XEN_DEV_EVTCHN=yCONFIG_XEN_BACKEND=yCONFIG_XENFS=yCONFIG_XEN_COMPAT_XENFS=yCONFIG_XEN_SYS_HYPERVISOR=yCONFIG_XEN_XENBUS_FRONTEND=yCONFIG_XEN_GNTDEV=yCONFIG_XEN_GRANT_DEV_ALLOC=mCONFIG_SWIOTLB_XEN=yCONFIG_XEN_PCIDEV_BACKEND=mCONFIG_XEN_PRIVCMD=y#
CONFIG_XEN_ACPI_PROCESSOR is not set
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
