Search results

Yes, but especially for LLM with large models that not fit into the GPU RAM a LXC with big EPYC 512 Core platform would be a very efficient way to use this as a side application instead of bind this resources by a VM which can't be used for other LXC/VM. LXC are really nice for over provisioning.

Top shows the same problem. If I adapt 8 cores it shows all cores of the two socket CPU's in the docker container but not in the LXC it self.

Is there any way to fix cores of one socket from dual socket system to a LXC? If have this problem with Ollama https://github.com/ollama/ollama/issues/5554 Thank you to all supporters.

Dear @unholyhumorousunratedoat thank you. I extend it for a better understanding. proxmox-backup-client list --repository pbsIP-pbsdatastore export PBS_REPOSITORY='pbsIP-pbsdatastore' proxmox-backup-client list Then proxmox-file-restore list vm/142/2024-10-03T01:23:15Z / is working.

Dear @Chris, I have the problem when I use proxmox-backup-client list or proxmox-file-restore list vm/142/2024-10-03T01:23:15Z / I get always the error massage: Error: unable to get (default) repository What is wrong? Best Tim

Dear George, yes I try it also on the newest Kernel and QEMU Version. There is on interesting thing by the ACPI PCI path between Windows an Other OS Config. If change the OSTyp. VM OSType Other: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SE0@1C/IOPP/GFX0@0...

Thank you, very interesting, that PCI Path is changing PciRoot a little bit if change the OSTyp. VM OSType Other: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SE0@1C/IOPP/GFX0@0 PciRoot(0x1)/Pci(0x1C,0x0)/Pci(0x0,0x0) VM OSType: Win10...

Hi Dmitry, If you need this for MacOS, this won't work. You can read this post and that could be work for you. https://forum.proxmox.com/threads/amd-radeon-rx6950xt-spoofing-for-macos-vm.125901/

I take out "agdpmod=pikera" from the boot arguments. No effect. The kexts will be loaded but something is missing.

I take out "agdpmod=pikera" from the boot arguments. No effect. The kexts will be loaded but something is missing.

Hi George, bare metal is no option because it is a rack server system as hypervisor. We need for more than one MacOS Instance. It tried to pass it as (0x6939) Tonga PRO [Radeon R9 285/380]. I used several methods Proxmox ID Spoof, SSDT, OpenCore config.plist at <DeviceProperties>. The Device ID...

Dear George, this is an important issue also for me. I'm working for a long time to get a S7150 (Tonga XT GL Device ID 0x6929) Card working in MacOS inside Server System with Proxmox as Hypervisor. Until now without success. I was where confused that the spoofing just by Proxmox was working...

Liebe Kollegen, also so wie ich das sehe ist doch nun das eingetretenen was ich mir immer gewünscht hatte. LXC auf ZFS Dataset mit overlay2 Dateisystem Docker Instanz. Ich habe es auch schon soweit getestet und es funktioniert bisher sehr uneingeschränkt mit allen Applikationen.

Maybe but please test it. My experience with this "Round up" order was good until now. service pve-cluster restart && service pvedaemon restart && service pvestatd restart && service pveproxy restart vs. service pvedaemon restart && service pveproxy restart

Save Solution >>> Login per SSH in every Node and run: service pve-cluster restart && service pvedaemon restart && service pvestatd restart && service pveproxy restart

Ja, aber eigentlich kann z.B. ein normales Intel Xeon Mainboard nur 10 S-ATA Geräte native anschließen. Mehr Ports bedeutet das da ein anderer Controller noch vorhanden ist, der dann eine Fehlerquelle für ZFS sein kann. Bei AMD EPIC, mit seiner anderen Board Architektur, fehlt uns noch die...

Hallo dieser Fehler kommt mir bekannt vor. Wir hatten ein ähnliches Problem bei einer Kombination aus HGST SAS 12 TB HDD's mit LSI-3008 Controllern als Kombi, wo nur ein Firmware Update der HDD's das Problem hätte lösen können, was aber Western nicht bereit gestellt hatte. Ursache: Der SAS...

mount bind with LXC is very simple if you use host adapted storage (ZFS, NFS; SMB) mounts.

Yes VM for Docker is the save and boring way, but the future belongs not to the VM. >> The Future could be LXC with ZFS with Pods and Kubernetes using docker hub images.