Displaying 20 results from an estimated 10000 matches similar to: "Re: Migrate to a bigger disk possible?"
2020 Apr 27
2
Re: Migrate to a bigger disk possible?
On Mon, Apr 27, 2020 at 10:13:37 +0200, Paul van der Vlis wrote:
> Op 27-04-2020 om 09:02 schreef Peter Krempa:
> > On Sat, Apr 25, 2020 at 16:40:35 +0200, Paul van der Vlis wrote:
> >> Op 25-04-2020 om 16:00 schreef Paul van der Vlis:
> >>> Hello,
> >>>
> >>> I have a qcow2 disk what needs to become increased.
> >>>
>
2020 Apr 27
0
Re: Migrate to a bigger disk possible?
Op 27-04-2020 om 10:41 schreef Peter Krempa:
> On Mon, Apr 27, 2020 at 10:13:37 +0200, Paul van der Vlis wrote:
>> A point is that I have to create disk(s) on the other side with
>> qemu-img, I did not found a way to do that automatically. My question
>
> We are able to pre-create the storage given that a full copy is
> requested (copy-storage-all, not copy-storage-inc)
2020 Jun 11
1
Re: Live migration to another volume at the same host
On Thu, Jun 11, 2020 at 05:45:46PM +0200, Paul van der Vlis wrote:
> Hello,
>
> I am looking for a way to migrate a VM live to another location.
>
> The qcow2 images are now on /data , but I want to move some of them to a
> volume mounted on /data2 what's faster.
>
> Is this possible without downtime?
Yes, you don't need to use live migration for this even.
The
2019 Feb 10
2
virsh migrate --copy-storage-inc
Hello,
I use libvirt on machines without shared storage. My VM's have all one
qcow2-disk, with the same name as the VM.
When I want to migrate a VM, I check if there is an qcow2 image on the
other host with that name. When that's not the case, I copy the image
using rsync first. If the image excist, I don't do that, and I think
that "--copy-storage-inc" will do it.
But I
2019 Feb 11
0
Re: virsh migrate --copy-storage-inc
On Sun, Feb 10, 2019 at 12:11:42 +0100, Paul van der Vlis wrote:
> Hello,
>
> I use libvirt on machines without shared storage. My VM's have all one
> qcow2-disk, with the same name as the VM.
>
> When I want to migrate a VM, I check if there is an qcow2 image on the
> other host with that name. When that's not the case, I copy the image
> using rsync first. If
2013 Jun 10
0
Re: virsh snapshot-create and blockcopy
On 06/10/2013 01:20 PM, Thomas Stein wrote:
> Am 10.06.13 09:07, schrieb Kashyap Chamarthy:
>> On 06/09/2013 02:46 PM, Thomas Stein wrote:
>>> Hello.
>>>
>>> I just tried the following:
>>>
>>> virsh dumpxml --security-info gentoo-template > gentoo-template.xml
>>> virsh snapshot-create gentoo-template
>>> virsh undefine
2013 Jun 10
1
Re: virsh snapshot-create and blockcopy
Am 10.06.13 10:40, schrieb Kashyap Chamarthy:
> On 06/10/2013 01:20 PM, Thomas Stein wrote:
>> Am 10.06.13 09:07, schrieb Kashyap Chamarthy:
>>> On 06/09/2013 02:46 PM, Thomas Stein wrote:
>>>> Hello.
>>>>
>>>> I just tried the following:
>>>>
>>>> virsh dumpxml --security-info gentoo-template > gentoo-template.xml
2015 Jan 08
2
Re: Using virsh blockcopy -- what's it supposed to accomplish?
On 01/08/2015 12:44 PM, Gary R Hook wrote:
> I've learned how to use the blockcopy command to create a local copy in
> a simple disk file:
>
> virsh dumpxml my_domain > my_domain.xml
> virsh undefine my_domain
> virsh blockcopy --domain my_domain vda $PWD/dsk.copy.qcow2 --wait
> --verbose --finish
> virsh define my_domain.xml
>
> and the resulting copy in
2014 Feb 05
0
Re: Can I move the disk image of the guest while it is running?
On 02/05/2014 02:54 PM, Gergely Horváth wrote:
> Thank you Eric,
>
> On 2014-02-05 17:23, Eric Blake wrote:
>> Yes, live storage migration is possible; although at the moment, qemu is
>> lacking a way to restart the operation if it fails midstream, so libvirt
>> only allows the operation if you are willing to temporarily make your
>> guest transient.
>
>
2013 Jun 10
2
Re: virsh snapshot-create and blockcopy
Am 10.06.13 09:07, schrieb Kashyap Chamarthy:
> On 06/09/2013 02:46 PM, Thomas Stein wrote:
>> Hello.
>>
>> I just tried the following:
>>
>> virsh dumpxml --security-info gentoo-template > gentoo-template.xml
>> virsh snapshot-create gentoo-template
>> virsh undefine gentoo-template
>
> Wait - is that really the command you used after
2015 Jan 08
0
Re: Using virsh blockcopy -- what's it supposed to accomplish?
On 12/24/14 4:42 AM, Kashyap Chamarthy wrote:
> On Tue, Dec 23, 2014 at 12:38:57PM -0600, Gary R Hook wrote:
>
> [. . .]
>
> In my case, the block device is a QCOW2 disk image file. If I boot
> without using the disk image file which has the operating system, the
> domain will fail to boot, no?
>
> I see you're playing with NBD disks. I'll admit, I haven't
2015 May 19
0
Re: Pivot without copy
On 05/19/2015 12:52 PM, Mathew Moon wrote:
> Hi,
>
> Is it possible to "pivot" to a new image without doing blockcopy or
> blockpull?
No. Qemu does not support arbitrary reopening of a backing chain yet
(even with the 'change-backing-file' QMP command, that is just rewriting
contents of the qcow2 metadata, and not actually reopening the chain).
The only way to pivot
2015 Jan 08
2
Re: Using virsh blockcopy -- what's it supposed to accomplish?
On Thu, Jan 08, 2015 at 01:44:58PM -0600, Gary R Hook wrote:
> On 12/24/14 4:42 AM, Kashyap Chamarthy wrote:
> >On Tue, Dec 23, 2014 at 12:38:57PM -0600, Gary R Hook wrote:
> >
> >[. . .]
> >
> >In my case, the block device is a QCOW2 disk image file. If I boot
> >without using the disk image file which has the operating system, the
> >domain will fail
2014 Jul 03
0
Re: virsh blockcopy: doesn't seem to flatten the chain by default
On 07/03/2014 03:12 AM, Kashyap Chamarthy wrote:
> Versions
> --------
>
> (Libvirt locally built from a recent git commit -ec7b922):
>
> $ rpm -q libvirt-daemon-kvm qemu-system-x86
> libvirt-daemon-kvm-1.2.6-1.fc20.x86_64
> qemu-system-x86-2.0.0-1.fc21.x86_64
>
>
> Test
> ----
>
> [All images are qcow2 files.]
>
>
> We have this
2015 Jan 09
0
Re: Using virsh blockcopy -- what's it supposed to accomplish?
On 1/8/15 2:21 PM, Kashyap Chamarthy wrote:
>> qemu-img create -f qcow2 /tmp/dsk.test.qcow2
>
> A typo? You also need to provide a size here:
>
> $ qemu-img create -f qcow2 /tmp/dsk.test.qcow2 1G
Yes, my mistake. The size is set to the potential size of the source
disk, which in this case is 20G.
> For the rest, I'm afraid I still didn't manage time to test
2014 Feb 06
2
Re: Can I move the disk image of the guest while it is running?
----- Original Message -----
> From: "Eric Blake" <eblake@redhat.com>
> To: "Gergely Horváth" <gergely.horvath@inepex.com>, libvirt-users@redhat.com
> Sent: Wednesday, February 5, 2014 4:47:47 PM
> Subject: Re: [libvirt-users] Can I move the disk image of the guest while it is running?
>
> On 02/05/2014 02:54 PM, Gergely Horváth wrote:
> >
2014 Jul 22
2
Problem about Disk Dize of Destination and Source File after Do Blockcopy
Hi There,
There is a case I met about the destination file's disk size after do
blockcopy
Details as below:
Env:
# rpm -q libvirt qemu-kvm-rhev
libvirt-1.1.1-29.el7.x86_64
qemu-kvm-rhev-1.5.3-60.el7ev_0.2.x86_64
1. Check source file
# qemu-img info /var/lib/libvirt/images/rhel6.img
image: /var/lib/libvirt/images/rhel6.img
file format: qcow2
virtual size: 5.0G (5368709120 bytes)
disk
2015 May 19
0
Re: Pivot without copy
It seems that my version of libvirt does not support the flags that yours
does either. I have the latest version from the Ubuntu repos and am running
14.04. What version are you running and do you know if these features
depend on libvirt, or qemu-img to be upgraded?
=============================================================================================
2013 Jun 10
0
Re: virsh snapshot-create and blockcopy
On 06/09/2013 02:46 PM, Thomas Stein wrote:
> Hello.
>
> I just tried the following:
>
> virsh dumpxml --security-info gentoo-template > gentoo-template.xml
> virsh snapshot-create gentoo-template
> virsh undefine gentoo-template
Wait - is that really the command you used after "snapshot-create" ?
Because: You cannot undefine a guest with a snapshot without
2014 Jul 02
0
Re: virsh blockcopy: doesn't seem to flatten the chain by default
On Thu, Jul 03, 2014 at 12:42:20AM +0530, Kashyap Chamarthy wrote:
[. . .]
Forgot to note: Before blockcopy, the current block device is
snap1.qcow2 (after too, it's the same, since we didn't `--pivot` to the
copy.
> Now, let's do a live blockcopy (with a '--finish' to graecully finish
> the mirroring):
>
> $ virsh blockcopy --domain testvm2 vda \
>