VM is loosing connection

P

Paul01

Member
Jan 13, 2018
11
1
8
28
Hello guys,

i have a huge problem with a VM.
I virualisize kvm.

There is one vm which is random loosing all connections.
I can't ping. I can't shutdown viva Proxmox webinterface, every action get's an timeout. I can't shutdown viva Putty.
I only can kill it and restart it on the webinterface.
After that the server is getting online and everything works until - i dont know - a random thing happens.

Which logs i can icheck?

Thats the only VM.
Networkconfig is the same as on other vms.

Just let me know which logs i can check. It would help me so much.

Thanks!
 
Hello and welcome on PVE :)

So you can't also open the konsole in Proxmox on that VM?
Please give us a bit more information.
Your Proxmoxversion:
Code: 
pveversion -v
Your VMconfiguration:
Code: 
qm config <vmid>
Your Proxmox network configuration:
Code: 
cat /etc/network/interfaces
 
  • Like
Reactions: Paul01
fireon said:
Hello and welcome on PVE :)

So you can't also open the konsole in Proxmox on that VM?
Please give us a bit more information.
Your Proxmoxversion:
Code: 
pveversion -v
Your VMconfiguration:
Code: 
qm config <vmid>
Your Proxmox network configuration:
Code: 
cat /etc/network/interfaces
Click to expand...

At first, thank you! :)

So you can't also open the konsole in Proxmox on that VM?
Click to expand...
Yeah thats right.

proxmox-ve: 4.2-58 (running kernel: 4.4.13-2-pve)
pve-manager: 4.2-17 (running version: 4.2-17/e1400248)
pve-kernel-4.4.13-2-pve: 4.4.13-58
pve-kernel-4.2.8-1-pve: 4.2.8-41
lvm2: 2.02.116-pve2
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-43
qemu-server: 4.0-85
pve-firmware: 1.1-8
libpve-common-perl: 4.0-71
libpve-access-control: 4.0-18
libpve-storage-perl: 4.0-56
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6-1
pve-container: 1.0-71
pve-firewall: 2.0-29
pve-ha-manager: 1.0-33
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5.7-pve10~bpo80

bootdisk: ide0
cores: 4
ide0: local:105/vm-105-disk-1.qcow2,size=100G
ide2: local:iso/debian-8.7.1-amd64-netinst.iso,media=cdrom
memory: 9000
name: VM105
net0: e1000=02:00:00:78:7b:5d,bridge=vmbr0
numa: 0
ostype: l26
parent: Clean
smbios1: uuid=5652d751-6542-423d-b3f2-b511ebf7a149
sockets: 2


# The loopback network interface
auto lo
iface lo inet loopback

# for Routing
auto vmbr1
iface vmbr1 inet manual
post-up /etc/pve/kvm-networking.sh
bridge_ports dummy0
bridge_stp off
bridge_fd 0


# vmbr0: Bridging. Make sure to use only MAC adresses that were assigned to you.
auto vmbr0
iface vmbr0 inet static
address 188.165.xxx.212
netmask 255.255.255.0
network 188.165.xxx.0
broadcast 188.165.xxx.255
gateway 188.165.xxx.254
bridge_ports eth0
bridge_stp off
bridge_fd 0

iface vmbr0 inet6 static
address 2001:41dX:X:b0d4::
netmask 64
post-up /sbin/ip -f inet6 route add 2001:41dX:X:b0ff:ff:ff:ff:ff dev vmbr0
post-up /sbin/ip -f inet6 route add default via 2001:41dX:X:b0ff:ff:ff:ff:ff
pre-down /sbin/ip -f inet6 route del default via 2001:41dX:X:b0ff:ff:ff:ff:ff
pre-down /sbin/ip -f inet6 route del 2001:41dX:X:b0ff:ff:ff:ff:ff dev vmbr0

Thanks for ur help!
 
Ok. For the first overview it look likes ok. But your system is not up do date. So when possible, please update.
Second: Your VMsettings are not optimal.

Change your network to "virtio".
Change your harddrive do SCSI
Numa must be enabled, you have two sockets!
Optional: install the qemu guest agent linux and make set the checkbox on pve to on

On every configuration there is a button for the documentation. Don't know, may be this is not on your version 4.2.
Example config from a testvm:
Code: 
agent: 1
boot: dc
bootdisk: scsi0
cores: 8
cpuunits: 1000
hotplug: disk,network,usb,memory
memory: 4096
name: xtest Ubuntu
net0: virtio=DA:73:E1:12:A9:72,bridge=vmbr0
numa: 1
ostype: l26
parent: snap01
sata0: none,media=cdrom
scsi0: HDD-vmdata-KVM:base-112-disk-2/vm-100-disk-2,discard=on,size=42G
scsi1: HDD-vmdata-KVM:base-112-disk-1/vm-100-disk-1,discard=on,size=4G
scsihw: virtio-scsi-pci
smbios1: uuid=4844fe29-2b76-4dab-b8df-27caa2b30dd1
sockets: 1
vga: qxl
 
  • Like
Reactions: Paul01
fireon said:
Ok. For the first overview it look likes ok. But your system is not up do date. So when possible, please update.
Second: Your VMsettings are not optimal.

Change your network to "virtio".
Change your harddrive do SCSI
Numa must be enabled, you have two sockets!
Optional: install the qemu guest agent linux and make set the checkbox on pve to on

On every configuration there is a button for the documentation. Don't know, may be this is not on your version 4.2.
Example config from a testvm:
Code: 
agent: 1
boot: dc
bootdisk: scsi0
cores: 8
cpuunits: 1000
hotplug: disk,network,usb,memory
memory: 4096
name: xtest Ubuntu
net0: virtio=DA:73:E1:12:A9:72,bridge=vmbr0
numa: 1
ostype: l26
parent: snap01
sata0: none,media=cdrom
scsi0: HDD-vmdata-KVM:base-112-disk-2/vm-100-disk-2,discard=on,size=42G
scsi1: HDD-vmdata-KVM:base-112-disk-1/vm-100-disk-1,discard=on,size=4G
scsihw: virtio-scsi-pci
smbios1: uuid=4844fe29-2b76-4dab-b8df-27caa2b30dd1
sockets: 1
vga: qxl
Click to expand...

On the next "crash" i will test this 3 options
Code: 
Change your network to "virtio".
Change your harddrive do SCSI
Numa must be enabled, you have two sockets!

Top update proxmox i have to reboot the root?
Regards
 
fireon said:
Change your network to "virtio".
Change your harddrive do SCSI
Numa must be enabled, you have two sockets!
Optional: install the qemu guest agent linux and make set the checkbox on pve to on

[/CODE]
Click to expand...

Change your network to "virtio".
How can i do this?
I can only choose between 2 bridge's.

Change your harddrive do SCSI
So i have to format the harddrive?
 
fireon said:
Read the documentation by click at the help button in network properties (where you can change the bridge). There are all network model descriptions. Same on hardrive. Easy detach, and attach the disk with new bus. Be careful that you have your disk with uuid in the fstab.
https://forum.proxmox.com/threads/c...-a-existing-vm-disk-to-scsi-bus-device.39358/
German: https://forum.proxmox.com/threads/info-zu-virtio-scsi.31095/page-2#post-194593

BTW: Have you updated your system?
Click to expand...


Okey, thanks. I will have a look!

For now i changed the cpu settings. I think thats the cause for the crash.
We willl see..

I didn't update the system because at the moment there are to many running vm's.
I try to update soon!
 
  • Like
Reactions: fireon
You must log in or register to reply here.
Top Bottom