Search results

See https://forum.proxmox.com/threads/blue-screen-with-5-1.37664 Probably, if you update your kernel, the problem will be solved.

Is someone have test the last kernel? As they said in https://forum.proxmox.com/threads/blue-screen-with-5-1.37664/page-10 is seem resolve some problem, and hope that also our problem.... I will not be able to test it before almost 1 week (waiting for an new server)...

What a bad news... so the kernel is not the cause of problem :-(

In your host, do an qm list to obtain id of your VM and then qm config <VMID> (you had to change <VMID> to the real id number of your vm)

Great, I willl try to test is ASAP (For now I have servers in production and had to do some test in other server before apply it in these servers). If another one do the test, please give us feedback.... Thanks

How I downgrade kernel? I suppose also have to reboot each host after downgrade...

Of course : # pveversion -v proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve) pve-manager: 5.1-35 (running version: 5.1-35/722cc488) pve-kernel-4.13.4-1-pve: 4.13.4-25 libpve-http-server-perl: 2.0-6 lvm2: 2.02.168-pve6 corosync: 2.4.2-pve3 libqb0: 1.0.1-1 pve-cluster: 5.0-15 qemu-server...

Well, in our case, it's on an dell C6220 with 2 cpus E5-2650 in each 4 nodes that have enclosure, 64G of RAM in each nodes, 6 disks SSD kingston DC400 in RAID10 hardware, setup in LVM, proxmox 5.1 fresh install about 2 weeks. We have 5 or 4 VPS on each one, with cloudlinux/plesk, no more...

We are a lot of members yet with problem, it's posible that proxmox team investigate the cause of this?

Well, RAID0 with ZFS can work, but it's absolutely not recommended... Personally, I think that in case that there is no HBA or RAID card in it-mode, better go to hw raid with lvm... other setup can be an big problem in case of failure ...

There is yet various post about very similar problems : https://forum.proxmox.com/threads/vm-stuck-on-reboot.38138/ https://forum.proxmox.com/threads/vm-go-down-no-logs-no-error-message-in-console.38143/ No solution for now :-(

It's depend a lot if your RAID card is also HBA o can be flashed in it-mode. If not, you will not able to use this and probably had to create an HW RAID and go to LVM... This is the case that I have on other DELL server. LVM is probably a few worst, but seem the correct solution in these case.

Similar problem in https://forum.proxmox.com/threads/vm-go-down-no-logs-no-error-message-in-console.38143/ no solution for now...

Well, almost someone else that have similar problem! What I have not seen, is what you have do to solve it...

I join the only that I have... proxmox graph...

Still investigate the problem... As I have 5 servers of 20 with a few filesystem errors (I have move disk of someone and have few menor error), I try to reboot and repair one... On reboot it, CPU and RAM gone at 100% and KVM blocked... I had to do again an stop and an start, then I repair...

Today I have again this same problem with another VM in another node :-(. I have tried to change cpu type from "host" to "Default (kvm64)" and ad some more RAM to each VM (from 10G to 11,7G). I don't thinks that is an RAM problem, I am also not sure that cpu change will solve the problem as I...

Hello I have 5 VMs on an bi xeon ES5-2650 with 64G of RAM and RAID10 HW. One of them go down today, when I log into our proxmox, VM have state UP, but console still in black (no error, no message). I do an VM reset => no working, I do an stop, and then an start, and the VM go UP again. Have no...

About HA, I have not used it, so better that other give you an answer about this... About cluster, you create it on one node, and then, you can add nodes (1, 2 or more)...

1 - NO 2 - there is no relation between hardware and proxmox function 3 - https://pve.proxmox.com/wiki/Cluster_Manager