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-users

Re: [Xen-users] DomU stops booting

To: mlg-hessigheim@xxxxxx
Subject: Re: [Xen-users] DomU stops booting
From: Thomas <iamkenzo@xxxxxxxxx>
Date: Sun, 12 Oct 2008 13:40:08 +0200
Cc: Anton <anton.list@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 12 Oct 2008 04:40:49 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=d2COyAq4lWiSmF7GY8MHxy6/IQ1qOURGkEdjJ8kvCDw=; b=FJ654QGuc7Ytkvh/GwLUqTCOWUzeFSI1+BjxWRKb8d1hV9OGfos9sdDxixrfCoZtl7 lnYeMD7MtBYXQF1sl2IpEk2MKF8T2wZrU8ichtoQmkUH/FvCYT2m+dUgue0wfm5lwxc9 uZVfOGR9fsJRP7t/v4/vZtKVIZTkvhXJ9dhXM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Zkls8ChW7HT+k0ekT3UtbN6JqKzcDig9tuxFg+9CgAI2ab28d43DdSrNIQiyqDkqn6 xZPcB03URg49K56HELGXegVdTIBBymBezx+0HQGNkXy8HgOKUoEO0dNez4whwQqSsrZf b3Q4XGut94dOIM9Ub8ycGgDQyNvPFVlsvWB7A=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48F1BB32.60308@xxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <48F07813.4020609@xxxxxx> <45811f70810110308x62fe7aecj28ee348c491d8451@xxxxxxxxxxxxxx> <48F1BB32.60308@xxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
How can such a stupid problem still exist in 2008? Can't Xen handle
some kind of misconfiguration detection? I remember struggling for
days just because I had to change 1 character or 1 word in my Xen
configuration files, that's not a very good selling point. Moreover
from one version to another, the configuration file can also
completely fail.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>