- Users - libvirt List Archives

[libvirt-users] connect libvirt and virtualbox
by angelo alfano 01 Apr '10

01 Apr '10

conn = libvirt.open("vbox:///session") return this error: libvir: VBOX error : internal error unable to initialize VirtualBox driver API Traceback (most recent call last): File "prova.py", line 5, in <module> conn = libvirt.open("vbox:///session") File "/usr/lib/python2.6/dist-packages/libvirt.py", line 163, in open if ret is None:raise libvirtError('virConnectOpen() failed') libvirt.libvirtError: internal error unable to initialize VirtualBox driver API why?

4 10

[libvirt-users] iSCSI supported initiators
by Alexander Pierce 01 Apr '10

01 Apr '10

What initiators does libvirt support for the iSCSI pool? Will it work with qlogic's iSCSI HBAs for instance? --- Alexander Pierce, RHCE Solutions Architect -- Red Hat, Inc. apierce(a)redhat.com -- +1 (530) MR-LINUX (675-4689) Learn. Network. Experience Open Source. The 2010 Red Hat Summit and JBoss World Boston. June 22 - 25, 2010 http://www.theredhatsummit.com http://www.jbossworld.com

2 1

[libvirt-users] advice on creating and reusing connections
by jeremy avnet 31 Mar '10

31 Mar '10

Are there any recommendations as to how often a new connection should be made versus reused? Right now we create a new connection *every time* we hit libvirt for something. We can easily change this so that a single connection is made for a series of libvirt calls, or even so that a single connection is used for the lifetime of the running application. What are the issues to consider when making these choices? We are connecting to qemu:///system. Thank you. .:. brainsik

2 1

[libvirt-users] connection creating
by jeremy avnet 31 Mar '10

31 Mar '10

Are there any recommendations as to how often a new connection should be made versus reused? Right now we create a new connection *every time* we hit libvirt for something. We can easily change this so that a single connection is made for a series of libvirt calls, or even so that a single connection is used for the lifetime of the running application. What are the issues to consider when making these choices? We are connecting to qemu:///system. Thank you. .:. brainsik

2 1

[libvirt-users] libvirt connections
by brandlk＠mathematik.uni-marburg.de 31 Mar '10

31 Mar '10

Hello, I'm working with libvirt version 0.7.7 and encountered some problems with ssh connections to the xen hypervisor: - if the hypervisor is not running libvirt.open("xen+ssh://host") doesn't time out put keeps trying to connect to host on port 8000. I've tried with the following test program: try: conn = libvirt.open("xen+ssh://host") except: print "failed" sys.exit(1) However: after aborting the program with Ctrl-C I get the exception. - I want to close all libvirt connections at the end, but closing the connections does not close the ssh - nc connections libvirt opens in the background to talk to the hypervisor. I have to manually delete all domain objects as well to get the pending ssh - nc connections closed. I can keep on using the domain object, even if I closed the connection before. Is this behaviour intended? Any help would be great. K. Haselhorst

2 2

[libvirt-users] Vserver patch for Libvirt
by Chaitra Gorantla 31 Mar '10

31 Mar '10

Hi all, I am using libvirt for managing KVM. I would also like to manage Vserver also using libvirt. Is there any patch available for vserver ? When will libvirt relase official patch for vserver? Thanks, Chaitra ________________________________ This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. ______________________________________________________________________

2 2

[libvirt-users] Attach-interface vs attach-device
by steven765＠yahoo.com 30 Mar '10

30 Mar '10

Working with the two commands there's a noticeable difference in the time redhat takes to detect interfaces using attach-interface vs attach-device? About 5-8 seconds using attach interface, and near instant with attach-device. That little bit aside, I'm trying to find a way to 'unplug' a VM without actually removing the interface. The easy fix is to attach it without adding the tap interface to mybridge, but attach device and interface do not allow this. Looking in the source for libvirt I found the InterfacesStartmodeDefFormat however it seems that virsh doesn't export this option. Maybe this just needs to be implemented? Might anyone have insights as to the best method to pursue? I'm willing to do the leg work but I'm just starting to look into how the sources are laid out and that's going to take a bit. Pointers are appreciated. Thanks in advance, Steve

1 0

[libvirt-users] CfP with Extended Deadline 5th Workshop on Virtualization in High-Performance Cloud Computing (VHPC'10)
by Michael Alexander 30 Mar '10

30 Mar '10

Apologies if you received multiple copies of this message. ================================================================= CALL FOR PAPERS 5th Workshop on Virtualization in High-Performance Cloud Computing VHPC'10 as part of Euro-Par 2010, Island of Ischia-Naples, Italy ================================================================= Date: August 31, 2010 Euro-Par 2009: http://www.europar2010.org/ Workshop URL: http://vhpc.org SUBMISSION DEADLINE: Abstracts: April 4, 2010 (extended) Full Paper: June 19, 2010 (extended) Scope: Virtualization has become a common abstraction layer in modern data centers, enabling resource owners to manage complex infrastructure independently of their applications. Conjointly virtualization is becoming a driving technology for a manifold of industry grade IT services. Piloted by the Amazon Elastic Computing Cloud services, the cloud concept includes the notion of a separation between resource owners and users, adding services such as hosted application frameworks and queuing. Utilizing the same infrastructure, clouds carry significant potential for use in high-performance scientific computing. The ability of clouds to provide for requests and releases of vast computing resource dynamically and close to the marginal cost of providing the services is unprecedented in the history of scientific and commercial computing. Distributed computing concepts that leverage federated resource access are popular within the grid community, but have not seen previously desired deployed levels so far. Also, many of the scientific datacenters have not adopted virtualization or cloud concepts yet. This workshop aims to bring together industrial providers with the scientific community in order to foster discussion, collaboration and mutual exchange of knowledge and experience. The workshop will be one day in length, composed of 20 min paper presentations, each followed by 10 min discussion sections. Presentations may be accompanied by interactive demonstrations. It concludes with a 30 min panel discussion by presenters. TOPICS Topics include, but are not limited to, the following subjects: - Virtualization in cloud, cluster and grid HPC environments - VM cloud, cluster load distribution algorithms - Cloud, cluster and grid filesystems - QoS and and service level guarantees - Cloud programming models, APIs and databases - Software as a service (SaaS) - Cloud provisioning - Virtualized I/O - VMMs and storage virtualization - MPI, PVM on virtual machines - High-performance network virtualization - High-speed interconnects - Hypervisor extensions - Tools for cluster and grid computing - Xen/other VMM cloud/cluster/grid tools - Raw device access from VMs - Cloud reliability, fault-tolerance, and security - Cloud load balancing - VMs - power efficiency - Network architectures for VM-based environments - VMMs/Hypervisors - Hardware support for virtualization - Fault tolerant VM environments - Workload characterizations for VM-based environments - Bottleneck management - Metering - VM-based cloud performance modeling - Cloud security, access control and data integrity - Performance management and tuning hosts and guest VMs - VMM performance tuning on various load types - Research and education use cases - Cloud use cases - Management of VM environments and clouds - Deployment of VM-based environments PAPER SUBMISSION Papers submitted to the workshop will be reviewed by at least two members of the program committee and external reviewers. Submissions should include abstract, key words, the e-mail address of the corresponding author, and must not exceed 10 pages, including tables and figures at a main font size no smaller than 11 point. Submission of a paper should be regarded as a commitment that, should the paper be accepted, at least one of the authors will register and attend the conference to present the work. Accepted papers will be published in the Springer LNCS series - the format must be according to the Springer LNCS Style. Initial submissions are in PDF, accepted papers will be requested to provided source files. Format Guidelines: http://www.springer.de/comp/lncs/authors.html Submission Link: http://edas.info/newPaper.php?c=8553 IMPORTANT DATES April 4 - Abstract submission due (extended) May 19 - Full paper submission (extended) July 14 - Acceptance notification August 3 - Camera-ready version due August 31 - September 3 - conference CHAIR Michael Alexander (chair), scaledinfra technologies GmbH, Austria Gianluigi Zanetti (co-chair), CRS4, Italy PROGRAM COMMITTEE Padmashree Apparao, Intel Corp., USA Volker Buege, University of Karlsruhe, Germany Roberto Canonico, University of Napoli Federico II, Italy Tommaso Cucinotta, Scuola Superiore Sant'Anna, Italy Werner Fischer, Thomas Krenn AG, Germany William Gardner, University of Guelph, Canada Wolfgang Gentzsch, DEISA. Max Planck Gesellschaft, Germany Derek Groen, UVA, The Netherlands Marcus Hardt, Forschungszentrum Karlsruhe, Germany Sverre Jarp, CERN, Switzerland Shantenu Jha, Louisiana State University, USA Xuxian Jiang, NC State, USA Kenji Kaneda, Google, Japan Yves Kemp, DESY Hamburg, Germany Ignacio Llorente, Universidad Complutense de Madrid, Spain Naoya Maruyama, Tokyo Institute of Technology, Japan Jean-Marc Menaud, Ecole des Mines de Nantes, France Anastassios Nano, National Technical University of Athens, Greece Oliver Oberst, Karlsruhe Institute of Technology, Germany Jose Renato Santos, HP Labs, USA Borja Sotomayor, University of Chicago, USA Yoshio Turner, HP Labs, USA Kurt Tuschku, University of Vienna, Austria Lizhe Wang, Indiana University, USA Chao-Tung Yang, Tunghai University, Taiwan DURATION: Workshop Duration is one day. GENERAL INFORMATION The workshop will be held as part of Euro-Par 2010, Island of Ischia-Naples, Italy. Euro-Par 2010: http://www.europar2010.org/

1 0

[libvirt-users] how-to doc for svirt/SELinux enabling
by Jonathan M Barney 30 Mar '10

30 Mar '10

Anyone have a pointer or some documentation or a how to enable svirt support in RHEL 5.4 using libvirt 6.3 and KVM/QEMU? Thanks Jonathan

1 0

Re: [libvirt-users] Problem attaching device
by steven765＠yahoo.com 25 Mar '10

25 Mar '10

Thanks, but problem still persists. I actually fat fingered entering it the first time The xmlfile really is: <?xml version="1.0"?> <interface type="network"> <mac address="52:54:00:5c:fe:a8"/> <source network="default"/> <target dev="vnet1"/> </interface> I ran xmllint and it just says no DTD specified, however this works perfectly if i use the attach-device command in virsh. I tired it both with and without the first line version=1.0 I try running it through python and boom, is there something else I'm missing? I can't find any documentation about the overall libvirt xml schema. Thanks again, Steve --- On Thu, 3/25/10, Daniel Veillard <veillard(a)redhat.com> wrote: > From: Daniel Veillard <veillard(a)redhat.com> > Subject: Re: [libvirt-users] Problem attaching device > To: steven765(a)yahoo.com > Cc: "Matthias Bolte" <matthias.bolte(a)googlemail.com>, libvirt-users(a)redhat.com > Date: Thursday, March 25, 2010, 9:18 AM > On Wed, Mar 24, 2010 at 11:18:10PM > +0100, Matthias Bolte wrote: > > 2010/3/24 <steven765(a)yahoo.com>: > > Your XML is really not well formed. This > > > > <source network-'default'/> > > > > should be > > > > <source network='default'/> > > > > > target dev='vnet1'/> > > > > And you miss a < before the word target: > > > > target dev='vnet1'/> > > > > should be > > > > <target dev='vnet1'/> > > > > > </interface> > > > > > > I've tired giving it the full path still no > luck. > > > Thanks in advance, > > use xmllint to check XML instances if you're not > sure > > xmllint net.xml > > Daniel > > -- > Daniel Veillard | libxml Gnome XML XSLT > toolkit http://xmlsoft.org/ > daniel(a)veillard.com > | Rpmfind RPM search engine http://rpmfind.net/ > http://veillard.com/ | virtualization library http://libvirt.org/ >

2 1