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] [XCP] ['NO_HOSTS_AVAILABLE']... what?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] [XCP] ['NO_HOSTS_AVAILABLE']... what?
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Sun, 13 Feb 2011 05:05:37 +0300
Delivery-date: Sat, 12 Feb 2011 18:05:59 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=6vgvpykaeRc+KuV5NJBs4K4DaJ3nDBT01XG1skz5hPE=; b=prE0KYTMN193xDNDhRevqYs12J+rbMKH1Lkz9yEHbw90DV8FrJDGyptuHBw4QXqQsn U8Hmn++dhfSpO5ql3EeWjjiZdxEG3a44Bkoj4llvOQ/Ejt/orX1q/5JUaEepkBj9334h Eb0/hELy3k4GEURpyyCag4g/6ToNiGVGKTZ8s=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; b=kOHlcUavOSYVIQ6ZOWVEefeueoqmgu+tyah59t7d63gOZ3k+Zn4caLQASsLoIn5e76 rwsocenUfLjrT/seT6ma/dfuQQ9P4gOVypYdYE0WMHnpfouhDZh9vwNCWiqN/HqaSCsO +XMlPmeaLajsIn+5uGUKVl1MVxVCFqO9ywoog=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <COL114-W6242C721F14D263CF2692A7EE0@xxxxxxx>
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: <COL114-W6242C721F14D263CF2692A7EE0@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20101226 Icedove/3.0.11
1) Throw away any GUI helpers. They may be nice when it works fine, but they are all suck when it come to solve problems.
2) Try to run VM by hands from pool master (do xe vm-start vm=(vm_name)
3) Check if pool have enabled hosts: xe host-list params=name-label,enabled
4) If no task performed, restart all xapi on every pool (xe-toolstack-restart starts from master to slaves).

And one more: check if you set sane memory values. If you set  memory  to 100500Gb for VM to be ran on host with 700Mb of RAM, it will not start anyway.

On 12.02.2011 04:23, Buckminster Katt wrote:

I'm still running XCP 0.5 on two servers.  I am trying to make a few 10Gig Slackware64 13.1 servers (using the Windows 2003 server template).

However, every time I try to start the guests in OpenXenManager, they die with something like:
 Async VM.start Slack64 13.1 #3['NO_HOSTS_AVAILABLE']

I tried starting the hosts from the xsconsole and got the same results.  I can't find anything to indicate why this is happening.

Whats really inconsistent is that at one point, I had built some identical 5Gig Slackware servers and out of 3... only the second would start, the 1st and 3rd would fail with the NO_HOSTS_AVAILABLE.  Unfortunately, I was not able to live with such small space, so I deleted them, but had less luck on the second try.

Best I can see, it appears to me that even though they are supposed to start on the second Xen server (where the virtual drive is), they are being started on the first xen server.

Any ideas on how to fix this?

Also, I am considering upgrading to the 1.0 beta.  Is it reasonable stable to do this upgrade at this point?

Thanks in advance.

BKNJ

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