I would be very surprised for this to work, as I would expect nova-compute to destroy the VM which is not supposed to be there once it's started. On Mon, 17 Feb 2025, 18:23 Eugen Block, <eblock@nde.ag> wrote:
Since you're doing it with virsh directly, I would assume that the console.log should be owned by libvirt-qemu user (like the disk) and/or group kvm? I haven't tried it this way myself though, but probably worth a shot.
Zitat von engineer2024 <engineerlinux2024@gmail.com>:
I am testing vm migration manually using virsh from one compute node to another:
--- nova@ccompute:~$ virsh migrate instance-0003457f0 qemu+ssh://<remote-ip>/system --live --verbose --unsafe error: Unable to open file: /var/lib/nova/instances/f4d4r423r4d/console.log: No such file or directory
nova@ccompute:~$ ll /var/lib/nova/instances/f4d4r423r4d/ drwxr-xr-x 2 nova nova 4096 Feb 17 15:43 ./ drwxr-xr-x 14 nova nova 4096 Dec 16 22:31 ../ -rw------- 1 nova root 56864 Feb 17 15:43 console.log -rw-r--r-- 1 libvirt-qemu kvm 1154624 Feb 17 15:35 disk -rw-r--r-- 1 nova nova 79 Dec 16 22:30 disk.info ------ I am doing the above as 'nova' user. Why is it failing even though it has r/w access to the console file ?
Thanks elinux