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

[Xen-users] 回复: Re: Dom0's Booting problem on RedHat enterprise linux 7



Hi Mark,
    That's the kernel's configuration about Xen(cat .config | grep XEN). I think it's OK.


CONFIG_XEN=y
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_PVHVM=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=500
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
CONFIG_PCI_XEN=y
# CONFIG_XEN_PCIDEV_FRONTEND is not set
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_XEN_BLKDEV_BACKEND=m
CONFIG_NETXEN_NIC=m
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_XEN_NETDEV_BACKEND=m
CONFIG_INPUT_XEN_KBDDEV_FRONTEND=m
CONFIG_HVC_XEN=y
CONFIG_HVC_XEN_FRONTEND=y
CONFIG_XEN_WDT=m
# CONFIG_XEN_FBDEV_FRONTEND is not set
CONFIG_XEN_BALLOON=y
# CONFIG_XEN_SELFBALLOONING is not set
# CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is not set
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m
CONFIG_XEN_BACKEND=y
CONFIG_XENFS=m
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_XENBUS_FRONTEND=y
CONFIG_XEN_GNTDEV=y
# CONFIG_XEN_GRANT_DEV_ALLOC is not set
CONFIG_SWIOTLB_XEN=y
CONFIG_XEN_TMEM=m
CONFIG_XEN_PCIDEV_BACKEND=m
CONFIG_XEN_PRIVCMD=m
CONFIG_XEN_ACPI_PROCESSOR=m
# CONFIG_XEN_MCE_LOG is not set
CONFIG_XEN_HAVE_PVMMU=y



chengkunck@xxxxxxxxx
 
发件人: Kenneth
发送时间: 2014-11-13 11:56
收件人: Mark Pryor
抄送: xen-users
主题: Re: [Xen-users] Dom0's Booting problem on RedHat enterprise linux 7

Hi Mark,
    Thank you for the reply. I am sure of the dom0 support as I manually changed the config according to wiki.xen.org, I also added echo command to the grub entry to tell me if the three parts are correctly loaded. The problem is it hangs when I see 'starting authorization manager'. And after 30 minutes it is still there hanging.

This email is typed on my iPhone. I'd like to apologize for any mistake in it.

在 2014年11月13日,11:10,Mark Pryor <tlviewer@xxxxxxxxx> 写道:

Ken,

before you go to the trouble of building xen, make sure your desired kernel will support dom0.
grep XEN /boot/config-3.10*
if you don't return at least 35 entries from ^^, then that Redhat kernel does not support dom0. I know for a fact it does not, but convince yourself too.

There is another kernel you can use, but its not supported by RH. For more info, visit #xen on freenode.net

BTW, I happily use Xen built from source on CentOS 7, with kernel-ml 3.16.1 (elrepo), and systemd is enabled.


On Wednesday, November 12, 2014 4:42 AM, "chengkunck@xxxxxxxxx" <chengkunck@xxxxxxxxx> wrote:


Hi,
    I used to be working under Debian but recently I've moved on to Redhat. I compiled and installed Xen 4.4.1 on redhat linux 7 x64 with linux 3.1-.59 kernel. after that I add an entry in /boot/grub2/grub.cfg. I copied a default one and made some change, in which I wrote:

menuentry 'Xen 4.4.1, Red Hat Enterprise Linux Server (3.10.59) 7.0 (Maipo)' --class red --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-123.el7.x86_64-advanced-4a6ecbd4-e01b-4030-ab09-a43d5b6f63b5' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos6 --hint-efi=hd1,msdos6 --hint-baremetal=ahci1,msdos6 --hint='hd0,msdos6' 4a6ecbd4-e01b-4030-ab09-a43d5b6f63b5
else
search --no-floppy --fs-uuid --set=root 4a6ecbd4-e01b-4030-ab09-a43d5b6f63b5
fi
echo 'Loading Xen 4.4.1'
multiboot /boot/xen-4.4.1.gz placeholder dom0_mem=4096M dom0_max_vcpus=8 loglvl=all iommu=1
echo 'Loading Linux 3.10.59'
module /boot/vmlinuz-3.10.59 root=UUID=4a6ecbd4-e01b-4030-ab09-a43d5b6f63b5 ro nomodeset pci_pt_e820_access=on crashkernel=auto vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8
echo 'Loading initial ramdisk ...'
module /boot/initramfs-3.10.59.img
}

I added some options like iommu=1. But I was and am pretty sure they're not the problem.
I noticed that the default grub.cfg used linux16 and initrd16 instead of linux and initrd (in Debian). Like this:

menuentry 'Red Hat Enterprise Linux Server (3.10.0-123.9.3.el7.x86_64) 7.0 (Maipo)' --class red --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-123.el7.x86_64-advanced-4a6ecbd4-e01b-4030-ab09-a43d5b6f63b5' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos6 --hint-efi=hd1,msdos6 --hint-baremetal=ahci1,msdos6 --hint='hd0,msdos6' 4a6ecbd4-e01b-4030-ab09-a43d5b6f63b5
else
search --no-floppy --fs-uuid --set=root 4a6ecbd4-e01b-4030-ab09-a43d5b6f63b5
fi
linux16 /boot/vmlinuz-3.10.0-123.9.3.el7.x86_64 root=UUID=4a6ecbd4-e01b-4030-ab09-a43d5b6f63b5 ro nomodeset crashkernel=auto vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8
initrd16 /boot/initramfs-3.10.0-123.9.3.el7.x86_64.img
}

 So dose that lead to the problem? And what a correct Xen entry should be? 


Best regards,
Kenneth

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

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