Search results

Hi @t.lamprecht I'm at the latest version as follows so assume there's maybe another issue here that wasn't fixed by the previous fix? root@pve-host1:~# pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.41-1-pve) pve-manager: 6.2-6 (running version: 6.2-6/ee1d7754) pve-kernel-5.4: 6.2-2...

Hi There, When I try to clone an existing VM from the (not-current/not-latest) snapshot, I get the following error (with the error seemingly randomly either related to scsi0 or efidisk0)? Is this expected or a bug? The configuration of the source VM being cloned is as follows...

I'm also seeing this in my syslog every 10mins as follows... Jun 17 09:15:19 pve-host1 pvestatd[2377]: qemu status update error: metrics send error 'influxdb': failed to send metrics: Message too long I couldn't find any bug raised about this as suggested above so have raised the followng bug...

Thanks for this. Is there a guide somewhere on the definition of and differences between UPT and legacy Passthrough and, importantly, how to configure each approach? thanks!

@Ekinox - As mentioned above, my VM (and the physical PVE host) is headless - I do not use the HDMI for the VM. I only passthrough the IGP to use the Intel QuickSync features of the CPU/IGP inside the VM and connect to the VM using console/SSH when I need to...

Have you tried passing the card through as a mediated device (GVT_g)? That’s how I’m currently passing my IGD through on Ubuntu 18.04 for headless Intel QuickSync.

I can’t recall whether I changed anything with the cstate in the BIOS - I know I looked into it at the time but I don’t recall amending anything in the BIOS specifically for this. If you can point me to the cstate settings in the BIOS, I can tell you what mine are set to...

It would be good to understand exactly what was backed up (full list of folders/files), and the procedure used to backup and then restore the node. Thanks!

Hi! You could run a VM on the windows machine using VirtualBox and use that VM as the netconsole target but obviously the VM needs to be running and awaiting a kernel panic on the Proxmox node. In terms of differences between Proxmox and kernel updates , the kernel updates are just a subset of...

some questions / pointers below. (1) Was this a one-off or happening multiple times? (2) Anything relevant in the Syslog before the freeze? (3) What was on the screen when the NUC froze? Did you manage to capture a screenshot/photo? (4) Have you tested the RAM in the NUC using memtest? (5) I’d...

I notice you're using the q35 machine type for the above VMs... I've only ever been able to passthrough my Coffee Lake IGD to a headless ubuntu (for Intel QuickSync purposes) using the i440fx machine type. If I use i440fx machine type, I can use the VM headless and it sees the IGD / QuickSync...

With headless Intel NUCs (for Intel QuickSync purposes), I've only ever been able to get the Coffee Lake IGD passed through using i440fx - If I try q35, the Ubuntu VM always hangs during boot... I wonder if the above could explain that behaviour also? Even so, if it's a bug, I think it would...

@onepamopa also seeing this same issue at the following post: https://forum.proxmox.com/threads/problem-with-vm-garbled-novnc.68035/#post-305160

Hi. I’m seeing the exact same issue and raised this yesterday (without a response as yet)... In my case changing the VM graphics adapter to SPICE works but I’d like to understand why the problem has started recently with the Default VGA adapter ...

Just to report back here... Since adding the "ethtool -K eno1 tso off gso off" to postup (about a week ago), I haven't had any further occurrences of the "Detected Hardware Unit Hang" issue... So it looks like only "tso off gso off" are required and not all the other parameters

I'm running a couple of Ubuntu 18.04.4 server VMs. The VMs run fine but when I try to view the VM using the "NoVNC console", I get the attached screen corruption? When starting the VM, the "Proxmox" splashscreen is shown fine in the console, but as soon as the VM commences boot, the display is...

I’ve got 5.4 running on one NUC8i5BEH and 5.3 on another and haven’t noticed any such issue with 5.4. But perhaps I’m not looking in the right place... Is there a command you run to identify the issue and perhaps I can run that here also?

I have the same NUC model and have no issues other than the well-documented regular integrated e1000e NIC “Detected Hardware Unit Hang” issues. Perhaps check syslog for any occurrences of the “Detected Hardware Unit Hang” issue where the network loses connectivity briefly before returning ... I...

After installing ethtool on the node ... apt install ethtool ... I tried this way first (putting the post-up under eno1) and rebooted. Checked whether the post-up had worked with "ethtool -k eno1 | grep offload" and I could see that it had not worked (tso was still enabled)... By placing the...

Thanks @Stoiko Ivanov - Could you let me know how and where I make this "post-up line"?