• Content Count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About positronicP

  • Rank

Recent Profile Visitors

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

  1. Are you able to login to Synology and use Quickconnect?
  2. If you can download packages you have internet. You will get a connection error if you try to login to Synology or use certain features like Quickconnect. You need to generate a working serial number to enable them.
  3. Came across this thread so I thought I’d give it whirl. Used the instructions as posted by @bmac6996 and it worked right out of the box. To clarify, and my experience Download bootloader v1.03b for DS3615xs, extract synoboot.img Add VM -> CentOS BIOS: SeaBIOS Machine: Q35 (3.1 is the latest as of this post) Primary vDisk: point to synoboot.img extracted earlier Primary vDisk Bus: USB 2nd (and additional) vDisk Location: I created a 10G vDisk, Type: qcow2. Someone earlier in the thread passed-through their disks
  4. Odd - I am experiencing the same issue. Updated from last stable 6.6 release to 6.7.1. After creating new VM's for Ubuntu and ElementaryOS, neither will output to the GPU. Both boot fine, and I can use VNC to access if VNC is the only graphics option. If I add both VNC and GPU passthrough, VNC will display 'Guest has not initialized the display (yet)'. Tried Ubuntu with both SeaBIOS and OVMF. However my macOS High Sierra and Fedora VM's created before updating still use the GPU as normal. Using an Nvidia 1050Ti without additional ROM Bios.
  5. Seems to be a number of working Mac VM's in this thread. Is everyone getting sound out of their GPU? Any specific kext requirements? I passed through a Sapphire Nitro RX580 using SpaceInvaders instructions. Everything worked EXCEPT for sound - no sound devices would show up in the VM. I did indeed passthrough both the sound and video parts of the card. Coincidentally I have the same issue with a 1050Ti in High Sierra. Everything works except for sound.
  6. I followed what @dee31797 posted - here are the itemized steps: turn on netcat-openbsd in Nerd Pack, apply, and restart computer open the virt-manager docker GUI - you'll still have the error in the Docker container, go File > Add Connection Hypervisor: QEMU Select connect to remote host over SSH Hostname: the internal network IP of your server Hit connect It will then ask you to accept certificate, then for your unRaid password. Once cleared you're in
  7. Had the same error, tried this and all is golden. Much appreciated
  8. Edit: nvm, tried my own advice and it didn't work
  9. I see delta sync is enabled by default. If I make 7 backups, then manually delete the first 6, will the 7th contain enough information to do a restore? Very happy the original script has been updated/modified to allow vdisk exclusion. Thank you!
  10. Just came to share my appreciation. Any reasons for sticking with an older product line (62.x) rather than a newer or newest (65.x) version.
  11. How should this browser be updated? It's on v61.0.1 - which if Wikipedia is to believed has reached EOL.
  12. Much appreciated - copied the backup XML to a new VM template and it worked no problem. I'll admit I was holding my breath at boot. Previously tried something similar with a Win10 VM, and encountered all sorts of issues. I did a before and after comparison on the XML and I noticed the UUID changed. Everything seemed to fall apart from there. Removing the topology is the common suggestion for allowing 'odd' core configurations in the MacOS VM threads. Is there a better way? Simply using the CPU Pinning GUI or template manager will add cores, but then the VM won't boot.
  13. In order to use 3cores for a macOS VM I removed the topology XML: <topology sockets='1' cores=... Everything ran fine. Shut it down, tried to use CPU Pinning under Settings to change cores, and received a "Missing Sockets Attribute..." error. No problem, I'll add it back to the XML. Unfortunately the VM has disappeared. Doesn't show up in VMs, doesn't show up in CPU Pinning. How do I get this VM back?
  14. This is an old question but I came across the same problem. Change network adapter type e1000-82545em instead of vmxnet3. Link to the SpaceinvaderOne video.
  15. Assuming you plan on running the VM from the same vDisk - move the disk img file and them manually assign the new location in VM Template Manager