[libvirt-users] Fwd: Does virsh actually work?

Gary Hook garyrhook at gmail.com
Wed Sep 3 22:10:11 UTC 2014


On Wed, Sep 3, 2014 at 2:12 PM, Brian Rak <brak at gameservers.com> wrote:

>  Try creating a blank file on the target system at
> /mnt/store01/virt/e7f75b9b-9ed4-4f7e-aa86-e481ab911d6f.qcow2 on 'dewey'.
>

Yes, tried that before posting. At least, with a simple "touch" command.


> Migrations really don't go well when the target disk doesn't exist.  I'm
> not certain why this is, I think the migration feature was mainly built
> with shared storage in mind.
>

I appreciate that, but unless it's a documented and designed restriction,
it seems it oughta work.  And I know for a fact that it does (details which
I will not include here).

Thank you for your time; much appreciated.


> On 9/3/2014 3:05 PM, Gary Hook wrote:
>
> I have been beating my head against a wall attempting to get virsh to
> migrate a simple VM from one host to another.
>
>  I have two systems running Ubuntu 14.04 with libvirt 1.2.2. Yes, they
> are bridged. Non-shared storage. Modest guest VM that only requires 100G of
> disk space; there is far more available.
>
>  In trying to accomplish even the simplest migration (per every page I
> can find from both the Fedore Project and Red Hat) I consistently get the
> following results:
>
>  root at huey:/tmp# virsh list --all
>  Id    Name                           State
> ----------------------------------------------------
>  9     e7f75b9b-9ed4-4f7e-aa86-e481ab911d6f running
>  -     81c50b5a-24ef-47d5-88ae-16ee7f4f9537 shut off
>  -     acd06610-c919-450b-97c8-8e49b9a0d45c shut off
>
> root at huey:/tmp# virsh migrate --live --p2p
> e7f75b9b-9ed4-4f7e-aa86-e481ab911d6f qemu+ssh://10.10.11.204/system
> error: Failed to open file
> '/mnt/store01/virt/e7f75b9b-9ed4-4f7e-aa86-e481ab911d6f.qcow2': No such
> file or directory
>
> root at huey:/tmp# ls -al /mnt/store01/virt
> total 9140768
> drwxr-xr-x  2 libvirt-qemu kvm        4096 Sep  3 10:17 .
> drwxr-xr-x 13 root         root       4096 Aug 28 10:39 ..
> -rw-r--r--  1 libvirt-qemu kvm  3271688192 Aug 29 14:39
> 81c50b5a-24ef-47d5-88ae-16ee7f4f9537.qcow2
> -rw-r--r--  1 libvirt-qemu kvm  2523136000 Aug 29 14:47
> acd06610-c919-450b-97c8-8e49b9a0d45c.qcow2
> -rw-r--r--  1 libvirt-qemu kvm  3565486080 Sep  3 13:52
> e7f75b9b-9ed4-4f7e-aa86-e481ab911d6f.qcow2
>
> root at dewey:~ >ls -al /mnt/store01/virt
> total 8
> drwxrwxrwx  2 libvirt-qemu kvm  4096 Sep  3 12:30 .
> drwxr-xr-x 13 root         root 4096 Aug 29 16:36 ..
> root at dewey:~ >
>
>  (huey is 10.10.11.203, dewey is 10.10.11.204; DNS works, but I thought
> to eliminate that as a source of this problem.) As can be seen, the .qcow2
> files exists on the source system, and does not exist on the target system.
> The directory shown is where images are to be stored. There is no problem
> starting and stopping VMs on the systems. It is not at all clear where the
> failure is occurring; there is no documentation that discusses this
> failure, of course.
>
>  I believe that I am invoking a basic migration per every page I can find
> in a web search. Please correct any errors.
>
>  I am working as root on both systems, and use ssh to get from one system
> to another, no passwords, no authentication required. All works well.
>
>  Any observations, or suggestions as to what configuration parameters I
> should check, would be greatly appreciated.
>
>  Thank you.
>
>  Gary
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20140903/0b07eec2/attachment.htm>


More information about the libvirt-users mailing list