WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] strange domU problem

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] strange domU problem
From: "S.Çağlar Onur" <caglar@xxxxxxxxxxxxx>
Date: Fri, 12 Jan 2007 01:26:09 +0200
Delivery-date: Thu, 11 Jan 2007 15:28:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200701101636.02759.caglar@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: TÜBİTAK / UEKAE
References: <200701101636.02759.caglar@xxxxxxxxxxxxx>
Reply-to: caglar@xxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.5
Hi;

10 Oca 2007 Çar 16:35 tarihinde, S.Çağlar Onur şunları yazmıştı: 
> After upgrading to current xen-3.0.4-testing.hg domU's starts to not
> working as expected, here are the some findings;
>
> * dom0 boot without a problem
> * xend starts without a problem
> * As soon as "xm create domain", domain enters a blocked state and never
> returns (nothing changes if i use old 3.0.3-domU kernel or new one)
> * dmesg, xen dmesg, xen logs shows nothing strange
> * Starting another domU while first domU in blocked state unfreezes first
> one for a while and first domU starts to boot but after a while (~5seconds)
> enters blocked state again
> * Second domU also enters blocked state as soon as it started
> * In order to boot/use first domU ,i have to continuosly destroy/create
> second domU but they always ended in blocked state

After trying lots of different setups i found the problem, somehow if xen/ is 
compiled with gcc-4.2 domU hangs forever as i described but dom0 boots/works 
fine without a problem. So here are the some more findings;

* gcc-3.4.6 compiled xen/ and gcc-4.2 compiled dom0/domU kernels (3.0.4_1) 
works well, 

* gcc-4.2 compiled xen/ and gcc-3.4.6 compiled dom0/domU kernels (3.0.3) hangs 
as described,

So neither gcc-4.2 generates wrong code for hypervisor or xen/ has some bugs 
triggered by gcc-4.2. Is there a way to debug/investigate so i can try to 
find the problem?

Cheers
-- 
S.Çağlar Onur <caglar@xxxxxxxxxxxxx>
http://cekirdek.pardus.org.tr/~caglar/

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!

Attachment: pgp7bWO5w0SLp.pgp
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>