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: Fwd: [Xen-users] Unable to create more than 1 VM

To: "Felix Krohn" <felix.krohn@xxxxxxx>
Subject: Re: Fwd: [Xen-users] Unable to create more than 1 VM
From: Thomas <iamkenzo@xxxxxxxxx>
Date: Tue, 10 Jun 2008 19:41:04 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 10 Jun 2008 10:41:54 -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=Ao2TFQRE8isA1rJBILeCS2VBMUEs0JXI7/YmYBX5N2I=; b=wom45NUeGP+0MYfoea0OAY3l6iEfP5amvZQuP5EQvPAqAAZmy5RicIOTF2Gt6E63ZQ NbKUhq5JQCgPP/k0dLO9Ovj1P6EHbyrlwb60dOeJkbnNiUCOayEOGyetIeUPbYVZ4s7o 7gJS+niLKWGhmsUyXCiVwMkMDZn6saL7OwdJ0=
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=jAxW2EzWJzIPNa5zffq7u6TGYtGBijGKf0/kTIOMUrHCOW8nxuHCv8/e9HnV8V472u x/FSnZjr58Egs692mKBKh/SThisroZ98WTskrazGKlWELwUy3bQqLJ1kahW8VEZzdy6r ieE2Vt6tS9+Yk1GnGLTycGuK5WGQHAsRjAVq0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080610132147.GJ11750@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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <55da14450806091459q7da765aeq2fad1a934920f24c@xxxxxxxxxxxxxx> <55da14450806100314l7bcc781fi948587d3d915527c@xxxxxxxxxxxxxx> <55da14450806100319w2a416cf5uf2c5a74bdb2fcf6f@xxxxxxxxxxxxxx> <20080610103521.GE11750@xxxxxx> <55da14450806100415r3a0edd16m470a1c0b62bc2258@xxxxxxxxxxxxxx> <55da14450806100440u5d05c9f3n1e7f2d9537354758@xxxxxxxxxxxxxx> <55da14450806100540y6d3da1f9gcfe6bbb5c3a9c556@xxxxxxxxxxxxxx> <20080610125926.GI11750@xxxxxx> <55da14450806100616p26d91e09l49093562fad62ba5@xxxxxxxxxxxxxx> <20080610132147.GJ11750@xxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> I guess your DNS is broken - make sure you can resolve names from inside
> the domU and that the adress you're connecting from can be reversed
> (easiest thing is to add an entry in /etc/hosts in the domU)
You are right, I can't resolve names from inside a DomU. I tried doing
"apt-get update" and it was unable to connect because it couldn't
resolve names. In the Dom0 it does work though. How do I fix that? I
never run into such issue before. Do I need to install dnsutils? I
cannot use nslookup in a DomU as it is not installed.

Here is the /etc/resolv.conf in Dom0:
----------------------------------------------------
nameserver 127.0.0.1
nameserver my.server.IP.address
nameserver 213.186.33.99

Here is the /etc/resolv.conf in a DomU:
--------------------------------------------------------
nameserver 213.186.33.99

Is 213.186.33.99 the IP address of Ovh DNS server?


Beside that when I ssh I use the IP address of the DomU, so I use the
following command: "ssh user@xxxxxxxx" therefore DNS is not part of
the equation. Am I right?

> /var/log/syslog?
There is only stuff about cron, nothing special I could find.

> I experienced the same thing. When I created a couple of guest, the
> momory of Dom0 was reduced. However, when I deleted those guest, the
> memory didn't come back to its original state. Only after rebooting
> Dom0, its memory went back to the number it should be. Maybe I'm
> misunderstanding something, but that doesn't seem a reasonable
> behavior (I mean, having to restart Dom0).
> Gaston
Yeah really strange. It might be Xen's default behaviour, there is
probably a special command to give back the freed memory to Dom0.

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