similar to: Snapshots after 2002/08/01

(Shame on me: wrong filename in last posting, now here are correct diffs) in contrib/solaris/ (openssh-SNAP-20011017.tar.gz) 1) buildpkg.sh makes wrong link for /etc/init.d/opensshd 2) /etc/init.d/opensshd has not-working killproc here my version tested on Solaris 2.4 and 8 (no pgrep with solaris 2.4, XARGS was undefined, simpler syntax) J?rg --- contrib/solaris/buildpkg.sh Fri Oct 12

On 05/22/2014 04:31 PM, Andrew Martin wrote: > Hello, > [Can you convince your mailer to wrap long lines?] > I am working on a script to automatically create live snapshots of > running VMs using qemu-kvm 1.4.0 and libvirt 1.0.2. If a VM has Any reason you aren't upgrading to newer versions? Although these seem sufficient for what you are trying. > multiple disks, I'd

Hello! I am trying to create snapshots for sheepdog disks using libvirt API or virsh. The disk is defined in domain as follows: <disk type='network' device='disk'>       <driver name='qemu' cache='none'/>       <source protocol='sheepdog' name='sheepvol1'/>       <target dev='vdb' bus='virtio'/> </disk>

Hello! I am trying to create snapshots for sheepdog disks using libvirt API or virsh. The disk is defined in domain as follows: <disk type='network' device='disk'>       <driver name='qemu' cache='none'/>       <source protocol='sheepdog' name='sheepvol1'/>       <target dev='vdb' bus='virtio'/> </disk>

Hi All, Sorry, I do not know to reply the previous message directly, so I have to manually copy them here. I have two questions about the following issue? 1. I follow the instructions blew to migrate a vm with snapshots. When I perform 'virsh snapshot-create --redefine $dom file' on the destination.' I got an error saying that "no domain with matching name $dom". I'm

[dropping multiple lists; let's just use libvirt-users] On 02/11/2015 02:45 PM, Edward Young wrote: > I perform a simple test, but failed. > > In the source, I create: base <- mid <- active (2 snapshots, the active > one is the current one) > In order to migrate this vm to the destination, I manually copy both base > and mid to the destination, and put them in the

Hi, I want to take snapshots of a iSCSI devices from a target that hasn't snapshot/cloning capabilities (it's a Infortrend A16E storage array). What method are you using to make snapshots/clones of iSCSI targets using Open-iSCSI + CentOS? What about using Open-iSCSI + LVM snapshots system? For example: - Take a LVM snapshot in the initiator with "lvcreate". - Give read-only

Dear libvirt users, I'm stuck on this subject and would appreciate a working example as this looks a supported feature :) After many tries and packages backports, here is my current setup: qemu 2.5 libvirt 3.0 ceph hammer on Debian jessie. Here is the relevent domain xml parts: <disk type='network' device='disk' snapshot='internal'> <driver

On Tue, Aug 13, 2019 at 15:15:11 +0200, Petr Stodulka wrote: > Hi guys, > I had to move to the new laptop week ago and I screw migration of my virtual > machines. I recovered my virtual machines on the new laptop (virsh define) > using the backed up xml files, but I am missing any file with metadata about > snapshots. The original storage is cleaned so I cannot take these files >

On Wed, Jul 06, 2016 at 05:33:01PM +0300, Maxim Perevedentsev wrote: > Hello everyone! > > I have an issue with OpenSUSE-42.1 (I guess this is the only distro > with btrfs snapshots by default). > As we remember, list_filesystems returns btrfs snapshots along with devices. > > ><fs> list-filesystems > /dev/sda1: swap > btrfsvol:/dev/sda2/@: btrfs >

On 12/08/2014 03:03 PM, Laszlo Hornyak wrote: > Hi, > > I ran into a strange behavior with libvirt snapshots. I have some vms > running with thin-provisioned qcow2 disk images (libvirt 1.1.3 with fedora > 20). > * When I create a snapshot on the VM, the qcow file suddenly grows big, > somewhat bigger than the maximum size of the disk. The maximum (guest) size of a disk is

Hi Team, I have created a "External system checkpoint snapshot" using the following link. http://kashyapc.fedorapeople.org/virt/external-system-checkpoint-snapshot.txt The disk and ram snapshot has been created successfully. The disk snapshot have the QCOW2 file format,I tried to boot the disk snapshot (qcow2)file using the KVM but it throws the error *" No bootable disk

Thanks a lot for the detailed explanation. Currently I am taking a dump of the memory with the virsh dump ‘live’ flag and taking the snapshot with the memory file pointed to /dev/null, without even pausing the guest. I don’t have a use case to restore from the snapshot snapshot so hopefully this approach will not cause any issue. On Mon, 26 Nov 2018 at 5:23 PM, Peter Krempa

On 3/20/19 1:50 PM, Mircea Husz wrote: > I scripted the creation of snapshots and it works fine. Now I'd like to run the script as non-root. > > virsh snapshot-create-as --domain hq-live-v01 \ >      --name snappy \ >      --diskspec vda,file=/var/lib/libvirt/images/hq-live-v01.snappy,snapshot=external \ >      --diskspec

Currently, I've tried to move qemu VM image to a new computer. So, I copied VM image files in /var/lib/libvirt/images, VM xml files in /etc/libvirt/qemu, VM snapshot files in /var/lib/libvirt/qemu/snapshot to the same places at the new computer. Everything is OK except snapshot!! When I use "qemu-img info" for the copied VM image, I can see the snapshot list in the result as shown

On Mon, Mar 23, 2015 at 04:34:21PM +0200, NoxDaFox wrote: > Greetings, > > I have the following typical scenario: given one or more qcow2 base images > I clone them with COW and start the VMs. > > At a certain point I'd like to inspect them in order to see their evolution > compared to the known base images. To do so I was thinking about taking a > disk snapshot of

I've recently begun to try out LVM snapshots and I have 2 things I'm wondering about My intention is to run backups off the snapshot. As a first iteration, I left 15% of the disk for the snapshot LV. 1. The HOWTO instructions suggest that the snapshot is in effect as long as the snapshot LV exists, and use lvremove to disable the snapshot. Is this the proper way? 2. I chose 15%

Hi, I have a win10 guest on a fedora32 system and have some questions as I explore using external snapshots as a form of backup in case of a Windows failure (as in, it won't boot or is completely irrecoverable) as well as revision control (to be able to rollback changes after a failed app install, etc). The first hit on Google for external snapshots involves a RHEL7 document that talks

On Wed, Mar 20, 2019 at 15:48:43 -0500, Eric Blake wrote: > On 3/20/19 1:50 PM, Mircea Husz wrote: > > I scripted the creation of snapshots and it works fine. Now I'd like to run the script as non-root. > > > > virsh snapshot-create-as --domain hq-live-v01 \ > >      --name snappy \ > >      --diskspec

On 12/04/2013 08:29 AM, Juraj Melo wrote: > Thanks for your answer, [please don't top-post on technical lists, and use proper in-reply-to headers to keep things properly threaded] > > I am trying to make a snapshot of whole virtual machine (disk, CPU > state, memory). But I need to make this snapshot in matter of seconds. This is possible using external snapshots with memory,