Search results

Found the issue - the boot partitions, in my case sda2 and sdb2 (I have 2 drives in zfs raid1) did not have a "grub" folder, nor had the "initrd.img-5.4.106-1-pve" and "vmlinuz-5.4.106-1-pve" files. Also, for some reason they were configured for uefi, which the Gen 8 does not have: #...

Hi, I am running proxmox on a HP Microserver Gen8 since version 6.0 without a single issue, upgrades up to version 6.3 were flawless. Today I decided to upgrade to 6.4 through the "PVE pve-no-subscription repository provided by proxmox.com", as I did in the past for 6.0->6.1 and so on and ran...

BTW, I installed yesterday OpenBSD 6.4 on Proxmox 5.4, preemption_timer is set to Y, and I observe normal operation of OpenBSD. This was yesterday: # time sleep 1 0m01.01s real 0m00.00s user 0m00.00s system # date Fri Apr 12 23:23:27 EEST 2019 This is today: # time sleep 1...

Any impact performance-wise or stability-wise by doing this?

Hi, I upgraded today my HP DL360p Gen8 to the latest 4.15.18-15 kernel and the system cannot boot, it is stuck at importing the zfs pool. proxmox-ve: 5.2-2 (running kernel: 4.15.17-3-pve) pve-manager: 5.2-5 (running version: 5.2-5/eb24855a) pve-kernel-4.15: 5.2-4 pve-kernel-4.15.18-1-pve...

Try to run the backup right after a reboot of the pve host (I know this is a pain in the neck) and see if you get better backup speeds.

That would be great!

https://meltdownattack.com/ At the bottom of the page there are links to different vendors, each explaining how these exploits might be used and what the mitigations are.

I removed the 4 GB module and installed 2 x KTH-PL316E/8G. Use the manufacturer's "memory finder" to get the compatible RAM modules with your server.

The size of the disk depends on what you want to do, but if you're asking if the default Proxmox installation will fit into 180 GB drive... it will :) Make sure you buy ECC RAM for the HP Microserver (e.g. Kingston KTH-PL316E/8G)

With only 4 GB of RAM forget about ZFS! In general the steps you need to perform when you're installing from scratch are: Step 1: install proxmox on the SSD Step 2: partition the 1TB drive (GPT scheme preferably), format in ext4 and give it a mount point Step 3: add it to /etc/fstab so that it...

You need to partition and format the drive before you do something with it, just like in any OS pretty much. If you have enough RAM (e.g. 16 GB on the microserver) then use ZFS, then add the pool/dataset from Cluster -> Storage -> Add so that it is visible to the system. Everything you need is...

Do some manual tests and monitor both locations: the dump folder on the host machine and the Windows share.

The .dat file is the temporary file during backup, for instance I launched a manual backup and observed the /var/lib/vz/dump folder: drwxr-xr-x 2 root root 3 Nov 10 19:43 vzdump-qemu-103-2017_11_10-19_43_52.tmp -rw-r--r-- 1 root root 94449936 Nov 10 19:44...

Can you share how you perform the backups?

Update: same behavior with OpenBSD 6.2.

When do you expect an ISO to be available for testing?

Here is the outcome of a full day of testing: with the Xeon E3-1220L the situation is a bit better, root login takes less time than before, service restart also. Looking forward to seeing a fix in the future, no matter where it comes from, OpenBSD or KVM :) Update: after a day or less, the...

I will change the CPU of the microserver with a Xeon E3-1220L which I received today from ebay. Let's see if that will change anything as the Celeron G1610T does not have HT, VT-d, AES NI, AVX, etc. Once I do the tests, I will share the info.

Ok, good to know. I hope that in OpenBSD 6.2 this will be fixed.