[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [virt-tools-list] Add Connection to Virt-Manager 100% from CLI?



Thanks.  This should help a lot... but I may have more questions later.
Just not a GConf guru.  :)

Schorschi Decker

VP; Sr. Consultant Engineer
ET&D Emerging Technologies / Virtualization Platform Engineering Team
Bank of America

Office 213-345-4714




-----Original Message-----
From: Cole Robinson [mailto:crobinso redhat com] 
Sent: Wednesday, 06 April, 2011 08:15
To: Decker, Schorschi
Cc: virt-tools-list redhat com
Subject: Re: [virt-tools-list] Add Connection to Virt-Manager 100% from
CLI?

On 04/06/2011 10:48 AM, Decker, Schorschi wrote:
> Anyone investigate or develop a program or tool to add KVM host 
> connections to Virt-Manager 100% without use of the GUI?  We want to 
> automate Virt-Manager configuration and the one gap we see, is no way 
> to add a KVM host connection to Virt-Manager without some interactive 
> action/task required.  This makes population of KVM host connections 
> impossible via 100% automation.  Just hate to dig into the API, and 
> re-invent the wheel if someone has done this?  A source code example 
> would be nice of how to do it?  Not at libvirt or virt-manager API
guru.
> 
>  
> 
> Schorschi

virt-manager uses gconf to store this value, so you can use gconf cli
tools to accomplish this.

To have virt-manager start populated with the uris xen:/// and
qemu:///system, use the command

gconftool-2 --set --type list --list-type string
/apps/virt-manager/connections/uris [xen:///,qemu:///system]

To then have virt-manager autostart qemu:///system on app startup, do

gconftool-2 --set --type list --list-type string
/apps/virt-manager/connections/autoconnect [qemu:///system]

Hope that helps,
Cole

----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. 
Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. 
The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. 

References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: 
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]