Bug 846665

Summary:	virDomainReset not implemented with VBox
Product:	[Community] Virtualization Tools	Reporter:	cohoe
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	cohoe, crobinso, rbalakri
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-23 22:36:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description cohoe 2012-08-08 11:45:27 UTC

Description of problem:
Attempting to "reset" (virDomainReset) a VM on a VirtualBox host returns: "error: this function is not supported by the connection driver: virDomainReset"

Version-Release number of selected component (if applicable):
Compiled against library: libvir 0.9.10
Using library: libvir 0.9.10
Using API: VBOX 0.9.10
Running hypervisor: VBOX 4.1.18

How reproducible:
Always

Steps to Reproduce:
1. Connect to VBox host with virsh (vbox:///session)
2. Issue reset command 'reset vbox-test01'
  
Actual results:
error: Failed to reset domain Test01
error: this function is not supported by the connection driver: virDomainReset

Expected results:
Domain Test01 reset

Additional info:
virDomainReboot works, however the same command on the ESX driver errors if VMware Tools is not installed within the guest. This bug is similar to 846406 (ESX rather than VBox).

Comment 1 cohoe 2012-08-09 13:07:46 UTC

This also affects library/API 0.9.13

Comment 2 Dave Allan 2012-08-09 14:03:28 UTC

As with the matching ESX BZ, I think your best bet for getting this functionality is to submit patches upstream.

Comment 3 Cole Robinson 2016-03-23 22:36:03 UTC

Agreed with dave, tracking this in bugzilla isn't going to generate any results. There's many unimplemented APIs across the drivers. Closing as DEFERRED; someone just needs to provide a patch