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: Thomas <iamkenzo@xxxxxxxxx>
Subject: Re: Fwd: [Xen-users] Unable to create more than 1 VM
From: "Ray Barnes" <tical.net@xxxxxxxxx>
Date: Mon, 9 Jun 2008 07:40:42 -0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 09 Jun 2008 04:41:17 -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=zzdR9nm8n1v+lWM4c6vYXPc2iImfFmpG0t1tvA+hKk8=; b=kSPejjWZvgMddmOueBQfh7PbQFoowjigiw4j2blfF9NSC5eAO8Y1QY/g+WPVAskwDb cVvd22NaO8BVtJDwamay49z7yeyk3l4HTCJjTdm/WBfQD2LjlW5XGHGwKWUpQKb81TyW rzl2oB7+Hk2JNakyDMmDMnh3yHdu2tK8eH0XM=
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=MoCdvD1X9+BxpmkHxXEuD5f2bDiuA6kAgfjNcu1mNZHKOFxzH9jg4kHAyTK6lrlMFI iWxWHBdaPpMi84kfHpEQWQY4BYEjuIiWY52pJW7lkeRCGvb13OmFpnpgtUokHTG/uI7J vsTux/No0uIFln2WxqW5Ccttz9EpaXTP/AJkI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <55da14450806090321k60748da2u7bb55359d5d3ea6e@xxxxxxxxxxxxxx>
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: <55da14450806071104m397f9346v3ee0ea82052bc3b8@xxxxxxxxxxxxxx> <200806081513.36087.jim_burn@xxxxxxxxxxxxx> <55da14450806081242g503289dewd57d02a8c6461911@xxxxxxxxxxxxxx> <200806081626.26179.jim_burn@xxxxxxxxxxxxx> <55da14450806081340m2d0c5f57v3142e315816134dd@xxxxxxxxxxxxxx> <55da14450806090321k60748da2u7bb55359d5d3ea6e@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Now that you've posted your configs and the error you're getting about
vncpasswd, this is a little more clear.  Comment out the line that
says:

vfb = [ 'type=vnc' ]

I realize that the default behavior (or at least the way I know it to
be) is as your config mentions:

# The backend listens on 127.0.0.1 port 5900+N by default, where N is
# the domain ID.

But clearly vnc can't bind(), probably because it's not incrementing
the port number.  I just duplicated this problem locally on Cent 5.1
with Xen 3.2.1 compiled from source.  Try something more reasonable
like:

vfb = [ 'type=vnc,vnclisten=0.0.0.0,vncdisplay=2,vncpasswd=letsgetit' ]

This will give you a VNC instance on :5902, just modify vncdisplay for
each domU.  If I have time, I'll dig into the code and find out if
this is really a "bug".

-Ray


On 6/9/08, Thomas <iamkenzo@xxxxxxxxx> wrote:
> This morning I tried using a disk image instead of LVM for the second
> VM, and I still have the exact same problem. I am starting to become
> really suspicious about the DomU distro I am using. I will try to use
> another method for installing a DomU.
>
> _______________________________________________
> 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