Search results

Does your first boot order a CD? Try to change to HDD.

I have checked the grub content, look like it use ZFS. See attachment.

This is old server, I think it was not using zfs.

After run apt-get dist-upgrade then reboot, I got error: - Kernel Panic ... line 10: can't not open /etc/zfs/zfs-functions See image for details error. Any idea to fix this?

Look like your backed up VM < Proxmox 4.2, if so read this: https://forum.proxmox.com/threads/local-lvm-storage-and-vm-format.27209/

My Proxmox PHP code broken on new Server which run perfectly on my all Servers. I just know the bug after I read your post, thanks.

FYI, not always 100 GB. The size depend on your Disk, when you have 120 GB Disk then local volume around 50 GB.

With 1000 webs better to use 4 x Server with SSD. But you need to add additional big SATA for CPanel backup. Support you make weekly backup then you must provide enough space for 5 x week in a month (suppose you retain 31 days backup).

Yes. that's right. Just stop the new VM before overwrite with your existing qcow2.

Better you post both /etc/network/interfaces so we can see exactly the config there. Make sure no pending interface setting on Proxmox UI.

LXC no need this options.

I don't think so, with Image Based you will: Can not browse VPS to copy/rename/delete/move file Can not directly copy/rename/delete/move file between host and VPS If you need Image Base then you can use KVM instead -- that's why we use OpenVZ rather than KVM Can not copy/sync partially, this...

Added to https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC#PTY_Allocation Thanks for sharing Ruben

After I resize again then fixed!

# pct fsck 36165 fsck from util-linux 2.25.2 /mnt/sda1/images/36165/vm-36165-disk-1.raw: clean, 369528/6553600 files, 8523021/26214400 blocks root@ids-094110:~# pct start 36165 lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details...

root@ids-094110:~# pct fsck 36165 cannot run fsck on active container root@ids-094110:~# pveversion -v proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve) pve-manager: 4.1-1 (running version: 4.1-1/2f9650d4) pve-kernel-4.2.6-1-pve: 4.2.6-26 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 0.17.2-1...

1. CT is ON ---------------- Resizing CT from 100 GB to 200 GB, Proxmox UI failed message: Image resized. resize2fs 1.42.12 (29-Aug-2014) resize2fs: Permission denied to resize filesystem Filesystem at /dev/loop0 is mounted on /tmp; on-line resizing required old_desc_blocks = 7, new_desc_blocks...

Use the Bare-metal installation.see: https://pve.proxmox.com/wiki/Quick_installation

More details please? What is the tool to generate the certificate (unfortunately pvecm updatecerts has no option to read certain file config).

Still find how to check the method I think using existing certificate from other Server will cause security issue? Becase verify the certificate's name against host will failed?