local-lvm strange behaviour on 6.3

[VartKat]

Let's begin by telling that I'm completly new to proxmox. I installed Proxmox 6.3 on an Intel i7 with GPU and two physical hard drives :
- 1 SSD 128Gb
- 1 HD 1Tb

The installation did partition the 128Gb in two,
- Local 28.91 GiB
- local-lvm 64.49 GiB

Datacenter's storage tell me :


So I assume I can save my VM disk images or CT on local-lvm, but when I try to create a CT or a VM the local menu only show me "local".

I'm quite sure I'm missing something, specifying content type is not enough... If so can someone point me in the right direction.

Thanks for your help
Regards
V.

 

[Dominic]

I'm quite sure I'm missing something

Actually, I don't think that you're missing something.

So I assume I can save my VM disk images or CT on local-lvm

This should be possible according to your screenshot.

Could you please execute the following command and copy&paste (using the code function of the forum, there is a button </>) the output of it?

qm create 500 --scsi0 local-lvm:5

This will create a VM with ID 500 and add a 5GB virtual disk on storage local-lvm to it. Replace 500 with any free VM ID. You can remove it afterwards using qm destroy 500.

 

[VartKat]

Actually, I don't think that you're missing something.

This should be possible according to your screenshot.

Could you please execute the following command and copy&paste (using the code function of the forum, there is a button </>) the output of it?

qm create 500 --scsi0 local-lvm:5

This will create a VM with ID 500 and add a 5GB virtual disk on storage local-lvm to it. Replace 500 with any free VM ID. You can remove it afterwards using qm destroy 500.

Here is the result :

root@pve:~# qm create 500 --scsi0 local-lvm:5
  WARNING: You have not turned on protection against thin pools running out of space.
  WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full.
  Logical volume "vm-500-disk-0" created.
  WARNING: Sum of all thin volume sizes (133.00 GiB) exceeds the size of thin pool pve/data and the size of whole volume group (<118.74 GiB).

The disk 500 is created, so no problem.

Before that I was in the process of setting up GPU passthrough to a Ubuntu 20.04 VM, I had a weird problem which was IOMMU disappearing with no clear reason :

root@pve:~# dmesg | grep -e DMAR -e IOMMU
[    0.000000] Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA
[    0.009971] ACPI: DMAR 0x000000008F412808 000094 (v01 INTEL  KBL      00000001 INTL 00000001)
[    0.047293] DMAR: IOMMU enabled
[    0.111929] DMAR: Host address width 39
[    0.111930] DMAR: DRHD base: 0x000000fed90000 flags: 0x1
[    0.111934] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap d2008c40660462 ecap f050da
[    0.111934] DMAR: RMRR base: 0x0000008ec8c000 end: 0x0000008ecabfff
[    0.111935] DMAR: ANDD device: 9 name: \_SB.PCI0.UA00
[    0.111937] DMAR-IR: IOAPIC id 2 under DRHD base  0xfed90000 IOMMU 0
[    0.111938] DMAR-IR: HPET id 0 under DRHD base 0xfed90000
[    0.111938] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[    0.113322] DMAR-IR: Enabled IRQ remapping in x2apic mode
[    0.962931] DMAR: ACPI device "device:77" under DMAR at fed90000 as 00:1e.0
[    0.962941] DMAR: No ATSR found
[    0.962979] DMAR: dmar0: Using Queued invalidation
[    0.963295] DMAR: Intel(R) Virtualization Technology for Directed I/O

was there after pve reboot, and... say 30 min after, the same command was returning nothing...

I beleive I found the problem was in grub :
it was :

GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction nofb nomodeset video=vesafb:off,efifb:off"

and I modified it to

GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction nofb nomodeset video=efifb:off"

This was generating error DMAR saying it cannot acces memory range.

I'm still not sure my modification was relevant but DMAR has no more errors and IOMMU is still there after 24 hours.
Could it be the reason I could not access the lvm-thin volume ?


By the way, a question leads to another...

1- Do I have to pay attention to these warnings :

WARNING: You have not turned on protection against thin pools running out of space.
  WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full.
  Logical volume "vm-500-disk-0" created.
  WARNING: Sum of all thin volume sizes (133.00 GiB) exceeds the size of thin pool pve/data and the size of whole volume group (<118.74 GiB).

Which I don't really get as the lvm-thin is quite empty and my 'main' zfs volume is only 23% used.

2- Now that I can access my lvm-thin volume, how can I move the vm disks I created from Main (zfs) to lvm-thin ?

Thank you very much for your help.

 

[fiona]

Hi,

Let's begin by telling that I'm completly new to proxmox. I installed Proxmox 6.3 on an Intel i7 with GPU and two physical hard drives :
- 1 SSD 128Gb
- 1 HD 1Tb

The installation did partition the 128Gb in two,
- Local 28.91 GiB
- local-lvm 64.49 GiB

Datacenter's storage tell me :
View attachment 25011

So I assume I can save my VM disk images or CT on local-lvm, but when I try to create a CT or a VM the local menu only show me "local".

I'm quite sure I'm missing something, specifying content type is not enough... If so can someone point me in the right direction.

Thanks for your help
Regards
V.

please configure the enterprise or no-subscription repository and use apt update && apt full-upgrade to update to the latest version. I highly suspect that this is a regression that has been fixed since the initial release of 6.3.