From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Announcing xen/master: pvops git trees rearranged Date: Mon, 21 Sep 2009 10:39:20 -0400 Message-ID: <20090921143920.GB20933@phenom.dumpdata.com> References: <4AB431AD.1030205@goop.org> <4AB4B439.7020001@wol.de> <4AB682AA.9050906@wol.de> <20090921062247.GH31123@reaktio.net> <1253522943.29011.36.camel@marc> <20090921090331.GJ31123@reaktio.net> <1253524707.29011.49.camel@marc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1253524707.29011.49.camel@marc> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" Cc: Jeremy Fitzhardinge , Xen-devel List-Id: xen-devel@lists.xenproject.org > > > 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 Do also add 'debug' in the line. That will give some more verbose output. > > > 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... If you specify 'mem=2GB' it will limit how much memory Xen and Linux see. But you do use 'dom0_mem' which limits the amount of memory that Dom0 would use for PCI drivers. So the 32-bit support shouldn't be an issue. Looking at the serial line it also looks that your Linux is 32-bit? Did you try the 64-bit? > > > > > > > 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. Yes. As long as CONFIG_HVC_XEN is compiled in (=y). > 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? It should be all clear. But we haven't tested all of them, so you might be hitting one that hasn't been tested yet.