Search results

Thanks you very much!

Well review the UEFI docs (https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_virtual_machines_settings) Sec. 10.2.10, I found something interesting. I did that and start the VM and that make it work. After that I change it back to default and the VM continue to reboot properly. Therefore...

I'm confronting similar issue. I was able to identify that if I remove the EFI Disk the boot process continue. If I add it again (to confirm relation) the issue came back. Header Proxmox Virtual Environment 7.1-8 Search Node 'GUYNPR1-PVE-NAF1' Hour (average) CPU usage 5.05% of 32 CPU(s) IO...

After upgrading to version 19.5.12 of the NIC firmware from version 19.0.12 no LACP bond interface will come active. This is just a reference for those that face similar issue. I rollback to the previous version on the Dell Servers and everything came back to normal. Proxmox Software...

This work for me too! A GUI for acknowledge would be too much to ask? ;) Thanks Proxmox Team for great Product!

Is very difficult to assist, if no details... A beginning point could be to provide the Proxmox version on all the nodes is deployed, that is under summary "Package Versions". Regards,

https://forum.proxmox.com/threads/proxmox-bridge-mtu-issue.51148/#post-293884 On that threat you will find my post and configs, there you will notice that I'm using QinQ. My topology there is like: vFirewall (OpnSense) <> vmbrXX <> vmbrY <> CiscoNexus 3548X <> Juniper MX...

Perfect. Thanks for your recommendation @tom I upgrade to version pve-kernel-5.4.24-1-pve and the device boot properly. By the way that device is a toy environment that runs on a Udoo x86. Of-course I try to run everything on LXC because the limited memory resource, but for validation and for...

Thanks for answer Tom. understood. Anyway the wifi interface is useful as Out-Of-Band access. In my case I attach to a vrf to not conflict with the main routing where I run the VMs/LXCs. I would let you know the results of the upgrade to kernel 5.4.

@spirit @dietmar Can you take a look at this? May be I can provide more information if need to fix the problem issue or is fix in newer kernel. Regards

I'm facing an issue with the wifi, while boot on the kernel pve-kernel-5.3.18-3-pve. If I rollback to the previous kernel (pve-kernel-5.3.18-2-pve) wifi work fine again. Attach are the to boot files that I was able to retrieve. Thanks for the assist.

I think the proposed solution will not work on a cluster environment, at least will not be efficient modify the file on all the PVEs... Is there other alternative? May be something on the pmxcfs?

You got a fix! That work like a charm. Is too much to ask, what are the changes? What is the commit on the git, so I can learn how to work on the git files and if possible directly contribute by summit git push request?

I'm downloading to validate. Let you know. Thanks!!!

I agree with you, even so, on the presented scenario the disk are SSD, and the rpool should just be use for running the OS, not VMs/LXC. I forget to mention that I deactivate everything from rpool disk from the Datacenter Storage section. Therefore the load of the SSD disk will be OS...

Sorry for the delay.... Here is the requested file: root@GUYNPR1-PVE-NAF1:~# more /etc/network/interfaces # network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the network configuration...

I used to have similar setup: 1. If I want just for second pool should I write name of second pool instead "rpool" (zpool add secondpoolname cache....)? You could install Proxmox on a small partition 16GB (ZFS Mirror), use a second partition for RAIDz2 with L2ARC cache (I named: Storage_zPool)...

I'm confronting similar message: The configuration and implementation had no issues, everything is working if configure on shell, even can applying using the new Apply Configuration button. The issue probably is a configuration check just for the GUI. what is strange is that complains about an...

I know is an old treat, but no one report if is fix or not. Therefore, I suggest to check the mtu between nodes. I face that kind of problem .

Understood:). I will wait until the repos are updated;). Thanks for your Guidance!