X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 040E5DC1382 for ; Fri, 9 Dec 2011 13:09:29 +0000 (UTC) Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id BB9182197F for ; Fri, 9 Dec 2011 08:09:28 -0500 (EST) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute2.internal (MEProxy); Fri, 09 Dec 2011 08:09:28 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=jlyo.org; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mesmtp; bh=pFQMqYkCd+fEdQnir3EJAkbA+10=; b=SvzjFrdyojrn31LB5C/8cCkitsSR XHxOQf7V6zYmrPHtcfTJesiHeYOY8ZYmwsivXTjEIbwxvXa28ZtKCy34qnvR+AEy iiviW/RlThRKPdckKjqQ0XVtRg2hlvhPZPnVoePS9UTSri8HfWCYc2dt8p4FMxJr t1prNTYXfFWKYLA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:from:to:cc:subject:message-id :in-reply-to:references:mime-version:content-type :content-transfer-encoding; s=smtpout; bh=pFQMqYkCd+fEdQnir3EJAk bA+10=; b=IwEUKITIgAz6vDpfgETnxgX7hr0zd0XrJBgXqmSNDmOcH0dsywWEj0 gw6Nw4WzFST0eSPUZyJOr7o/vzXzO+EbeRKY7XnkKE4vKXrEZZufnZOkup4xVTo1 dFceMf9qgOmBKWHAtfTDsFUS3g/azAj96BYk9mvZNuVIvQIkcbeTY= X-Sasl-enc: 8AMzk3AQU4RDt9a/5S/u9KLSUcQk/GrexTjI4y9v/dzI 1323436168 Received: from telperion.jlyo.org (67-129-215-3.dia.static.qwest.net [67.129.215.3]) by mail.messagingengine.com (Postfix) with ESMTPA id 74295482522; Fri, 9 Dec 2011 08:09:28 -0500 (EST) Date: Fri, 9 Dec 2011 07:09:24 -0600 From: Jesse Young To: Natanael Copa Cc: alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] advice for virtualization on desktop Message-ID: <20111209070924.4dabfd44@telperion.jlyo.org> In-Reply-To: <20111208075522.5804d2a6@ncopa-desktop.nor.wtbts.net> References: <20111208075522.5804d2a6@ncopa-desktop.nor.wtbts.net> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.8; x86_64-unknown-linux-gnu) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Thu, 8 Dec 2011 07:55:22 +0100 Natanael Copa wrote: > Hi, > > I have been using qemu for some time for testing and network > development. > > I think raw qemu is a bit cumbersome since i need to keep track of the > mac address of all the guests. When I create a guest i create a > start.sh script where i stuff in the mac address. (I sometimes need > multiple NICs in guests and will need multiple guest vlans etc. > vde, tap and bridges is what I use). This works ok, but I think it > could be done better. (I find it cumbersome to manage the guest mac > addr manually. assign a mac, and keep track of what guest has what > mac) > > So I am asking for advice. > > I think I have the following alternatives: > > Switch to Xen. > > Use libvirtd. > > Make virtualbox work. I used to work with virtualbox, but I found that when I would run a guest for a couple of days it (the Windows XP guest) would crash. I switched to raw qemu-kvm to libvirtd/virt-manager. > In addition to N different alpine boxes I will install at least one > Windows 7 guest. I'd like to have an ubuntu guest and a fedora guest. > And fire up a random distro once in a while. > > So far, Xen dom0 boots up, but xorg seems to fail (Sandy bridge > graphics) Interestingly enough it seemed to work with the ATI card > even if switching to console with ctrl-alt-1 didnt work. > > I am having issues getting started with libvirtd. (how do i create a > new qemu guest? how do i start it, stop it?) I've been using the virt-manager (pygtk) utility with some success. it's fairily easy to work with. I couldn't get raw libvirtd working, too much XML crap, and no apparent starting point, so I looked up virt manager. I found libvirtd to be really obnoxious when it sticks it's fingers into my iptables/dnsmasq/radvd setup. I worked around this by setting the iptables path, etc. to /bin/true at configure time. So far I haven't come across any issues with it. If you're doing fancy network testing, you'd probably want to do this manually anyways. I was suprised libvirtd doesn't hand off it's networking configuration to a script. Just my 2c Jesse --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---