Search results

  1. M

    Too slow windows startup on zfs?

    I have the same problem but I'm using a single NVME. It takes half an hour to boot a win 10 VM. a similar Win 8 VM boots alot faster... strange thing: If I'm running during the boot of the win 10 guest a "pveperf" at the host, it starts immediatly?! After deactivating qemu-agent it starts...
  2. M

    Upgrade to kernel 4.15.18-12-pve goes BOOM!

    is it safe to upgrade the new version?
  3. M

    can't upgrade zfs

    Hi, I can't upgrade zfs to 0.7.13. this is what I get: root@pve:~# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required...
  4. M

    Load average increasing

    Hi, the CPU Load average is since yesterday 5 pm increasing. Until the reboot I made 6 hours ago the load was at 280. Now it's at 36 and still increasing again. The CPU usage is normal like before (3-4 %). What is this and what can I do?
  5. M

    SPICE doesn't change resolution anymore

    Yes I did and the service is running. And as I said it works as it should right AFTER I hit the shutdown button inside the VM or in the proxmox GUI over qemu. I can see the shutdown screen in FHD until the windows closes because of the turned off VM.
  6. M

    SPICE doesn't change resolution anymore

    Hi, yes, this solved the problem. But I never had to install this before? And in the Proxmox Wiki under Linux is written "All linux distributions released after 2011 have the necessary qxl driver included as a part of the Xorg package." Now I'm facing this problem: Linux Mint works, but if I...
  7. M

    SPICE doesn't change resolution anymore

    Hi, My somewhat older Mint VM still works, but if I install a new Linux-VM and set the screen to spice, I got at least a screen but it doesn't resize the resolution anymore if I set the virt-viewer to fullscreen. As I said my old Mint VM works with fullscreen but other guests not anymore...
  8. M

    Can't shutdown / VM Locking problem

    Hi, My Proxmox-Server won't shutdown out of the sudden, because either some ct or vm won't shutdown. When I delete the files within /var/lock/qemu-server or restart the qemu-server, then I can shutdown. But after a new boot I have the same problem. What can I do? The only thing changed was the...
  9. M

    Proxmox Cluster shutdown

    Hi, I would like to use a Proxmox 2-Node Cluster but only for testing. I would like to test stuff on the second node, and after setting up everything in the LXC, I would like to move it to the first node. In addition, the second node should be used for backup for maintenance on the first node...
  10. M

    add local storage to Proxmox node

    I had to delete the Cluster, because my first node did not shutdown anymore. My intention was to have one "testing" node and one productivity node, plus the testing node should be useable as a "Backup-Node", when the first node is offline due to maintenance or failure.
  11. M

    Deinstalled Cluster, now no WebGUI

    Hi, I deinstalled the Cluster I made on my Proxmox 5.1 with first removing Node2 and than doing: stop pve-cluster.service and corosync.service then destroy /etc/corosync/* and /var/lib/pve-cluster written here: https://forum.proxmox.com/threads/destroy-cluster-configuration.29092/ Now I can...
  12. M

    add local storage to Proxmox node

    Hi, I set up a 2-node Cluster and I would like to move VMs/CTs between both nodes, but on each own harddrive in each node. I would like to move/copy them in the case, if the mainnode with the ZFS-Storage goes offline. This is a home environment, though HA is not necessary.
  13. M

    Can't access WebGUIs from LXC and VM

    Hi, After I upgraded to 5.1 I cannot access the Webgui from my Wordpress-Website (Turnkey-Linux) and not from my pihole-VM (Ubuntu 16.04). But I cann access the Webgui of my Nextcloud-CT and my Observium-Turnkey. What's wrong?? It worked before I upgraded to 5.1.
  14. M

    KVM does not boot after Kernelupdate 4.13.4.1

    This I'll get when I create a new VM: kvm: -drive file=/tank/Backup/images/100/vm-100-disk-1.qcow2,if=none,id=drive-scsi0,discard=on,format=qcow2,cache=none,aio=native,detect-zeroes=unmap: file system may not support O_DIRECT kvm: -drive...
  15. M

    Proxmox VE 5.1 released!

    the test kernel doesn't work with ZFS (0.6.5) for me.
  16. M

    KVM does not boot after Kernelupdate 4.13.4.1

    Another reboot didn't help. And it takes now some time to boot up... Edit: Swap is missing as well....
  17. M

    KVM does not boot after Kernelupdate 4.13.4.1

    where can I find the full journal of the boot? both of the mentioned files exists. edit: Here is everything from boot in the syslog: https://pastebin.com/AH0BSEnR
  18. M

    Cannot access disk on zfs

    I got the same problem. /dev/zvol is missing.
  19. M

    KVM does not boot after Kernelupdate 4.13.4.1

    Update: I rebooted and my KVM can't boot anymore: kvm: -drive file=/dev/zvol/rpool/data/vm-250-disk-1,if=none,id=drive-scsi0,discard=on,format=raw,cache=none,aio=native,detect-zeroes=unmap: Could not open '/dev/zvol/rpool/data/vm-250-disk-1': No such file or directory sudo zpool list NAME...