All VM IPs not working after reboot server

vosvos

New Member
Jan 13, 2023
4
0
1
Hello

One of my proxmox server was running well with 5-7 VMs with Centos 6 and CentOS 7

But suddenly after reboot none IPs are working.

Any suggestions?

Thaks
 
Hi,

Can you post the network configuration of the mentioned node and one of the CentOS configs?
 
Hi,

Can you post the network configuration of the mentioned node and one of the CentOS configs?
Please Check the attachment.

CentOS 6.8 and CentOS 7 both same issue.
 

Attachments

  • noip.jpg
    noip.jpg
    261.4 KB · Views: 18
Hello,

Sorry, that I am not asked with detailed. I mean the network configuration of the PVE node cat /etc/network/interfaces, and one of the VM config qm config 104. Additionally, did you check the Syslog/journalctl when the node got reboot?
 
Hello,

Sorry, that I am not asked with detailed. I mean the network configuration of the PVE node cat /etc/network/interfaces, and one of the VM config qm config 104. Additionally, did you check the Syslog/journalctl when the node got reboot?

VM IP not working

qm config 104
boot: order=scsi0;ide2;net0
cores: 4
ide2: local:iso/CentOS-6.4-x86_64-minimal.iso,media=cdrom,size=350546K
memory: 16384
meta: creation-qemu=7.0.0,ctime=1666666667
name: VOS16GB36
net0: virtio=02:00:00:e6:ca:83,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
scsi0: local:104/vm-104-disk-0.qcow2,size=250G
scsihw: virtio-scsi-pci
smbios1: uuid=12489119-c9d6-40f8-b25c-8af7692cc050
sockets: 2
vmgenid: d24fbd66-a40d-4d23-9909-055e8159a8f1



But same OS CentOS 6.4, another VM still working on another proxmox server.
 

Attachments

  • 36.jpg
    36.jpg
    225.4 KB · Views: 6
Hello,

The network of the Proxmox VE server, not for the VM.
Please connect to your Proxmox VE via SSH or from the Web UI console, then issue `cat /etc/network/interfaces` command, to see the network configuration.
 
Hello,

The network of the Proxmox VE server, not for the VM.
Please connect to your Proxmox VE via SSH or from the Web UI console, then issue `cat /etc/network/interfaces` command, to see the network configuration.
cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto enp1s0f0
iface enp1s0f0 inet manual

auto enp1s0f1
iface enp1s0f1 inet manual

auto vmbr0
iface vmbr0 inet static
address 139.99.63.165/32
gateway 139.99.63.254
bridge-ports enp1s0f0
bridge-stp off
bridge-fd 0
hwaddress 3C:EC:EF:20:83:B8







Note: I have installed CentOS 6.10 on a new VM and IP working. But Cant make previous 4 VMs (All are CentOS 6.4) active.

VM 100

ifconfig
eth0 Link encap:Ethernet HWaddr 02:00:00:8D:8A:58
inet addr:15.235.188.36 Bcast:15.235.188.39 Mask:255.255.255.248
inet6 addr: fe80::ff:fe8d:8a58/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:32293 errors:0 dropped:0 overruns:0 frame:0
TX packets:3501 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2656301 (2.5 MiB) TX bytes:247711 (241.9 KiB)
 
The network configuration looks good to me. I would check the syslog when the VMs lose the network.

You can check the syslog using journalctl e.g:


Bash:
journalctl --since "2023-01-17 00:00" --until "2023-01-17 07:45" > /tmp/Syslog.log

You have to change the time/date in the above command.