Jump to content
XPEnology Community

haydibe

Contributor
  • Posts

    705
  • Joined

  • Last visited

  • Days Won

    35

haydibe last won the day on January 7

haydibe had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

haydibe's Achievements

Guru

Guru (6/7)

312

Reputation

  1. What is an IGD? For PCI-E passthrough, make sure to follow this guide https://pve.proxmox.com/wiki/PCI(e)_Passthrough and configure your vm to use the q35 chipset.
  2. Afaik gibt es mittlerweile die Kernel-Sourcen für DSM7. Ich würde davon ausgehen das pocopico die Kernel-Sourcen für den Build der Treiber-Module verwendet. Trotzdem bleibt das Problem das Syno's Kernel verbogen sind und damit gebaute Treiber trotzdem nicht richtig funktionieren.
  3. Pack das mal bitte in andere Worte... Vor allem auch in solche die ermöglichen zu verstehen was überhaupt Dein Problem ist. Erklär mal bitte welchen Sinn es ergibt in Befehl 4 einen DS3515xs Bootloader zu bauen, aber vorher in Befehl 1 für ein anderes Model die Seriennummer generieren zu lassen? Nicht das es eine ungültige Seriennummer die Installation verhindern würde... ich würde nur gerne das warum verstehen.
  4. Something must be off with your user_config.json. Use "jq '.' ~/user_config.json" (of course without quotes) to see wether your json document is valid. Also you might want to generaly check if the structure is still correct (lookout for missing or missplaced comma or curly bracket character(s)?) and the values look similar to those of other platfrom versions. Another option is to just attach your user_config.json to a post. Make sure to redact the sn and mac addresses. Update: I should have read the thread to the end. @pocopico the sanity check is missplaced. It needs to be either within "function selectPlatform()" or after it's called the first time. Though, since it sets a global variable, I assume it's safer to place the sanity check it in the function itself.
  5. Unfold the menu by clicking the down-arrow and select xterm.js to see the serial console.
  6. Great that you found the post, Orphée! I still find it odd that > even needs to be escapped with \\, even though it shouldn't be necessary in a json value. It should use zero offset as well, but tbh I am not sure if the offset starts at 0 or 1.
  7. Odd how a passthrough adapter does that. With a Q35 type PVE machine there are always 2 sata controllers connected, while all virtual disks will be attached to the second. I have no idea why the first even exists. You could use remap to straighten out the drive order, I remember it beeing discussed in this thread. the remap string requires escaping and can be used to straighten out the driver ordering.
  8. I started with Proxmox 7.1-0 I think and kept them updated and am now on the latest 7.1-8. I do not have a subscription for any of my 3 nodes. Two nodes use a Xeon E1275v5 and 32gb ram, the third uses a Intel i5-9500T and 32gb ram. All nodes use a Melanox 10gbps nic. I can't say that I experience any issues at all. One of the 1275v2 Nodes has my main DSM VM with a passthough LSI adapter. Before Proxmox, the nodes were operated as vSphere Cluster with a generated serial number - while this didn't bother me in the beginning it did after a while and I was looking for an open source solution. PVE uses KVM under the hood. May cloud solutions (AWS, every OpenStack Cloud) use it to provision and run their compute instances , so it can't be that bad.. can it? Thus said, what details are you exactly looking for?
  9. In addition to @jarugut's post, you might want to do into this blog post: https://gugucomputing.wordpress.com/2018/11/11/experiment-on-sata_args-in-grub-cfg/
  10. And we have the link for 3622sx as well: https://global.download.synology.com/download/ToolChain/Synology NAS GPL Source/7.0-41890/broadwellnk/linux-4.4.x.txz
  11. Es gibt etwas für 3617xs, allerdings habe ich mir das nie näher angesehen bzw. nur überflogen. Ich wüsste jetzt auch nicht auf Anhieb wo die entsprechenden Posts dazu zu finden sind, vor allem den Post zum Thema "wie baue ich mir selber eine pat-Datei für die Update Versionen". Diesem Forum fehlt leider eine Art persönliches Wiki/Blog, in dem man bspw. Tipps & Tricks und nützliche Links sammeln könnte und aktuell halten könnte. In so einem Bereich hätte ich solche Links festgehalten, da die Threads hier teilweise hunderte von Seiten haben, die keiner mehr wirklich durchblicken kann.
  12. It's possible that the virtio driver is not detected by listmods now - I am not sure, as I made my first PVE installation before listmods now was even implemented. It worked like a charm without adding any additional extension. ... and it shouldn't matter if the virtio driver is not detected, unless the maintainer of the redpill-load repo you choose in your global_config.json or custom_config.json removed the virtio extension from the bundled-exts.json file. For instance, jumkey's repos still has the virtio driver as one of the default extensions, see: https://github.com/jumkey/redpill-load/blob/develop/bundled-exts.json. Thus said, you might want to check the repo used for the specific platform and version, then check the bundled-exts.json to verify wether virtio is still included or not. Ever maintainer is free to modify the bundles-exts.json according their needs. So better doublecheck if the virtio extensions are still present and if not, just add the extension using "ext add" yourself. On PVE you don't need to add any extension, unless the redpill-load repo removed it from bundled-exts.json or you passthrough pci-e cards and require drivers for them to be added to the bootloader.
  13. Virtio, USB-Boot should work fine with when the vm is created from the cli with the commands I provide in my signature. As long as the hardware is properly detected on the hypervisor level, the pysical hardware shouldn't matter. Proxmox (and every other hypervisor) emulate the same set of virtual hardware component for vm's regardless of the physical compoentnes the Proxmox server is run on. This is with a Virtio vnic?! Are you sure you are connected to the correct bridge? Since it's working with TC, I would assume to work identicaly with DMS7. In every of my installations on three different hosts, it was always the case.
  14. Neither is the link speed shown, nor is it possible to select a mtu > 1500.
  15. The output difference is because of the `-f G` parameter. What I see on my systems: me@dsm1:~$ iperf3 -c 192.168.200.11 # DSM -> PVE Connecting to host 192.168.200.11, port 5201 [ 5] local 192.168.200.18 port 37910 connected to 192.168.200.11 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 3.96 GBytes 34.0 Gbits/sec 0 2.27 MBytes [ 5] 1.00-2.00 sec 3.93 GBytes 33.8 Gbits/sec 0 2.45 MBytes [ 5] 2.00-3.00 sec 3.91 GBytes 33.6 Gbits/sec 0 2.58 MBytes [ 5] 3.00-4.00 sec 3.70 GBytes 31.8 Gbits/sec 0 3.04 MBytes [ 5] 4.00-5.00 sec 3.66 GBytes 31.4 Gbits/sec 0 3.04 MBytes [ 5] 5.00-6.00 sec 3.90 GBytes 33.5 Gbits/sec 0 3.04 MBytes [ 5] 6.00-7.00 sec 3.90 GBytes 33.5 Gbits/sec 0 3.04 MBytes [ 5] 7.00-8.00 sec 3.49 GBytes 30.0 Gbits/sec 0 3.04 MBytes [ 5] 8.00-9.00 sec 3.66 GBytes 31.4 Gbits/sec 0 3.04 MBytes [ 5] 9.00-10.00 sec 3.76 GBytes 32.3 Gbits/sec 0 3.04 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 37.9 GBytes 32.5 Gbits/sec 0 sender [ 5] 0.00-10.04 sec 37.9 GBytes 32.4 Gbits/sec receiver iperf Done. me@dsm1:~$ iperf3 -c 192.168.200.11 -R # reverse sender/receiver role, PVE -> DSM Connecting to host 192.168.200.11, port 5201 Reverse mode, remote host 192.168.200.11 is sending [ 5] local 192.168.200.18 port 37914 connected to 192.168.200.11 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 2.33 GBytes 20.0 Gbits/sec [ 5] 1.00-2.00 sec 2.36 GBytes 20.3 Gbits/sec [ 5] 2.00-3.00 sec 2.45 GBytes 21.0 Gbits/sec [ 5] 3.00-4.00 sec 2.51 GBytes 21.6 Gbits/sec [ 5] 4.00-5.00 sec 2.35 GBytes 20.2 Gbits/sec [ 5] 5.00-6.00 sec 2.28 GBytes 19.6 Gbits/sec [ 5] 6.00-7.00 sec 2.38 GBytes 20.5 Gbits/sec [ 5] 7.00-8.00 sec 2.28 GBytes 19.6 Gbits/sec [ 5] 8.00-9.00 sec 2.43 GBytes 20.9 Gbits/sec [ 5] 9.00-10.00 sec 2.45 GBytes 21.1 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.04 sec 23.8 GBytes 20.4 Gbits/sec 698 sender [ 5] 0.00-10.00 sec 23.8 GBytes 20.5 Gbits/sec receiver iperf Done. From a 2nd PVE host transfer speeds to the dsm vm are ~ 9.3 Gbps in both directions. I am not realy sure what causes the retransmits, but it appears they are more likely to happen from pve to dsm, then from dsm to pve.
×
×
  • Create New...