[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Announcing xen/master: pvops git trees rearranged
Am Montag, den 21.09.2009, 12:03 +0300 schrieb Pasi Kärkkäinen: > On Mon, Sep 21, 2009 at 10:49:03AM +0200, Marc - A. Dahlhaus [ Administration > | Westermann GmbH ] wrote: --8<-- > > title XEN pv_ops dom0 > > root (hd0,1) > > kernel /boot/xen.gz dom0_mem=512M loglvl=all guest_loglvl=all > > module /boot/bzImage-2.6.31-xen ro root=LABEL=ROOT earlyprintk=xen 4 > > module /boot/initramfs-2.6.31-xen > > > > With this one i get no output from the kernel itself at all, i think i > > have some things build as modules in my .config that needs to be buildin > > for a working vga console (might be that i need to change the > > earlyprintk param to vga) but didn't had the time to hunt the problem > > down. > > > > > > title XEN pv_ops dom0 with serial console > > root (hd0,1) > > kernel /boot/xen.gz dom0_mem=512M loglvl=all guest_loglvl=all > > com1=9600,8n1 console=com1 > > module /boot/bzImage-2.6.31-xen ro root=LABEL=ROOT console=ttyS0,9600n8 > > earlyprintk=xen 4 > > module /boot/initramfs-2.6.31-xen > > > > That's the one i used to grab the log. > > > > This is a i945 based box with an Core 2 Duo E8400 and 4GB Ram installed > > but only 2912584k usable because of an PCI-Card that supports only 32bit > > addressing (appropriated-ram-crap). Could this be a problem? I try to > > test again with 2GB Ram installed this evening and report if it gets any > > further... > > > > Here are my working grub.conf entries for pv_ops dom0: > > VGA text console: > > title Fedora Xen pv_ops dom0-test (2.6.31-rc5) > root (hd0,0) > kernel /xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all > module /vmlinuz-2.6.31-rc5 ro root=/dev/mapper/vg_dom0test-lv01 > module /initrd-2.6.31-rc5.img > > > Serial console: > > title Fedora Xen pv_ops dom0-test (2.6.31-rc5) / serial console > root (hd0,0) > kernel /xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all > com1=19200,8n1 console=com1 > module /vmlinuz-2.6.31-rc5 ro root=/dev/mapper/vg_dom0test-lv01 > console=hvc0 earlyprintk=xen > module /initrd-2.6.31-rc5.img > > When using serial console with Xen you don't need to specify serial console > stuff for the dom0 kernel.. > Also note the 'console=hvc0' for dom0 kernel.. Isn't the selection of hvc0 as main console supposed to work out automatically? Looks like a bug if it isn't. Anyway thanks for the hint. Will give it a try with a grub config adapted to yours later today. Are there still problems related to specific CONFIG_ options which i should deactivate in my build? The xen related options i used (only frontends build as modules): [mad@darkstar ~]$ grep XEN /boot/config-2.6.31-xen CONFIG_XEN=y CONFIG_XEN_MAX_DOMAIN_MEMORY=8 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_DOM0_PCI=y CONFIG_MICROCODE_XEN=y CONFIG_PCI_XEN=y CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_KBDDEV_FRONTEND=m CONFIG_HVC_XEN=y CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=y CONFIG_XENFS=y CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=m CONFIG_XEN_S3=y CONFIG_ACPI_PROCESSOR_XEN=y Marc _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |