惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

C
Check Point Blog
美团技术团队
Microsoft Security Blog
Microsoft Security Blog
大猫的无限游戏
大猫的无限游戏
T
Tailwind CSS Blog
G
Google Developers Blog
博客园 - 聂微东
爱范儿
爱范儿
博客园 - 叶小钗
J
Java Code Geeks
月光博客
月光博客
博客园 - Franky
MongoDB | Blog
MongoDB | Blog
The Cloudflare Blog
宝玉的分享
宝玉的分享
博客园 - 【当耐特】
Microsoft Azure Blog
Microsoft Azure Blog
The GitHub Blog
The GitHub Blog
小众软件
小众软件
WordPress大学
WordPress大学
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Vercel News
Vercel News
Y
Y Combinator Blog
量子位

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
Change machine type from i440fx to q35
invalid@exam · 2024-03-02 · via Proxmox Support Forum

Hi, just tried to change the machine type to q35 but cannot get ip configurations after that and the boot stuck at :

Code:

A start job is running for wait for network to be configured

My network configuration on hardware is virtio bridged to vmbr1 and the OS is Ubuntu 22.04.

When trying to change the machine back to i440fx everything works OK. Why i happens?

q35 is a different virtual mother chipset, if your ubuntu is using predictable nic name, based on pci address,

it's really possible that the nic name have change.

maybe remove the nic first, reboot on q35, then readd the nic.

When the machine type is changed from i440FX to Q35 in Proxmox, it can lead to a change in the naming convention of the network interfaces. The interface name shifts from a traditional naming schema like ens18 to a predictable naming schema such as enp6s18.
This change can prevent the operating system (in my personal case, Ubuntu LTS) from correctly recognizing and configuring the network interface, ultimately resulting in the VM being unable to obtain an IP address.

I solved the issue by changing the interface name in the netplan configuration from ens18 to enp6s18. After identifying the new interface name using the command ip a, I updated the YAML file in /etc/netplan/ and applied the changes with sudo netplan apply. This allowed Ubuntu to recognize the network interface and obtain the correct IP address.