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: "jim burns" <jim_burn@xxxxxxxxxxxxx>
Subject: Re: Fwd: [Xen-users] Unable to create more than 1 VM
From: Thomas <iamkenzo@xxxxxxxxx>
Date: Sun, 8 Jun 2008 19:19:07 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 08 Jun 2008 10:19:37 -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=S/QvMPLycXApDVdii9bK/DLmq1pnHemdzJRqQ3cqm/Q=; b=f61FcQzL5JUvjOrmQS8a14d9Rx0Dnd2nvKWBWtIKwpm4XydDFtw47YZ1q2QUlSd6AE scmawUPm68YzXsmw7y9G8jdX8vmZ3/99n9NTiK69iDmYe0S12AJ7w2h6rFWFRLavYBF0 m6Nixsc2o4n7pArREj2O7rgf5w2imwqIs7AwY=
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=m+SLtQxrRqenMYH0sgLSSMdM+YxV/2Nt5uOUv0HyR8ynYdXtqEM8Vrj/YdaU82CL0Z EwzZ/pAr8OKreKuQOrSWX8bRvguJ5fi8PNfxeo5rQEORLHt/mbHySbeNIhNPb/ybrJXA YXJ6+ZpfgLlx7Ch4v+k/GLnI7F/zUBww6iH2w=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200806081245.20660.jim_burn@xxxxxxxxxxxxx>
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> <200806081022.56376.jim_burn@xxxxxxxxxxxxx> <55da14450806080802u16f4546bm89c45edf0c234459@xxxxxxxxxxxxxx> <200806081245.20660.jim_burn@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> Yeah, caps never changed with 3.1 and up. The version you've been told should
> match something like:
>
> xen_major              : 3
> xen_minor              : 2
> xen_extra              : .1
>
> If it is indeed 3.2.1, 32-on-64 should work fine.

Then yes my Xen is 3.2.1


> That's good. I guess NAT accounts for the vifs having ips, but then shouldn't
> your 2nd vm's gateway be 10.0.0.129, not .128?
Now that I specify the mac address in vif=[...], the vifxx.0 in Dom0
keeps changing. Therefore my gateway gets always wrong, and the
network is no longer reachable.


By the way, I have deactivated network support in xend-config.sxp,
just to check, and still my second VM won't run, so I think we can say
that is nothing to do with networking. What could possibly go wrong?

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