This bug doesn't seem to have gotten much attention since July last year but I can report that the issue still exists on Karmic using libvirt-bin 0.7.0-1ubuntu13.1:
$ virsh reboot foo1
Connecting to uri: qemu:///system
error: Failed to reboot domain foo1
error: this function is not supported by the hypervisor: virDomainReboot
The stack trace printed by virt-manager says the same:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 523, in reboot_domain
vm.reboot()
File "/usr/share/virt-manager/virtManager/domain.py", line 554, in reboot
self.vm.reboot(0)
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 398, in reboot
if ret == -1: raise libvirtError ('virDomainReboot() failed', dom=self)
libvirtError: this function is not supported by the hypervisor: virDomainReboot
This bug doesn't seem to have gotten much attention since July last year but I can report that the issue still exists on Karmic using libvirt-bin 0.7.0-1ubuntu13.1:
$ virsh reboot foo1
Connecting to uri: qemu:///system
error: Failed to reboot domain foo1
error: this function is not supported by the hypervisor: virDomainReboot
The stack trace printed by virt-manager says the same:
Traceback (most recent call last): virt-manager/ virtManager/ engine. py", line 523, in reboot_domain virt-manager/ virtManager/ domain. py", line 554, in reboot vm.reboot( 0) python2. 6/dist- packages/ libvirt. py", line 398, in reboot
File "/usr/share/
vm.reboot()
File "/usr/share/
self.
File "/usr/lib/
if ret == -1: raise libvirtError ('virDomainReboot() failed', dom=self)
libvirtError: this function is not supported by the hypervisor: virDomainReboot
Anything we users can or should do here?