FOSS-Cloud / Bugs / #225 Backup: 21 (Can not copy state file to retain)

Beat Stebler - 2013-02-25

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Beat Stebler - 2013-02-25

Description has changed:

Diff:

--- old +++ new @@ -1,4 +1,4 @@ -Backups reject the following Error: +Backups return the following Error: 21 (Can not copy state file to retain)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

We could verify the bug.

Unfortunately the VM-Manager uses the wrong error-code => error-string mapping. The error number 21 is the following: CANNOT_RESTORE_MACHINE. So the problem is that the machine cannot be restored after the new disk image is created. The following lines are taken form the provisioning.log file:

Feb 25 16:35:37 foss-cloud-node-02 provisioning.pl[19015]: KVM:  Restoring machine 2ca6c09d-54b6-4550-949b-d09ccaf9e0ba from /var/virtualization/retain/vm-persistent/0f83f084-8080-413e-b558-b678e504836e/2ca6c09d-54b6-4550-949b-d09ccaf9e0ba/20130225T163500Z/2ca6c09d-54b6-4550-949b-d09ccaf9e0ba.state
Feb 25 16:35:58 foss-cloud-node-02 provisioning.pl[19015]: KVM:  Error from libvirt (38): libvirt says: Unable to read from monitor: Connection reset by peer.

The same error is thrown when you try to restore the machine manually using the virsh restore command:

foss-cloud-node-02 syslog-ng.conf.d # virsh restore /var/virtualization/retain/vm-persistent/0f83f084-8080-413e-b558-b678e504836e/2ca6c09d-54b6-4550-949b-d09ccaf9e0ba/20130225T163500Z/2ca6c09d-54b6-4550-949b-d09ccaf9e0ba.state
error: Failed to restore domain from /var/virtualization/retain/vm-persistent/0f83f084-8080-413e-b558-b678e504836e/2ca6c09d-54b6-4550-949b-d09ccaf9e0ba/20130225T163500Z/2ca6c09d-54b6-4550-949b-d09ccaf9e0ba.state
error: Unable to read from monitor: Connection reset by peer

Pat Kläy - 2013-02-25

assigned_to: Christian Wittkowski
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Christian Wittkowski - 2013-02-26

Don't know what the VM-Manager should do to prevent this

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Michael Eichenberger - 2013-02-27

This seems to be QEMU related bug. We are in the process of building a new release candidate with an updated libvirt and qemu version and we'll try to verify, if the bug still exists and still causes a segfault.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Michael Eichenberger - 2013-02-27

assigned_to: Christian Wittkowski --> Tiziano Müller

component: Unknown --> Operating-System
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Michael Eichenberger - 2013-03-01

status: open --> open-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Michael Eichenberger - 2013-03-01

The downgrade of qemu to version 1.3.1 fixed the problem.

foss-cloud-node-01 libvirt # qemu-kvm --version QEMU emulator version 1.3.1, Copyright (c) 2003-2008 Fabrice Bellard
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Backup: 21 (Can not copy state file to retain)

Build your own Cloud

Group

Searches

Help

#225 Backup: 21 (Can not copy state file to retain)

Discussion