On Mon, Sep 20, 2021 at 7:40 PM Krešimir Kovačević
<1943...@bugs.launchpad.net> wrote:
>
> Hi Christian,
>
> I agree. It works as expected.
> As you said it is stated on the man page that images must exist on same
> location on destination host.
>
> It just confused me because migration without im
Hi Christian,
I agree. It works as expected.
As you said it is stated on the man page that images must exist on same
location on destination host.
It just confused me because migration without image on destination host
really works in case of qcow2 image.
BR,
Krešimir
--
You received this bug
Hi Krešimir,
thanks for the clarifications!
To be clear the common setup is to use migration with some kind of
shared storage which can be anything from a clusterFS of any kind with
image files to a shared FCP infrastructure. Therefore while --copy* can
be handy it is not the common case and has s
Hi,
Sry. I did not post error message in original post.
c/p error :D
BR,
Krešimir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943847
Title:
virsh migrate with LVM volume as disk fails
To manag
Hi,
Attached you can find LVM and VM configurations.
I did post error message. It is:
"error: internal error: cannot precreate storage for disk type 'block'".
... and some good news:
As I described problem occurs when VM has raw disk backed by LVM.
In my test case it was "/dev/mapper/vg1-test--vm
Hi,
there is kind of a minefield of non-supported configuration options around this
so we might first need to clarify what exactly you use to get an idea -
depending on that we have to then search for a breaking change or fix OR otoh
might just report/discuss a feature request upstream.
Saying
