Sorry for the lack of information, my bad.
The snapshot is an internal one and the machine is running.
The whole thing was set-up by another person and left to me to cope with.
The typo is mine, as the machine is isolated I cannot actually copy-paste
it so have to do it in the traditional way.
re are the details:
I wrote this test script to snapshot and commit over and over:
#!/bin/sh
while [ 1 ]; do
echo "Starting snapshot test `date`"
virsh snapshot-create-as test 20150429 20150429-backup --disk-only
--atomic
virsh domblklist test
virsh blockcommit test vda --acti
On Wed, Apr 29, 2015 at 10:30:09AM -0600, Eric Blake wrote:
> On 04/29/2015 09:47 AM, Andreas Buschmann wrote:
> > Hello,
> >
> > I have two servers where I can push VMs from one to the other by issuing
> > the command
> >
> > virsh migrate --live --persistent --copy-storage-all --verbose \
> >
On 04/29/2015 10:30 AM, Eric Blake wrote:
>> Is there a way to just copy the data file over to the second server,
>> without moving the VM?
>> I want the equivalent of doing these two migrations is sequence, but
>> without moving the VM.
>
> Yes - 'virsh blockcopy' can be used for creating a live
On 04/29/2015 10:09 AM, Andreas Buschmann wrote:
> Hello,
>
> what is really the difference between
> virsh migrate --copy-storage-all
> and
> virsh migrate --copy-storage-inc
> ?
If you use qcow2 backing chains for thin provisioning, as in:
base.qcow2 <- active.qcow2
then --copy-storage-
On 04/29/2015 09:47 AM, Andreas Buschmann wrote:
> Hello,
>
> I have two servers where I can push VMs from one to the other by issuing
> the command
>
> virsh migrate --live --persistent --copy-storage-all --verbose \
> test6 qemu+ssh://kvmhost2/system
>
> on kvmhost1. I can get the VM
Hello,
what is really the difference between
virsh migrate --copy-storage-all
and
virsh migrate --copy-storage-inc
?
There are some documents talking about NBD snapshots, but the user
visible semantics are incomplete.
Where does the incremental stuff happen?
Does it require qcow2 files?
Do
Hello,
I have two servers where I can push VMs from one to the other by issuing
the command
virsh migrate --live --persistent --copy-storage-all --verbose \
test6 qemu+ssh://kvmhost2/system
on kvmhost1. I can get the VM back by issuing the equivalent command on
kvmhost2:
virsh migrate
On 04/29/2015 01:08 AM, NoxDaFox wrote:
> Greetings,
>
> due to hardware failure I had to replace my workstation which has a
> different CPU. I have a VM with several snapshots and I need to revert to a
> specific one.
>
> While reverting to it, I get an error due to unsupported CPU features.
> T
On Wed, Apr 29, 2015 at 01:26:31AM +, r...@openmailbox.org wrote:
> Hi. Is is possible to use GPG on the host instead of NSS with virtual
> smartcards? Please document how or add support for it.
>
> Can a virtual smartcard make the host less secure? If there are bugs in
> GPG/NSS backend on th
On Wed, Apr 29, 2015 at 10:08:54AM +0300, NoxDaFox wrote:
> Greetings,
>
> due to hardware failure I had to replace my workstation which has a
> different CPU. I have a VM with several snapshots and I need to revert
> to a specific one.
I'll assume these are external snapshots? You might want to
On Tue, Apr 28, 2015 at 01:16:52PM +0200, Matthias Fenner wrote:
> Dear libvirt team,
>
> we a currently in a pci-dss certification process and our security
> scanner found weak ciphers in the vlc_tls service on our centos6 box:
>
> When I scan using sslscan I can see that sslv3 and rc4 is accept
Greetings,
due to hardware failure I had to replace my workstation which has a
different CPU. I have a VM with several snapshots and I need to revert to a
specific one.
While reverting to it, I get an error due to unsupported CPU features.
Therefore, I try to edit the snapshot XML through the com
13 matches
Mail list logo
