Bug #3677

Use TCP connection for libvirt

Added by Javi Fontan over 5 years ago. Updated almost 5 years ago.

Status:ClosedStart date:03/12/2015
Priority:NormalDue date:
Assignee:Javi Fontan% Done:

0%

Category:Documentation
Target version:Release 4.14.2
Resolution:fixed Pull request:
Affected Versions:OpenNebula 4.14

Description

The KVM drivers connect to libvirt using a socket connection. This means that only one action can be performed at a given time. Using TCP connection makes multiple actions at the same time feasible. For example, deploying 16 VM in the same host at the same time.

Check that changing the connection from qemu:///system to qemu://localhost/system works.


Related issues

Related to Bug #3686: Check Libvirt TCP mention in KVM configuration guides (qe... Closed 03/16/2015

History

#1 Updated by Ruben S. Montero over 5 years ago

  • Target version set to Release 5.0

#2 Updated by Ruben S. Montero over 5 years ago

  • Related to Bug #3686: Check Libvirt TCP mention in KVM configuration guides (qemu+ssh) added

#3 Updated by Ruben S. Montero almost 5 years ago

  • Tracker changed from Backlog to Bug
  • Category changed from Drivers - VM to Documentation
  • Affected Versions OpenNebula 4.14 added

Documentation was not added, but it tcp connection is supported

#4 Updated by Ruben S. Montero almost 5 years ago

  • Target version changed from Release 5.0 to Release 4.14.2

#5 Updated by Ruben S. Montero almost 5 years ago

Evaluate the use of the TCP connection as default for OpenNebula

#6 Updated by Tino Vázquez almost 5 years ago

  • Assignee set to Javi Fontan

#7 Updated by Javi Fontan almost 5 years ago

  • Status changed from Pending to Closed
  • Resolution set to fixed

Also available in: Atom PDF