From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lcaron@unix-scripts.info>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id D0B9B84E7
 for <pve-user@lists.proxmox.com>; Wed, 21 Jun 2023 15:03:31 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id B1BA51DA4F
 for <pve-user@lists.proxmox.com>; Wed, 21 Jun 2023 15:03:01 +0200 (CEST)
Received: from mail.unix-scripts.info (mail.unix-scripts.info [46.21.115.223])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by firstgate.proxmox.com (Proxmox) with ESMTPS
 for <pve-user@lists.proxmox.com>; Wed, 21 Jun 2023 15:03:01 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by mail.unix-scripts.info (Postfix) with ESMTP id E210B3A0B98
 for <pve-user@lists.proxmox.com>; Wed, 21 Jun 2023 15:03:00 +0200 (CEST)
Received: from mail.unix-scripts.info ([127.0.0.1])
 by localhost (venus.unix-scripts.info [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id Mym3WfCrRiGg for <pve-user@lists.proxmox.com>;
 Wed, 21 Jun 2023 15:03:00 +0200 (CEST)
Received: from [IPV6:2a02:27d0:0:5e0d:da9e:f3ff:fe2d:48ca] (unknown
 [IPv6:2a02:27d0:0:5e0d:da9e:f3ff:fe2d:48ca])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by mail.unix-scripts.info (Postfix) with ESMTPSA id CB8603A089C
 for <pve-user@lists.proxmox.com>; Wed, 21 Jun 2023 15:03:00 +0200 (CEST)
Message-ID: <1bbf6a07-8592-6608-40cf-4c4e8578cee3@unix-scripts.info>
Date: Wed, 21 Jun 2023 15:03:00 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.12.0
Content-Language: fr
To: Proxmox VE user list <pve-user@lists.proxmox.com>
References: <91e589fd-0811-b2ba-98e8-b78fcc21e8bd@unix-scripts.info>
 <528533255.585.1687350936401@webmail.proxmox.com>
From: Laurent CARON <lcaron@unix-scripts.info>
In-Reply-To: <528533255.585.1687350936401@webmail.proxmox.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.092 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 KAM_INFOUSMEBIZ 0.75 Prevalent use of
 .info|.us|.me|.me.uk|.biz|xyz|id|rocks|life domains in spam/malware
 NICE_REPLY_A           -0.102 Looks like a legit reply (A)
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
 T_SCC_BODY_TEXT_LINE    -0.01 -
Subject: Re: [PVE-User] Network device name change (with systemd) under
 debian after adding/removing line meta: from config file
X-BeenThere: pve-user@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE user list <pve-user.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-user/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Wed, 21 Jun 2023 13:03:31 -0000

Thanks for the pointer Fabian. This is exactly it.


Laurent

Le 21/06/2023 à 14:35, Fabian Grünbichler a écrit :
> there was a change in how Qemu sets up PCI slots. we record the version with which the VM was first created exactly to avoid this change during the lifetime of the VM:
>
> https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=cc1810363579b8d6bf7dd8d681b831f33209bbb0
>
>> Laurent CARON <lcaron@unix-scripts.info> hat am 21.06.2023 14:22 CEST geschrieben:
>>
>>   
>> Hi,
>>
>> I'm experiencing a rather strange behavior with VM creation on a 7.7
>> proxmox cluster.
>>
>> I do have quite old (migrated from older proxmox versions) VMs as well
>> as new VMs (created after the 7.2 version).
>>
>> Config file:
>>
>> $ cat /etc/pve/qemu-server/889.conf
>> boot: order=virtio0;ide2;net0
>> cores: 1
>> cpu: host
>> ide2: none,media=cdrom
>> machine: q35
>> memory: 2048
>> meta: creation-qemu=7.0.0,ctime=1687340877
>> name: vs-lcaron-testalacon
>> net0: virtio=C2:B9:B3:FE:6C:B0,bridge=vmbr2000
>> numa: 1
>> ostype: l26
>> scsihw: virtio-scsi-pci
>> smbios1: uuid=ef269cd3-e7a6-442e-87ad-30b68741003b
>> sockets: 1
>> virtio0: VMs_NFS:889/vm-889-disk-0.qcow2,discard=on,size=64G
>> vmgenid: ac09af11-7012-41eb-99e3-ca1162afc2bd
>>
>> Using this config, VM installs fine.
>>
>> Interface name is enp6s18
>>
>> If I do remove the line 'meta: ...' from the config file, and restart
>> the VM's interface is now ens18.
>>
>> Please note, when using 'meta: ...' lspci | grrp Ethernet is:
>>
>> 06:12.0 Ethernet controller: Red Hat, Inc. Virtio network device
>>
>> When not using 'meta: ...' lspci is exactly the same.
>>
>>
>> What is changing behind the scenes when using 'meta: ' in the config file ?
>>
>>
>> I'm trying to have a consistent naming across VMs, wether the VMs were
>> instanciated on an old or a new proxmox version.
>>
>> Thanks
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user