Search results

Tested it with another Debian VM, editing the conf file by hand. Switching from "scsi0" to "sata0" and vice versa doesn't harm the VM. Changing cache mode also not. Thanks a lot for all those clarifications.

Thanks a lot for this. Interresting insights. Can changes at the vdisk settings be done without any risk? And how can I tell, if the disk is qcow2 or raw? I used trimming on other VMs before, but they were freshly installed VM, not migrated VMs like this one. You may ask, why i won't make a...

The hardware tab doesn't show any type. # qm config 100 agent: 1 boot: order=sata1;ide2;net0 cores: 8 ide2: none,media=cdrom memory: 8192 meta: creation-qemu=6.2.0,ctime=1662923244 name: Debian net0: virtio=08:00:27:8a:9e:87,bridge=vmbr0,firewall=1 numa: 0 ostype: l26 sata1...

This is a fresh installation with ZFS. I have successfully migrated a 2TB VM from VirtualBox into Proxmox. Afterwards I deleted many unneeded big files within this VM. How can I tell what physical disk space this VM's disk is taking? I'm completely unsure, if the VM's trim mechanism works...

Okay, got it. The USB HDD was not mounted and what was shown was the bare directory of the root file system. Mounting the HDD shows the correct size for it. Why doesn't proxmox remount USB file systems at reboot? Does it have to be manually added in fstab? But the issue with the root disks size...

# zfs list NAME USED AVAIL REFER MOUNTPOINT rpool 5.53T 1.39T 140K /rpool rpool/ROOT 2.46T 1.39T 140K /rpool/ROOT rpool/ROOT/pve-1 2.46T 1.39T 2.46T / rpool/data 3.06T 1.39T 140K...

# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 3.6T 0 disk ├─sda1 8:1 0 1007K 0 part ├─sda2 8:2 0 512M 0 part └─sda3 8:3 0 3.6T 0 part sdb 8:16 0 3.6T 0 disk ├─sdb1 8:17 0 1007K 0 part ├─sdb2 8:18 0 512M 0 part...

sde 8:64 0 7.3T 0 disk └─sde1 8:65 0 7.3T 0 part Strangely its the same with the main volume. Its a ZRAID with 4 x 4TB HDDs. The node says under Disks/ZFS: size = 16 TB, free = 3.5 TB, allocated = 12.5 TB. But under summary: HD space 2.46 of 3.86 TB

Hi! This is something, I did not see anywhere else. I've got PVE 7.1-7 with a single node. For backup purposes an 8TB USB HDD is attached. "Disks" shows /dev/dsde and sde1 as 8 TB (it's one single EXT4 partition). When I click on that Volume (listed below the node's VMs), the summary shows 4.24...

Hi, I wanted to test the YubiKey U2F mechanism with YubiCloud. The manual only mentions that phrase, but I cannot find a clear instruction how to bind to the YubiCloud servers, only the setup for self hosted key servers. Don't know if the documents at yubico.com changed. They are not a big help...

Thanks. Suspend is set to "never".

This node is far away so I don't want to update it at the moment. pveversion -v proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve) pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e) pve-kernel-helper: 6.1-6 pve-kernel-5.3: 6.1-5 pve-kernel-5.3.18-2-pve: 5.3.18-2 ceph-fuse: 12.2.11+dfsg1-2.1+b1...

qm config 100 boot: cd bootdisk: scsi1 cores: 4 ide2: local:iso/debian-8.11.1-amd64-netinst.iso,media=cdrom memory: 8192 name: OwnCloud net0: virtio=8A:F6:4D:1D:E2:CD,bridge=vmbr0,firewall=1 numa: 0 onboot: 1 ostype: l26 scsi0: local-zfs:vm-100-disk-1,size=8G scsi1...

Hi, have a strange problem with one PVE (V. 6.1) host and its Debian 8 (old version for technical reasons) Guest. The guest crashes every now and then with no apparent reason, sometimes runs fine for weeks. The PVE logs say out_of_memory : Dec 10 18:09:39 pve kernel...

Excellent. Thanks. Missed this completely. :confused:

Well, the title says it all. Can this be done and how?

At the moment I cannot find anything on the arch linux website regarding this problem: When I create a container with Arch Linux as guest, everything works finde until I do a full system upgrade via "pacman -Syu" and reboot when done. Networking is gone then. As the given Arch Linux template is...

Edit: I had a systemd unit file with the old mount as name "/etc/systemd/system/mnt-pve-pve2\x2ddata.mount". I renamed to "/etc/systemd/system/mnt-pve-pve1\x2ddata.mount" and corrected the Where= and Description= line in it accordingly. After that I could successfully mount that and assign it in...

Okay, resolved this. There was a stale systemd mount for the old name. Edited this, so it reflects "pve1-data" and now it works. Even non-live migration. Nice!

Thanks for the details. It's a directory. Gave it a shot. But it now has a question mark on it, saying "unable to activate storage 'pve1-data' - directory is expected to be a mount point but is not mounted: '/mnt/pve/pve1-data' (500)" When I try to reformat and mount /dev/sdb1 it says "storage...