Search results

That is true. Live migrations at least do not work if cpu differ. If you do migrations in that situation, use as CPU the default KVM64. Then you can migrate to nodes running different CPU:s. After migrations are finished, you can change the CPU back to host.

Use Internet search engines with: site:forum.proxmox.com why dist-upgrade You learn that doing apt upgrade may lead to The following packages have been kept back: proxmox-ve If this is not fixed with dist-upgrade or installing the missing packages, proxmox is broken because components are...

Does this server have access to the Internet? The subscription key check tries to contact Proxmox licence server.

Is pve-manager the one Find out with apt-get dist-upgrade It should show what is to be upgraded and hopefully advice on how to fix. Did the Proxmox subscription run out? Or is the /etc/pve directory missing completely? Where does the /etc/pve come from?

Nobody what? Like @sb-jw wrote in #4, what about fdisk and mount? And like @sb-jw wrote in #2, if you have 2 Terabyte disk but use only 200 G, there is unused space that can be mounted and added as storage to Promox. It's in Server | Storage | Add and choose Directory in this case.

Clonezilla. https://clonezilla.org

First thing to do is not hijack threads. https://www.urbandictionary.com/define.php?term=Thread Hijacking Mount the filesystem, then add is as storage in Proxmox. Use Internet search engines with

Does command apt dist-upgrade show upgradeable packagex?

According to PVE Admin manual 5.2 chapter 13. it is possible. I did not know this until now when I looked it up in the manual.

I rebooted Proxmox server with 12 VMs. Guests that run only name service or otherwise small hosts booted up OK, but bigger hosts with database, web server and e-mail booted up with no network settings and services down. I logged into each from console and started network with ifup, then started...

There is 15 GB used for buffers and cache. 28 GB used + 15 GB buffers/cache + 36 GB free = all memory accounted for.

If you write zeros with compression on, the actual writes to disk are drastically reduced. Have you checked whether it is the reading from /dev/urandom that is slow? It is very slow on my host. Now that you have the /root/test file, try copying it to see if the load is different when not reading...

The PVE host uses RAM also for disk cache, buffers and what the PVE itself uses. If you run ZFS it uses memory a lot. See where the memory goes, on the PVE host run command free, then examine further with top, htop etc.

The use case does not look like it would put heavy load on disk. Users are not likely to spend all their time uploading big PDF files and downloading them. So my guess is any disk system has sufficient performance. I asked similar question a while ago...

Have you tried httpS:// url?

The test is useful for me. I do not need the more complicated testing fio does. Besides, i do not understand the reams of numbers fio produces.

Thanks, that works. I created ZFS Storage and a new VM using that, and it boots and I could install Debian on it. I'll have to read more about storages now that I plan to use ZFS.

root@rautaantenni:/etc/pve/nodes/rautaantenni/qemu-server# cat 100.conf bootdisk: scsi0 cores: 1 ide2: local:iso/debian-9.4.0-amd64-netinst.iso,media=cdrom memory: 512 net0: virtio=BA:74:F3:34:08:8C,bridge=vmbr0 numa: 0 ostype: l26 scsi0: local:100/vm-100-disk-1.qcow2,size=32G scsihw...

Fresh installed Proxmox 5.2 from OVH Hosting provided image. Starting the created VM fails, VM/CT 100 Console Error: Failed to run vncproxy VM 100 - Start Error: start failed: command '/usr/bin/kvm -id 10 -name ..... I created that VM with all defaults. root@rautaantenni:~# pveversion -v...

Fresh installed Proxmox 5.2. I did not notice the GUI had button for Certificates, so followed Let's Encrypt instructions in the wiki: https://pve.proxmox.com/wiki/Certificate_Management Seems I managed to create certificate first with the staging server, and now I can not figure out how to...