[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fwd: [Xen-users] Unable to create more than 1 VM


  • To: "Felix Krohn" <felix.krohn@xxxxxxx>
  • 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
  • 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=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

> 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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.