Displaying 20 results from an estimated 20000 matches similar to: "Disk-only internal snapshot"
2014 Jul 10
1
snapshot-create error
Hi,
What's the difference between QEMU snapshot and libvirt snapshot?
# qemu-img create -f qcow2 disk.img 512
Formatting 'disk.img', fmt=qcow2 size=512 encryption=off cluster_size=65536 lazy_refcounts=off
# qemu-img info disk.img
image: disk.img
file format: qcow2
virtual size: 512 (512 bytes)
disk size: 136K
cluster_size: 65536
Format specific information:
compat: 1.1
lazy
2013 Sep 20
2
Re: Incremental Backups
On 2013-09-20 15:41, Davide Guerri wrote:
> Hi Thomas,
Hello Davide.
> I'm using this script which leverages external snapshots and
> blockpull: https://github.com/dguerri/LibVirtKvm-scripts
Yeah. I saw that and tried this already. But it needs to be adjusted to
libvirtd-1.1.2 i think. Can you do this? I fiddled a litte bit around
but wasn't realy successfull.
hn
2013 Mar 04
1
Live external snapshot coalescing
On standard Fedora 18 I was attempting blockcommit on a *live* VM,
libvirt said it was not supported, so I tried fedora-virt-preview as
recommended.
We found a problem with qemu 1.4, there seems to be an acknowledged bug,
a missing library.
On a different system we loaded Fedora 18, and then pulled qemu (1.3)
and libvirt (1.0.2) from rawhide.
I tried blockcommit with domain shut down, it said
2019 May 15
1
domain still running although snapshot-file is deleted !?!
Hi,
i have a strange situation:
A domain is still running where domblklist points to a snapshot file and also dumpxml says the current drive is that snapshot file.
But the file has been deleted hours ago. And the domain is still running. I can login via ssh, the database and the webserver are still running,
domain is performant.
How can that be ?
Also lsof shows that the file is deleted:
2017 Jun 22
4
recovering from deleted snapshot
I have an automatic process setup. It's still pretty new and obviously
in need of better error handling because now I find myself in a bad state.
I run snapshot-create-as across all my vms, then do zfs replication to
the target backup system, then blockcommit everything.
virsh snapshot-create-as --domain $vm snap --diskspec
$DISK,file=$VMPREFIX/"$vm"-snap.qcow2 --disk-only --atomic
2015 Sep 11
2
Backup a VM (using live external snapshot and blockcommit)
Hi.
I'm following here a conversation that was initiated on Kashyap's
website [1].
We have a server we use as a host for virtual machines using KVM
(virt-manager used for VM creation) and we would like to setup VM
backups. Basically, we're thinking of a backup schedule like "keep 7
daily and 4 weekly backups". We'd rather not shutdown the VM every day
so live backups
2013 Sep 20
1
Re: Incremental Backups
On 2013-09-20 16:05, Davide Guerri wrote:
> Hi
>
>> hn LibVirtKvm-scripts # ./fi-backup.sh -b /opt/virt-backup-local/ -d
>> serve.lordcritical
>> [DEB] qemu-img version '1.6.0' is supported
>> [DEB] KVM version '1.6.0,' is supported
>> [DEB] Snapshot for domain 'serve.lordcritical' requested
>> [DEB] Using timestamp
2012 Mar 19
16
LV resize encrypted volume
Hi,
dom0: Debian Lenny 2.6.26-2-xen-amd64, domU: same. Xen 3.2-1
After resizing a LV on dom0, Xen is not reporting the new extended size
to the PV domU even though dom0 is well aware of the new size. I''ve
rebooted domU (not dom0 yet as that''s running a lot of other domU''s).
The LV I tried to resize is encrypted. Resizing unencrypted volumes
works as expected.
dom0:~#
2015 Nov 24
2
Any risk in sparsifying a base image (that has a snapshot on top of it)
Assuming the VM is not running, and we have a base (raw, sparse) with a
snapshot (qcow2) on top of it.
Is there any issue with running virt-sparsify on the base image? I assume
deleted blocks in the base can be sparsified, since they are either still
deleted on the snap (which is fine) or were written in the snap (which is
fine either and does not change or matter for the base image).
Can I assume
2009 Aug 14
16
What''s eating my disk space? Missing snapshots?
Please can someone take a look at the attached file which shows the output on my machine of
zfs list -r -t filesystem,snapshot -o space rpool/export/home/matt
The USEDDS figure of ~2GB is what I would expect, and is the same figure reported by the Disk Usage Analyzer. Where is the remaining 13.8GB USEDSNAP figure coming from? If I total up the list of zfs-auto snapshots it adds up to about 4.8GB,
2017 May 31
1
Snapshot auto-delete unmount problem
Hi I am having a problem deleting snapshots, gluster is failing to unmount
them. I am running centos 7.3 with gluster-3.10.2-1
here is some log output:
[2017-05-31 09:21:39.961371] W [MSGID: 106057]
[glusterd-snapshot-utils.c:410:glusterd_snap_volinfo_find] 0-management:
Snap volume
331ec972f90d494d8a86dd4f69d718b7.glust01-li.run-gluster-snaps-331ec972f90d494d8a86dd4f69d718b7-brick1-b
not found
2012 May 25
1
Spawn new domains from a snapshot.
Hello everybody,
I would like to be able to spawn several domains from a given snapshot.
Here's a possible scenario:
- I start from disk image A.qcow2.
- I made some changes to A and I take different snapshots: 1 - 2 - 3
- While A is still running I would like to run domains B and C from snapshot 2
I don't want to revert a domain, I want to create new ones. The
original should be
2017 Nov 13
2
snapshot mount fails in 3.12
Hi,
quick question about snapshot mounting: Were there changes in 3.12 that
were not mentioned in the release notes for snapshot mounting?
I recently upgraded from 3.10 to 3.12 on CentOS (using
centos-release-gluster312). The upgrade worked flawless. The volume
works fine too. But mounting a snapshot fails with those two error messages:
[2017-11-13 08:46:02.300719] E
2011 May 16
1
(no subject)
Hi,
I am using libvirt and virsh for my application. I am trying to manage
snapshots for my infrastructure. All virsh commands are working fine like
snapshot-create, delete, list, revert, current.
But when I try to do the same using libvirt, I get out of memory error. Here
are the commands that i execute on my host in a python shell...
import libvirt
conn =
2017 Nov 13
0
snapshot mount fails in 3.12
Hi Richard,
Thanks for posting this.
This issues is caused as part of the regression in 3.12.0 version [1], and
is already fixed in 3.12.3 [2] version (3.12.3 is tagged now with couple of
more subdirectory mount related fixes).
[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1501235
[2] - https://review.gluster.org/#/c/18506/
If you don't want to change the versions, then please remove
2013 Sep 20
5
Incremental Backups
Hello.
Is someone performing incremental backups via libvirt for qemu/kvm
machines? I'm still having a hard time to
find a nice procedure. I mean is it possible to make a full backup of an
image on monday a do the next days of the week
incremental backups?
Another way could be mount the image and rsync its contents. Does that
makes sense?
Also i read in qemu changelog:
---
Support for a
2013 Feb 13
1
Changing QoS on-the-fly
Hi all,
it's possible to change/add the QoS settings for a running domain?
I edited the domain definition with virsh but it seems to have no effect until I shut down the domain.
libvirt version 0.9.13
kvm-qemu version 1.2.0
Best,
Davide.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5930 bytes
Desc:
2009 Sep 07
1
Problem with Samba 3.4 Franky: Internal Error starting Samba3
Hi all,
I got a problem while trying to set up a Samba 3.4 Server in hybrid-mode.
After trying for some time I managed doing a merged-build of Samba3 and
Samba4 and I can now start samba4 without getting errors. However, the
same is not true for Samba3: starting it, I get the below error message.
Has anyone an idea about what the reason could be? Did I miss anything
during build/setup?
2008 Apr 12
2
merge an lvm snapshot back
So how does one accomplish this if say the snap is now deemed the copy of interest? I am hoping dd is not the only answer:)
Thanks!
jlc
2002 Feb 04
1
LVM (1.0.2 ), ext3 and 'hot' snapshotting
Hello, all.
I work with lvm ( kernel 2.4.17 + ext3-2.4-0.9.17-2418p3 patch ) but i can't
snapshot a ext3 fs directly
# lvcreate --snap --name snap --size +1G /dev/vgtest/lvtest
# mount -o ro -t ext3 /dev/vgtest/lvtest /snap /mnt/snap
ext3 can't work , ext2 work
If I mount readonly the etx3 filesystem, snapshot-it, and remount rw the
filesystem ( and ro the snapshot ) it work