Bug 846406 - virDomainReset not implemented with ESX
Summary: virDomainReset not implemented with ESX
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-07 16:58 UTC by cohoe
Modified: 2016-04-26 16:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-23 22:35:52 UTC
Embargoed:


Attachments (Terms of Use)

Description cohoe 2012-08-07 16:58:04 UTC
Description of problem:
Attempting to "reset" (virDomainReset) a VM on an ESX 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: ESX 0.9.10
Running hypervisor: ESX 5.0.0

How reproducible:
Always

Steps to Reproduce:
1. Connect to ESXi host with virsh (esx://root@MYSERVERNAME?no_verify=1
2. Issue reset command 'reset 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:
Error shows up in both virsh and the Python API bindings.

Comment 1 cohoe 2012-08-09 13:07:43 UTC
This also affects library/API 0.9.13

Comment 2 Dave Allan 2012-08-09 14:02:32 UTC
I think your best bet for getting this functionality is to submit patches upstream, and I'm sure people will work with you to get them accepted.

Comment 3 Cole Robinson 2016-03-23 22:35:52 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


Note You need to log in before you can comment on or make changes to this bug.