Search results

Not sure I see the point of post as it is meaningless and contains nothing useful..... After digging around a bit more I found that the default pool ashift of 12 produces block sizes of 4k while the default block size for a ZVOL is 8k for VM disks. Basically that is doubling the amount of...

It is not possible to have two GPUs that use the same driver to have one be a pass through and the other the host main GPU.

Have you checked to see if the file exists and has the right permissions?

I have migrated a bare server over to proxmox just recently. The server is up to date running the non-production repo. The server has a HBA controller with (6) SATA3 6Gbs 4TB drives connected. A ZFS pool has been created with the (6) drives in raidz( raid5 ). In general I am seeing...

I have added a USB3 PCI card to a server, but for some reason the driver is getting assigned/loaded: 84:00.0 USB controller: ASMedia Technology Inc. ASM2142 USB 3.1 Host Controller 84:00.0 0c03: 1b21:2142 (prog-if 30 [XHCI]) Subsystem: 1b21:2142 Physical Slot: 6...

Updates today from "deb http://download.proxmox.com/debian bullseye pve-no-subscription" broke the management port. Can not ssh to it or bring up the UI from it. Using ssh it keeps failing the password. Pointing a browser to port 8006 gets connection refused. Any chance of getting a...

root@thor:/etc/pve/qemu-server# qm config 104 agent: 1,fstrim_cloned_disks=1 boot: order=ide2;scsi0 cores: 8 ide2: none,media=cdrom machine: q35 memory: 16384 name: scatha net0: virtio=3A:AF:D5:FD:1E:2B,bridge=vmbr1,firewall=1 ostype: l26 scsi0: ssd-lvm:vm-104-disk-0,size=32G scsi1...

I was kinda following the guide here since I have yet to find anything in the forum here: https://www.nocser.net/clients/index.php/knowledgebase/474/Adding-SSD-Cache-to-Existing-LVM.html

I am trying to add an SSD to a LVM VG. Here are the steps I did for it: created an new Linux LVM partition on the ssd: fdisk /dev/sdd created the physical volume on the ssd: pvcreate /dev/sdd1 extended the VG in question: vgextend vm2-lvm /dev/sdd1 created the cache lv: lvcreate -n...

I am going to try the latest driver next. Looking at the source code, it looks like it still has the same check and will continue to fill up the log with the warning messages because the card still has the McBroken firmware. I can modify the driver not to log the warning, but with each...

The problem is that I have vm-101-disk-0 on two different VGs. I have no idea how the duplicated ended up on the other VG. When I try removing the disk/lg from the VG the vm is not referring two, I get an error saying the VM the disk refers to still exists. That is why I was asking out...

I got a couple of questions in regards to LVM as I am pretty new to it. 1) I have a logic volume( aka a vm disk ) that is now long associated/attached to its vm. Can I just remove it with the 'lvremove' command? I dont see an option for removing it through the GUI. 2) I have an existing...

Thanks. I will do that as a last resort as modifying the kernel driver make things more complicated. I am really hoping to track down the latest firmware for the card.

OK, I have looked around a bit and I can not find the latest firmware for the card: intel 82599. Looking at the loaded firmware, it does look like it is an older version: root@thor:/usr/src# ethtool -i ens6f0 | grep firmware firmware-version: 0x800001a5 If I can find the firmware and tool...

The boot disk for the VM is supplied by the host. The host supplied disk contains the VM's boot/efi partition, swap partition, and / partition. The disks on the the passthrough controller contain data only. From the proxmox options/bios menu, it is seeing the bootloader for the VM and...

Changing the chipset does not help it, still goes to the EFI menu rather than booting/going to the disk. If the bootloader on the disk can not be read, how can it boot when it is selected through the efi boot menu? What a PITA all this is. Yet another reason EFI is pure evil and a...

With a 7.1 I have a 10gb NIC writing out 10,000s of these messages. Can these messages be turned off or is there something that can be done to fix what it is complaining about: Dec 12 13:48:15 thor kernel: [112353.329938] ixgbe 0000:88:00.0: Warning firmware error detected FWSM: 0x00000000...

OK, tried that same thing. The VM always goes to the BIOS menu. Selecting continue or going to the boot manager and selecting fedora boots as expected. For some reason the proxmox BIOS/UEFI is not going to the bootable disk.

There was about a total of 980ish packages updated going from the initial install of the iso to doing the dnf update. The most significant that would cause anything would be going from kernel 5.8.15-301.fc33.x86_64 to 5.14.18-100.fc33.x86_64. This would cause grub to be updated as well as...

Got the check to finally pass. Needed the machine type to be set to the q35 option. root@odin:~# cat /etc/pve/qemu-server/103.conf agent: 1 bios: ovmf boot: order=sata0;ide2;net0 cores: 4 efidisk0: datastore2s:vm-103-disk-1,efitype=4m,pre-enrolled-keys=1,size=1M hostpci0: 0000:04:00.0 ide2...