From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 9C3DE1381F3 for ; Mon, 3 Dec 2012 20:08:00 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8049421C02E; Mon, 3 Dec 2012 20:07:42 +0000 (UTC) Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6899A21C01C for ; Mon, 3 Dec 2012 20:06:12 +0000 (UTC) Received: by mail-bk0-f53.google.com with SMTP id j5so1265402bkw.40 for ; Mon, 03 Dec 2012 12:06:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=XdBLj5QmuL0tvdG9FCCE7U//3knHAHE1f52RuZTyO+Q=; b=Yd9jl5xhvDV7S0FvrSEo0o5kB+q7nmzsj8vwJbTcdvVekQd20SsmlFhQb8K3Vu7tms mRftCwzZClH7YZ4dIYPXD3DgSm5UOhU62lMhX9YLNPI0IAdo/tGMPYQxkvHs+kE9CUII QyY2R1VeaClu90F0tAS96S9sQqEOTdwGTaupT0zCD7dv3x5fxDDFrZf/mqSBzP8f/iVL HLL6TEHI5aEsbFOvqXN+vAP4F1MN2ZyO0pFeHOeCCldM0v5ionABUCFnTAjWzJrlOuDe eS4v0ctfesa8HNQoagUhOS1XNl9+TsoJj3IG3+5vOpYXGEOtFnawnV7QV2WcteZ+9gXO YkBA== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.204.153.27 with SMTP id i27mr3186200bkw.116.1354565170889; Mon, 03 Dec 2012 12:06:10 -0800 (PST) Received: by 10.205.26.137 with HTTP; Mon, 3 Dec 2012 12:06:10 -0800 (PST) In-Reply-To: <50BCC31F.8080202@hadt.biz> References: <50BC62C1.2070801@hadt.biz> <50BCC31F.8080202@hadt.biz> Date: Mon, 3 Dec 2012 15:06:10 -0500 Message-ID: Subject: Re: [gentoo-user] libvirt From: Michael Mol To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 58184b22-cebd-4b4b-99db-69985afd48c5 X-Archives-Hash: eff2d9c54c490bfad992ff2c41f9b5d4 On Mon, Dec 3, 2012 at 10:19 AM, Michael Hampicke wrote: >>> Do you need a virsh command, or is it enough to know libvirt supports? >>> In the second case you might look at [1] >> >> Well, given that I'm on gentoo, USE flags start getting involved in >> enabling and disabling functionality. Rather than actively examining >> the compile-time factors, I was hoping for a way to simply ask >> libvirtd via virsh. Going that route gives me an approach that works >> weather I'm on Gentoo, Linux, Debian or whatever. >> > > Good point. Virsh should at least tell you what storage pool support has > been enabled while compiling. That would still leave you with another > problem: Even if iSCSI or LVM support has been enabled, it doesn't mean > you can actually use it on that host (maybe no kernel support, not > configured, maybe no disk in node, ...) > > In virsh there's a find-storage-pool-sources command, sadly there's > almost no documentation. On my testing machine it is at least able to > discover the LVM. > > virsh # find-storage-pool-sources logical > > > > kvm1 > > > After digging through the docs a little more, I'm almost certainly going with 'directory'. Later, it'll be NFS. I'm surprised it didn't offer you either of those options...but I guess it was looking for fully-configured things. > >>> You also might take a look at virt-manager (in portage) which is a gui >>> for libvirt that manages libvirt on your local machine an remote >>> machines (via ssh tunnel for example). >> >> I've played with virt-manager before. I could use it again, but at >> least part of this exercise is to learn libvirt and kvm using a >> spartan toolchain. So I'm trying to do everything I can via CLI. (I'm >> handy enough with Python that I could use the python API bindings, but >> I presumed virsh would be easier, if not simpler.) > > Yeah, I was a hardcore kvm user once too :) No libvirt installed, just > pure kvm, did everything on cli, creating images, setting up the virtual > network, starting kvm vms by hand with a big-ass argument list, ... I > guess I just got lazy :) Actually more familiar with Xen. I'm going with kvm on this one bevause virtualbox on a debian system doesn't give me the flexibility for network topology that I'm looking for...so I want to go with Linux as a hypervisor and do the topology magic there. Anyway, I'm of the opinion that once you understand what you're doing, being lazy is the best thing you can be. But you have to understand what you're doing in order to know when to be lazy. ^^ > >>> I am really happy with virt-manager here, it work very well on you don't >>> need to remember all the virsh commands (which becomes pretty handy when >>> managing storage, virtual networks and creating vms) >> >> Yeah, I'm hoping to learn all those commands. I want to >> proof-of-concept an approach for a high-availability NFS server using >> VMs.[2] :) > > Sounds interesting, I'll bookmark that. Yeah, it's going to be fun. :) -- :wq