Hi!
I'm using Proxmox with the commandline and the Tool qm.
I can create, rollback and delete the Snapshots from the Qemu-Qcow2-image with
the qm command.
If I want to delete a existing snapshot, I go on the Place where the Image is
stored (look into the id.conf-File of the VM) and use the qemu-i
applied
> Dominik Csapak hat am 22. Juni 2016 um 09:33
> geschrieben:
>
>
> since we ship the same binaries as qemu-utils
> (such as qemu-nbd or qemu-img)
>
> Signed-off-by: Dominik Csapak
> ---
> debian/control | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/debia
just knowing that local disks prevent a migration is not
very helpful, so be a bit more verbose here.
---
PVE/QemuMigrate.pm | 19 +++
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/PVE/QemuMigrate.pm b/PVE/QemuMigrate.pm
index 1305b5c..3b861a5 100644
--- a/PVE/Qemu
and then die with more meaningful output, instead of on the
first encountered error.
---
PVE/QemuMigrate.pm | 64 --
1 file changed, 52 insertions(+), 12 deletions(-)
diff --git a/PVE/QemuMigrate.pm b/PVE/QemuMigrate.pm
index 2b383fa..6415032 10
this patch series has two main parts:
- mark local volumes with their origin (storage, snapshot or config) instead of
1
- test all local volumes and collect errors, then die with a complete error
message
instead of dying upon the first error
example output for a VM that exercises almost all the
to make log message more meaningful.
'storage' < 'snapshot' < 'config'
---
PVE/QemuMigrate.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PVE/QemuMigrate.pm b/PVE/QemuMigrate.pm
index 3b861a5..b72087b 100644
--- a/PVE/QemuMigrate.pm
+++ b/PVE/QemuMigrate.pm
@@ -302,12 +302,
---
PVE/QemuMigrate.pm | 20 +++-
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/PVE/QemuMigrate.pm b/PVE/QemuMigrate.pm
index b72087b..2b383fa 100644
--- a/PVE/QemuMigrate.pm
+++ b/PVE/QemuMigrate.pm
@@ -218,13 +218,15 @@ sub sync_disks {
my $conf = $self->{
