From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" Subject: Re: Announcing xen/master: pvops git trees rearranged Date: Mon, 21 Sep 2009 10:49:03 +0200 Message-ID: <1253522943.29011.36.camel@marc> References: <4AB431AD.1030205@goop.org> <4AB4B439.7020001@wol.de> <4AB682AA.9050906@wol.de> <20090921062247.GH31123@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20090921062247.GH31123@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= Cc: Jeremy Fitzhardinge , Xen-devel List-Id: xen-devel@lists.xenproject.org Am Montag, den 21.09.2009, 09:22 +0300 schrieb Pasi K=E4rkk=E4inen: > On Sun, Sep 20, 2009 at 09:29:46PM +0200, Marc - A. Dahlhaus wrote: > > Marc - A. Dahlhaus schrieb: > > >Hello Jeremy, > > > > > >Jeremy Fitzhardinge schrieb: > > >>Well, my current pvops/dom0 tree is finally (reasonably) stable. T= here > > >>was a fairly nasty bug which ended up corrupting dom0 memory when d= oing > > >>IO on behalf of domains, but that is finally fixed. > > >> > > >>In honour of this, I've renamed the rebase/* branches to xen/* (mov= ing > > >>the old remaining xen/* branches to xen-old/*); xen/master is now t= he > > >>preferred branch for fetching current dom0 work. > > >> > > --8<-- > > >>See http://wiki.xensource.com/xenwiki/XenParavirtOps for general > > >>directions on configuration, compilation and use. > > > > > >I think it would be a good idea to add some backtrace and debug rela= ted=20 > > >options to the CONFIG_ options listed on the wiki page so that one g= ets=20 > > >all the details needed from the testers when some bug shows up (CCd=20 > > >Pasi). The NETXEN_NIC option looks unrelated to xen... > >=20 > > Somehow my mail gateway got problems with umlauts and rewrote=20 > > mailadress, so this is another try to CC pasi... > > >=20 > Heh. It's kinda funny to have all these charset/umlaut problems still i= n 2009 :) Stange problem as we don't had such problems with other mail addresses that used umlauts in headers, we're working on reproducing it. Looks like a Perl-Module related problem in the spam filter as far as we got until now... > > >>This is definitely a work-in-progress kernel. I'd appreciate all b= ug > > >>*and* success reports so I can get some idea of how many people are > > >>using this thing, and how often there are problems. Patches gratef= ully > > >>accepted. > > > > > >Will report something back soon, > >=20 > > Had no luck. It crashed during irq initialization. Somehow the serial= =20 > > logs aren't fully transmitted. All i could catch is attached. Also is= =20 > > attached the .config used to build the dom0 kernel. Will give xen 3.4= .1=20 > > and unstable another try tomorrow. > >=20 >=20 > Please paste your grub.conf. I'm going to try xen/master tree today.. >=20 > -- Pasi title XEN pv_ops dom0 root (hd0,1) kernel /boot/xen.gz dom0_mem=3D512M loglvl=3Dall guest_loglvl=3Dall module /boot/bzImage-2.6.31-xen ro root=3DLABEL=3DROOT earlyprintk=3Dxen = 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=3D512M loglvl=3Dall guest_loglvl=3Dall com1=3D9600,8n1 console=3Dcom1 module /boot/bzImage-2.6.31-xen ro root=3DLABEL=3DROOT console=3DttyS0,96= 00n8 earlyprintk=3Dxen 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... Marc