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 43CFF1381F3 for ; Mon, 3 Dec 2012 15:21:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7639E21C00C; Mon, 3 Dec 2012 15:21:24 +0000 (UTC) Received: from mx1.hadt.biz (sil.hadt.biz [5.9.16.100]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A13FCE065A for ; Mon, 3 Dec 2012 15:20:02 +0000 (UTC) Received: from [192.168.255.100] (p5DCC76F3.dip.t-dialin.net [93.204.118.243]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.hadt.biz (Postfix) with ESMTPSA id 4290C40040 for ; Mon, 3 Dec 2012 16:20:00 +0100 (CET) Message-ID: <50BCC31F.8080202@hadt.biz> Date: Mon, 03 Dec 2012 16:19:59 +0100 From: Michael Hampicke User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] libvirt References: <50BC62C1.2070801@hadt.biz> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 00f440cd-630b-494e-9f28-03e8d2e22799 X-Archives-Hash: c775fc4b3949db745e784823843bcbd6 >> 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 >> 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 :) >> 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.