Recent content by shukko

Hello Your disk is now using virtio0 Select this disk and click detach from the top then double click the unused disk which will be on bottom of the hardware list and reattch it using scsi (default option)

Hey My problem is now solved! Solution: Switch all disks to Virtio SCSI from Virtio. detach disk from vm and reattach using SCSI Setup new boot order for SCSI Out of 20 KVM virtual Servers all running Centos 6 only one server suffered some minor data loss. But restored. No problems with...

here is a new screenshot

root@r5:~# pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve) pve-manager: 7.1-5 (running version: 7.1-5/6fe299a0) pve-kernel-5.13: 7.1-4 pve-kernel-helper: 7.1-4 pve-kernel-5.4: 6.4-7 pve-kernel-5.13.19-1-pve: 5.13.19-2 pve-kernel-5.4.143-1-pve: 5.4.143-1 pve-kernel-5.4.73-1-pve...

After upgrading to several proxmox 6 boxes to proxmox 7.1 I've got exactly the same problem. but only on centos 6 KVM virtual machines. Centos 7 and Centos 8 / AlmaLinux 8 KVM Virtual servers are not having this problem. Centos 7 KVM Virtual Servers Going into Read Only randomly after giving...

do NOT use LXC. LXC is NOT OpenVZ alternative. LXC s NOT OpenVZ successor. LXC is not a true container system. - Lacks tons of features and depends on tons of ubuntu apparmor crap. Use KVM if possible. Or do NOT upgrade your proxmox 3.x Installations to 4.x LXC is a useless, untested...

Being not alone makes me happy, but as always not a solution to "our" problems. what can be done ? what is the solution ? I don't want to get rid of openvz, but I also want to use Proxmox 4.x. I can not find any other alternatives to this beautiful Proxmox we have... That is %100 true for me...

OpenVz Is always the unwanted adopted child of Proxmox from the beginning. Proxmox developers want to get rid of it from the first day. Now with the new 4.x series they replaced it with LXC without thinking and testing any much further. There are tons and tons of problems with LXC. OpenVZ have...

this is me :) Thank you for your kind words, shukko.com is my notepad so that's why comments are always closed. I am very happy that you like my tutorial. I've got around 30+ servers working in that configuration, so yes it is well tested and recommended. Thank you again :)

http://forum.proxmox.com/threads/19675-Fresh-install-of-PVE-3-2-won-t-boot-best-work-around?p=100161#post100161

8x1TB SATA Production server. root@pmd03:~# lspci -vvv | grep Adaptec 01:00.0 RAID bus controller: Adaptec Series 6 - 6G SAS/PCIe 2 (rev 01) Subsystem: Adaptec Series 6 Entry Level - ASR-6805E - 8 internal 6G SAS ports root@pmd03:~# pveperf CPU BOGOMIPS: 32001.04 REGEX/SECOND...

I have git a problem with one of my openvz containers I've set the disk to 25GB on proxmox: /etc/pve/openvz/144.conf as you can see everything os ok. BUT, a df -h from host node: as you can see container 144 have full host node disk and inside container again full host node disk...

Exact same thing happened to me twice. UEFI H97 Chipset mobo + proxmox 3.2 does not boot, whatever I did tried. The best way to fix this is Install Proxmox 3.1 and upgrade it after installation. Everything works as expected...

UPDATE on this subject: Server did have bad ram sticks. Pulling out the bad sticks worked. Server is now fully functional.

I get random kernel panic's at this specific server. below is a screenshot. anybody have an idea why?