Search results

  1. T

    Freeing Up Unused Space In A Linux VM That Doesn't Support TRIM

    Thank you very much for your reply :-). Interesting. So the reclaiming of disk space is a function solely within LVM and not PVE (beyond passing the TRIM requests through to LVM). For some reason I got it into my head that PVE was passing explicit `return this block to the free pool' requests to...
  2. T

    Freeing Up Unused Space In A Linux VM That Doesn't Support TRIM

    I simply want to shrink the disk down to free up unused space, returning it to the LVM thin pool. The VM itself runs fine, but at the moment the only way to reclaim the space would be to either do a native back up of the disk, recreate the disk and restore from backup. Or mount the disk in...
  3. T

    Freeing Up Unused Space In A Linux VM That Doesn't Support TRIM

    Hi all, I'm usng LVM-Thin storage for my VMs, one of which is a very old legacy Linux VM. So old that the kernel doesn't support TRIM. The file system is EXT2. Is it possible to somehow run fstrim from the PVE host on the lvm-thin volume and have the space reclaimed in the lvm-thin pool? The VM...
  4. T

    blank/black/empty console issue since update

    It seems that just creating the getty.target.wants directory is enough.
  5. T

    [SOLVED] LVM `issue_discards` is disabled after upgrade from 7 to 8.

    <snip> Thank you so much Fabian for that brilliant explanation. I tried googling around for an answer for ages but apart from the not needed on lv-thin LVs comments scattered about the place I got no further.
  6. T

    [SOLVED] LVM `issue_discards` is disabled after upgrade from 7 to 8.

    Just curious... Why isn't it necessary to set issue_discards=1 when used with PVE and lvm thin provisioning? Surely this is still needed when a thin volume is deleted (as there's always stuff left lying around in the volume etc)?
  7. T

    blank/black/empty console issue since update

    I had a very similar issue when upgrading from 6.4 through to 8.1. All of my containers didn't display anything on the console but booted up and I could ssh in. The above fix to switch the console mode to /dev/console worked as stated above (and many thanks for the posted solution :)). However I...
  8. T

    Networking not working on nested VM

    Sorry I took a very long time to reply, been moving house, selling the old family home and re-setting up my home lab etc... Anyway I tried the exact same experiment on PVE version 8.1 and had the exact same issue. However this also occurred on a plain KVM/QEMU install on regular Ubuntu and so...
  9. T

    Networking not working on nested VM

    Update: I have tested this on a `bare' KVM/QEMU setup, no proxmox software involved, and it suffers from exactly the same issue. I shall raise this with the kvm/qemu team. Many thanks for you help and sorry to take up your time. If I/someone else gets to the bottom of this I'll of course post...
  10. T

    Networking not working on nested VM

    Yup no firewalls in the way. It's weird. Basically when VM running on the same L0 PVE server tries to connect in you can see it sending the initial SYN packet, 2 TCP retransmits and then the originating VM trying to find the mac address for the L2 VM with a couple of ARP requests (which makes...
  11. T

    Networking not working on nested VM

    Hello again, I have an apology to make, I didn't mention what type the L1 hypervisors were :-(. I tried the tcpdump command but it didn't show anything odd as ping worked, I just couldn't ssh into it unless it was from another real machine. Likewise ip route and ip neighbor showed nothing...
  12. T

    Networking not working on nested VM

    Firstly sorry about the late reply. Life took over! :-(. BTW many thanks for the tip about L0-2, much simpler! Anyway I have done some further investigating... In fact I can successfully ping the L2 VM from any of my networks but, for example, sshing in from a PVE L1 VM doesn't work, nor does...
  13. T

    Duplicating A Node Through Backup And Restore

    Ok just to give some feedback in case someone else wants to do this... It actually works surprisingly well but the system only had one node and wasn't a part of a cluster. However use these instructions at your own risk... You've been warned! So I actually backed up the system, minus the VM...
  14. T

    Networking not working on nested VM

    Hia all, I have a VM with the host CPU setting enabled and inside that VM I'm running VirtualBox and VMwarePlayer with VMs that use bridged networking. This is for testing Ansible configurations under different virtualisation environments. Both the guest OS and the guest-guest OS (if you get my...
  15. T

    Duplicating A Node Through Backup And Restore

    Ok thanks once again :) MUCH appreciated...
  16. T

    Duplicating A Node Through Backup And Restore

    Hi Fabian, many thanks for the info. I take it the config SQL database will simply update itself on finding deleted config files...
  17. T

    Duplicating A Node Through Backup And Restore

    Hello all, I wish to duplicate a working PVE node onto another machine but without copying the VMs across. Some points: VM storage is done using lvmthin. PCE version 6.3-3. Quite some tweaking and work has gone on on the node to meet my requirements, nothing outlandish but not a case of simply...
  18. T

    How to shutdown Proxmox 6 from CLI?

    From doing systemd-analyse and systemctl list-unit-files I came up with the following script for disabling and and enabling Proxmox services and related daemons. In order to start stuff up again you need to reboot, to make sure you get a clean boot in the right order. Your mileage may vary but I...
  19. T

    Intermittent Network Dropouts

    On my proxmox single server setup I have the following network setup: vmbr0: Bridge onto the main network. This as a video renderer VM (media) and a desktop VM (pluto) connected to it. vmbr1: NAT, using the PVE host to do the DNS/DHCP by using dnsmasq and NATting via IPTables and forwarding...
  20. T

    Problem for user permission to only start, restart, shutdown one node

    Try also granting the sys.audit permission. They'll seemingly get access to all the settings but will get permission denied when they try to change them. However they will be able to reboot and shutdown a node.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!