Feature #84

Migrate KVM driver to the new Driver Engine

Added by Ruben S. Montero over 12 years ago. Updated almost 10 years ago.

Status:ClosedStart date:
Priority:HighDue date:
Assignee:Javi Fontan% Done:

80%

Category:Drivers - Auth
Target version:Release 1.4
Resolution:fixed Pull request:

Description

Make the KVM driver to use the new libraries, this change should not require any interface/modification changes


Related issues

Related to Feature #46: VirtualBox Driver Closed

History

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

A first functional version of the new driver was committed in r372. To close this ticket we need to perform additional testing on the driver

#2 Updated by Javi Fontan over 12 years ago

  • % Done changed from 0 to 80

#3 Updated by Ruben S. Montero about 12 years ago

  • Assignee changed from Tino Vázquez to Javi Fontan

#4 Updated by Javi Fontan about 12 years ago

Libvirt port for VNC is a real port, not a VNC port. This should be stated in the documentation.

5900 -> 0
5901 -> 1
...

#5 Updated by Javi Fontan about 12 years ago

Shutdown does not work. virsh sends the shutdown command to libvirt and returns, then the driver answers success and tm deletes the images. The VM is still shutting down but there are no disk files where to read or write so it keeps the VM in running state. A new VM state must be added while it is shutting down and epilog should be performed after poll gets shutdown state for the VM.

#6 Updated by Javi Fontan about 12 years ago

Documentation updated to reflect VNC ports for kvm/libvirt driver

#7 Updated by Javi Fontan about 12 years ago

  • Status changed from New to 3
  • Resolution set to fixed

#8 Updated by Ruben S. Montero almost 10 years ago

  • Status changed from 3 to Closed

Also available in: Atom PDF