Search results

On the second screenshot i see kernel 5.15. Proxmox 8 has his default kernel 6.8. So It looks like the update is not completely finished. Under the first screenshot "Advanced options ..." your are able to load an 6.8 Kernel too? What you have in your kernellist? On the third screenshot you can...

Hello @WTTG how to you installed the driver exactly and what Nvidia Card to you have. Nvidia K6000 is working very well here.

Please have a look at this thread, that should work by now. https://forum.proxmox.com/threads/certificates-acme-and-sectigo.120404/

I know this topic is from a long time ago, but was anyone been able to solve it? In my tests on Proxmox 8, Solaris is also 2/3 slower than an Ubuntu 22.04 when writing to a virtual drive, even with virtio drivers. It makes no difference whether ZFS or UFS is used. Nor does it matter which cache...

Same here tested on PVE8.x

Auch mit einer zufällig generierten MAC funktioniert es. Anscheinend muss nur eine vorhanden sein in der Config. Seltsamerweise wird (wenn man keine MAC einträgt) immer die MAC vom sekundären Interfaces verwendet. Bei allen anderen Servern ist das nicht so, da wird immer die vom primären...

@Falk R. und @cwt Danke euch beiden für eure Antworten, brachte hier leider keine Veränderung. Mir ist dann nochmal der Part in der Anleitung Proxmox Upgrade von 6 auf 7 eingefallen wo die Macadresse bei der Bridge manuell gesetzt werden konnte. Das hab ich also gemacht und die MAC des primären...

Hab ich mir auch schon gedacht. Die Ports sind für alle Server gleich konfiguriert, hatte auch schon Ports gewechselt. Sind nur VLAN's drauf konfiguriert. Ein Bond ist am Switch nicht konfiguriert, da den Bond ja das "active-backup" am Server macht.

Hallo Leute, mir ist hier bei meinem Cluster in den letzten zwei Wochen ein recht seltsames Verhalten aufgefallen. Hier mal Details zur Node die das verursacht: HP ML350G10 4x Nic Gigabit on Board (Intel X722 / 369i) 1x 10Gbit PCIe (Intel X540) pve-manager/8.2.7/3e0176e6bb2ade3b (running...

Configure a single APC UPS for Proxmox VE server https://deepdoc.at/dokuwiki/doku.php?id=virtualisierung:proxmox_kvm_und_lxc:configure_a_single_apc_ups_for_proxmox_ve_server

New englisch Tutorial: https://deepdoc.at/dokuwiki/doku.php?id=virtualisierung:proxmox_kvm_und_lxc:configure_apc_multimon_for_proxmox_ve_server

Yes i can confirm, it is working now again :)

https://bugzilla.proxmox.com/show_bug.cgi?id=5732

Hi @bbgeek17 and thanks for your answer, I've tested no multible options: TargetName=iqn.2005-10.org.freenas.ctl:target1 { node.session.auth.username = supertux1 node.session.auth.password = 123456789012 } iqn.2005-10.org.freenas.ctl:target1 { node.session.auth.username = supertux1...

I've now taken a big step forward. Basically, the targetcli on Debian 12 has a problem with Auth. Because the exact same thing works on a built TrueNAS. And this is how it looks: 2 targets set up at Truenas: iqn.2005-10.org.freenas.ctl:target1 iqn.2005-10.org.freenas.ctl:target2 + 2...

I'm on the topic too. But I just can't figure out how and where to configer it. One auth ok, but two? How was it actually solved? Do you have a working example?

If Thin provision is not activated, this is displayed as such. Right. But why it is only displayed on storage utilization and not on the Zpool, I can't tell you yet either. I have never used a Zpool without thin provision. My theory is that the VM storage is reserved dynamically. ZFS only...

unbelievable... :eek: Perfect . Please mark your thread as "solved". You can do this by editing your first post and setting the flag.

Interesting... :confused: Please post the output of the following commandos and please use the code function for a good overview, then it will be easier for us here ;) journalctl -r -p4 dmesg -l err mount lsblk -o +fstype df -h

I/O wait is sometimes a bit difficult to debug. Normally, these programs should provide clues as to the cause. Of course, there is also the journal log: man journalctl The priority switch can help you to filter events: -p, --priority= Filter output by message priorities or priority...