Search results

  1. I

    Nested virtualization suddenly doesnt work

    I was experiencing the same error "kvm: error: failed to set MSR 0x48b to 0x137bff00000000" with the latest 6.2 kernel and using "host" cpu. Setting the CPU to SkyLake-Server allowed me to boot the machines. After reading the thread I narrowed down the problem to flag "-pcid". I also have...
  2. I

    [SOLVED] Expanding rpool to bigger disk

    Thanks a lot that helped. I was so focused on the zfs part and expecting it to automatically expand that I didn't even consider other tools to expand the GPT table. parted /dev/nvme1n1 Number Start End Size File system Name Flags 1 17.4kB 1049kB 1031kB...
  3. I

    [SOLVED] Expanding rpool to bigger disk

    I haven't expanded the partition because I don't see the additional space anywhere. fdisk -p /dev/nvme1n1 Device Start End Sectors Size Type /dev/nvme1n1p1 34 2047 2014 1007K BIOS boot /dev/nvme1n1p2 2048 1050623 1048576 512M EFI System /dev/nvme1n1p3...
  4. I

    [SOLVED] Expanding rpool to bigger disk

    Hi, I have installed ProxMox 6.1 on mirrored pool with systemd-boot. I wanted to migrate to bigger single disk but I think I screwed up the sequence of operations. This is what I have done so far: - Initial state: - mirrored rpool 2x250GB - autoexpand=off - Executed operations: - dd...
  5. I

    /etc/pve/nodes accidentally deleted

    I just made the same f@ckup. I managed to restore the configuration by: 1. Without restarting anything copy the /var/lib/pve-cluster/config.db 2. Stop pve-cluster and corosync services 3. Restore the /var/lib/pve-clusterconfig.db 4. Restart the services Anyway backup of the configuration files...
  6. I

    ProxMox 5 -> 6 (host migration)

    This is my homelab and I will have a free weekend so ... :). Seriously though the main reasons I want to move to UEFI is - systemd-boot - really easy to manage and configure. If they used the grub for UEFI bootloader I wouldn't be so keen. I never got the hang of grub and I am scared of breaking...
  7. I

    ProxMox 5 -> 6 (host migration)

    Hi, I want to migrate my ProxMox 5 host to 6 and use UEFI boot. ASFAIK there is no direct migration path between 5 legacy boot to 6 UEFI boot. I would like to know how much of the old host I can migrate? Can i transfer the statistics as well? I assume copying the /etc/pve/* should cover the...
  8. I

    PFsense 2.4 on Proxmox 5.2/5.3

    Nothing special. Just follow the guide in the proxmox documentation and you should be OK.
  9. I

    [SOLVED] Can't get the third node pi cluster working

    Ssuming you have only two nodes and wanting to run them in cluster. Alternative to adding raspberry Pi as 3rd node is to give pne of the nodes 2 votes. In such case you can be sure that always at least one of the nodes will be able to boot and you will be able to manage the cluster...
  10. I

    PFsense 2.4 on Proxmox 5.2/5.3

    In general it is not recommended to run pfSense with virtualized NICs. I have been running pfSense since 2.2 virtualized on ProxMox with 4x 1GB NICs passed through and zero problems. These cards are cheep as chips and can save you such problems. Not exactly an answer to your problem but...
  11. I

    Cloning a VM from snapshot - not working

    Hi, I think I saw it in different thread and didn't update this one. I think the feature is not supported with ZFS storage.
  12. I

    IPMI not accessible through the ProxMox virtual switch

    There are no VLANs. Everything is on the same LAN 10.10.0.0/24. In practise the MB NIC has two IPs one of the IPMI and the other one is of the host. I guess the bridge can't see the second IP. I don't know how the MB implements the IPMI on the same NIC.
  13. I

    IPMI not accessible through the ProxMox virtual switch

    Thanks for the reply. I wanted to use this configuration in order to simplify my network settings as this is a single node home lab. As workaround I have connected the dedicate IPMI NIC to my switch and now it is accessible from the machines behind the virtual switch. I still wonder why the...
  14. I

    IPMI not accessible through the ProxMox virtual switch

    Hello, I have Supermicro MB X11SPi-TF with IPMI. The IPMI has separate port but I would like to access it over one of the MB network ports. This port is also used for entry point for the proxmox host. I am using pfSense VM with 4x 1Gb Intel nics passed to the pfSense VM. The pfSense and the NIC...
  15. I

    [SOLVED] No network on some LXC containers

    I finally resolved the issue and it was all my fault. I have commented the option "mount fstype=cgroup -> /sys/fs/cgroup/**," in the apparmor policy file lxc-default-cgns. I was trying to run NFS server within container and than gave up and obviously forgot to revert the settings. The funny...
  16. I

    qemu-2.7 iothread

    Hello, any progress on the backup support for iothread devices? The situation means that currently we have to choose between optimal performance or backups. Thanks.
  17. I

    [SOLVED] No network on some LXC containers

    Hello, at some point in ProxMox 5 development my Ubuntu LXC containers lost network. There is no network on Centos/Fedora/Ubuntu containers. Debian/Alpine/Tyrnkey-images are having connectivity. I have tried with static IPs and DHCP for the existing and new containers but the result is the...
  18. I

    Cloning a VM from snapshot - not working

    Hello, I am getting the following error "Full clone feature is not available at /usr/share/perl5/PVE/API2/Qemu.pm line 2441. (500)" when trying to clone a VM by giving different snapshot than the current as bases for the new VM. Cloning works as expected when I choose "current" as the original...
  19. I

    Proxmox 5 beta OSD trouble...

    Hi, I have my VM autostart with the following error: Mar 23 21:56:23 convergence qm[15052]: start failed: org.freedesktop.DBus.Error.InvalidArgs: CPUShares value out of range Mar 23 21:56:23 convergence qm[15049]: <root@pam> end task...
  20. I

    Proxmox VE 5.0 Beta1 Issue

    Hi, I jumped the gun and upgraded with apt-get update; apt-get dist-upgrade and also got the error: apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: corosync-pve...