Search results

Let me just say that this idea is awesome. I have been doing the cumulative CPU usage and vms running using a script which logs into each machine and harvests information; cpu, disk, memory, etc. A dashboard is most welcome. I have been AFK for few weeks, so won't be able to suggest/recommend...

I would recommend using xfs only if you can guarantee that there would no abrupt reboots of your PVE host. Otherwise go with ext4. Regards, Shantanu Gadgil

That would be interesting to see indeed!

I agree, I too didn't think the vertical menus was such a "hot" idea, but I'm OK with it. Only so many options can fit in a horizontal menu. @ScOut3R I think they must have done this as they expect more options/settings coming up. Cheers and Regards, Shantanu

Awesome work guys! Love the update. Also the minor things like the BIOS display image. Keep up the awesome work! Regards, Shantanu Gadgil

Can you post screenshot of what setting you use when you do a backup? And also a screeenshot of : Datacenter > Storage Also output of "pveversion -v" would be good for folks to help! :):)

Try installing 'ncdu' on your host machine and check where (which directory/subdirectory) is the culprit.

Looks like you have created a Linked Clone. I don't think you would be able to delete the template till the linked clone exists. Regards, Shantanu

Before deleting the SWAP you could have done the following: * move the END of the EXTENDED partition to the end-of-disk (right) * move the SWAP partition to the right. * move the BEGINNING of the EXTENDED partition to the right. * increase the size of the first partition. Assuming you have...

As long as all features from LXD will be present and usable in "Proxmox + LXC", I wouldn't complain too much. Though I doubt the REST API etc. will be happening for LXC. I am extremely happy with how easy it is to manage LXDs rather than Docker. Being more like a machine makes it waaaay easier...

Errr... yes and no ... but mostly no! https://linuxcontainers.org/lxc/introduction/ https://linuxcontainers.org/lxd/introduction/#relationship-with-lxc The only reason for bringing up the topic of LXD was its much simpler usage model than having to remember lxc-ls, lxc-attach, etc. etc. Also...

Hi, I have faced similar issues, but after a backup and restore of LXC. It had to do with the "/var/run", etc. directory missing or having the wrong ownership. HTH, Shantanu

@KillianS , I think @tom means you will need to "upgrade" your packages. @tom , besides editing the config file directly, is there a command-line method to edit the config file? (Something like the "qm set" equivalent). Thanks and Regards, Shantanu

Hi, In continuation with this, any plans to get LXD support for Proxmox ? I am using LXD (LXC 2.0) quite actively on other Ubuntu 16.04 machines and am very happy with it. For my work, I create Ubuntu 16.04 VMs on Proxmox and run LXD based workloads within the VM. It would be awesome if...

@raidelriveran Do you want to add new network device to your VM ? Regards, Shantanu

This is not recommended, do it at your own risk. Disabling barriers it not a good idea. File: /etc/fstab Before: /dev/pve/root / ext3 errors=remount-ro 0 1 After: /dev/pve/root / ext3 nobarrier,errors=remount-ro 0 1

+1 I second this. I too feel that the vm/container and host controls are too close to each other. regards, Shantanu

Very odd, nothing like that for me on many servers of mine. Maybe if you can safely stop your VMs, force reboot the machine and try again ?

<bump>

Hi, I know this is an old topic, but recently I too faced a similar problem on some of my older version 3.4 servers. The "new" arping conflicts with the the older "iputils-arping" and in turn wants to remove the "pve-manager". *** As expected, if I accept this, the WebGUI and PVE in general...