From: Fabrizio Cuseo <f.cuseo@panservice.it>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] qm remote-migrate
Date: Wed, 11 Oct 2023 07:32:29 +0000 (UTC) [thread overview]
Message-ID: <1095727920.145819.1697009549240.JavaMail.zimbra@zimbra.panservice.it> (raw)
In-Reply-To: <1200893807.110513.1696964512431.JavaMail.zimbra@zimbra.panservice.it>
PS: I'm checking the qm.pm code, and I have found that I miss an (undocumented ?) option "delete", otherwise vm remains stopped on the source cluster (but "migrating locked").
I can't found any option to specify the vlan-tag mapping on destination cluster, where I am using sdn.
Some comment ?
Thanks, Fabrizio
----- Il 10-ott-23, alle 21:01, Fabrizio Cuseo f.cuseo@panservice.it ha scritto:
> Hello.
> I am testing qm remote-migrate with 2 pve 8.0.4 clusters.
> Source cluster has one bridge with vlan id on every VM, destination cluster uses
> SDN and a different bridge (vnet) without vlanid.
> If I migrate the vm, i need to specify both bridge and vlan-id, but I have not
> found an option to do it.
>
> PS: after migration, on the new cluster the vm is running without any problem,
> but on source cluster remains locked and in migration, so I need to issue a "qm
> unlock vmid" and stop/delete it.
>
> I know that is an experimental feature, so I send my test results.
>
> Regards, Fabrizio
>
>
> --
> ---
> Fabrizio Cuseo - mailto:f.cuseo@panservice.it
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
--
---
Fabrizio Cuseo - mailto:f.cuseo@panservice.it
next prev parent reply other threads:[~2023-10-11 7:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 19:01 Fabrizio Cuseo
2023-10-11 7:32 ` Fabrizio Cuseo [this message]
2023-10-11 7:41 ` Stefan Lendl
2023-10-11 7:55 ` Fabrizio Cuseo
2023-10-11 9:37 ` Stefan Lendl
2023-10-11 10:14 ` Fabrizio Cuseo
2023-10-11 16:06 ` DERUMIER, Alexandre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1095727920.145819.1697009549240.JavaMail.zimbra@zimbra.panservice.it \
--to=f.cuseo@panservice.it \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox