public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Lendl <s.lendl@proxmox.com>
To: Fabrizio Cuseo <f.cuseo@panservice.it>,
	Proxmox VE user list <pve-user@lists.proxmox.com>,
	pve-user <pve-user@pve.proxmox.com>
Subject: Re: [PVE-User] qm remote-migrate
Date: Wed, 11 Oct 2023 09:41:17 +0200	[thread overview]
Message-ID: <87jzrtip2a.fsf@gmail.com> (raw)
In-Reply-To: <1200893807.110513.1696964512431.JavaMail.zimbra@zimbra.panservice.it>

Fabrizio Cuseo <f.cuseo@panservice.it> writes:

Hello Fabrizio,

To better understand your issue, the source cluster has a VM with a
bridge with a VLAN tag assigned and the target cluster does not have the
same setup but uses SDN (vnet) without vlan.

After migration you manually changed the VMs configuration to match the
new setup?

What SDN configuration are you using on the traget cluster?
Please send the output of the following:

head -n -1 /etc/pve/sdn/*.cfg

What was to exact command you ran to start the remote-migrate process?

Did you notice any suspicios log messages in the source clusters
journal?

Usually I would ask you to send me the entire journal but this is not
feasible on the mailing list. If necessary, I would recommend you open a
Thread in our community forum and I will take a look there.

https://forum.proxmox.com/

Best regards,
Stefan Lendl

> 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




  parent reply	other threads:[~2023-10-11  7:41 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
2023-10-11  7:41 ` Stefan Lendl [this message]
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=87jzrtip2a.fsf@gmail.com \
    --to=s.lendl@proxmox.com \
    --cc=f.cuseo@panservice.it \
    --cc=pve-user@lists.proxmox.com \
    --cc=pve-user@pve.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal