Bug #4164
Imported Xen VMs can not be resumed after poweroff
Status: | Closed | Start date: | 11/17/2015 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | Carlos Martín | % Done: | 0% | |
Category: | Drivers - VM | |||
Target version: | Release 5.0 | |||
Resolution: | wontfix | Pull request: | ||
Affected Versions: | OpenNebula 4.14 |
Description
Error:
Tue Nov 17 12:12:27 2015 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/xen4/deploy '/home/jfontan/work/one/install-4.14.2/var//datastores/0/6/deployment.1' '10.3.3.88' 6 10.3.3.88 Tue Nov 17 12:12:27 2015 [Z0][VMM][I]: libxl: error: libxl_create.c:478:libxl__domain_make: domain creation fail Tue Nov 17 12:12:27 2015 [Z0][VMM][I]: libxl: error: libxl_create.c:743:initiate_domain_create: cannot make domain: -3 Tue Nov 17 12:12:27 2015 [Z0][VMM][I]: libxl: error: libxl.c:1384:libxl__destroy_domid: non-existant domain -1 Tue Nov 17 12:12:27 2015 [Z0][VMM][I]: libxl: error: libxl.c:1348:domain_destroy_callback: unable to destroy guest with domid 4294967295 Tue Nov 17 12:12:27 2015 [Z0][VMM][I]: libxl: error: libxl_create.c:1320:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation
VM is undefined after poweroff.
Associated revisions
Bug #4164: Remove poweroff action for kvm & xen imported VMs
Bug #4164: Remove poweroff action for kvm & xen imported VMs
(cherry picked from commit d369908da2c162d04132eb2c55fb5e26c99ed66d)
Revert "Bug #4164: Remove poweroff action for kvm & xen imported VMs"
This reverts commit d369908da2c162d04132eb2c55fb5e26c99ed66d.
bug #4164: Moved imported_vm_action logic to the driver class. Add
defaults for well-known drivers
History
#1 Updated by Ruben S. Montero over 5 years ago
- Target version set to Release 4.14.2
#2 Updated by Ignacio M. Llorente over 5 years ago
- Assignee set to Carlos Martín
#3 Updated by Ignacio M. Llorente over 5 years ago
- Target version changed from Release 4.14.2 to Release 5.0
#4 Updated by Hector Sanjuan over 5 years ago
I think it is nice to have a poweroff action for imported VMs. Of course, the user should be responsible of manually restarting the VMs as opennebula can't do anything about it. Opennebula just should adjust the state accordingly when they re-appear in the HV.
The problem right now is that, when performing an start action on an imported VM, opennebula copies the template a launches an empty machine.
#5 Updated by Javi Fontan about 5 years ago
- Status changed from Pending to Closed
- Resolution set to wontfix