Jump to content

SuperW2

Members
  • Posts

    407
  • Joined

  • Last visited

Posts posted by SuperW2

  1. Have been running ZFS on my UNRaid now for most of this year with no issues.  Completed update to 6.11.5 (had previously been applying all point releases fairly quickly after release)... After the last update I'm getting a PANIC at boot directly after "Starting Samba: on 4th line "/usr/sbin/winbindd -D". 

     

    Quote

    VERIFY3(size <= rt->rt_space) failed (281442933186560 <= 1071386624)
    PANIC at range_tree.c:436:range_tree_remove_impl()

     

    If I start Unraid in safe mode it boots just fine... I renamed the unRAID6-ZFS .PLG file and it boots normally as expected...  Has anyone else run into any issues with the ZFS plugin and newer 6.11 versions of UnRaid?  Any ideas?  I completely removed the ZFS plugin and reinstalled and get the error messages in the live SysLog...

     

    I've imported my pool into a TRUENAS boot that I've used to add vdevs and it appears healthy and no issues that I can identity.   Scrub completed normally.  I also downgraded to previous 6.11 versions (I was running 6.11.4 before with no issue) and no change, same PANIC error.

     

    Any Ideas or anyone else with similar issues?

     

    SW2

  2. 2 hours ago, Hoopster said:

    You can manually downgrade by downloading the 6.11.3 (6.11.4 is not available) release from the download page, extracting the zip file and copying all the bz* files to the root of your unRAID flash drive.

    Thanks...didn't help...now get the PANIC with either 6.11.3 or 6.11.5.  I CAN boot into Safe Mode in both so maybe I had some type of hardware failure that just happened at the same time... unfortunantly almost zero info anywhere with the error i'm seeing.

  3. Attempted upgrade from 6.11.4 to 6.11.5 and getting a PANIC and hang... no other changes to hardware or any recent hardware issues that I know about and have been upgrading at every point release... Guess I can try to downrev my USB Boot stick but not sure how to proceed and or troubleshoot since it never finishes a boot.

     

    This is occurring directly after "Starting Samba: on 4th line "/usr/sbin/winbindd -D"

    VERIFY3(size <= rt-›rt_space) failed (281442933186560 <=

    PANIC at range_tree.c:436 :range_tree_remove _impiO)

     

  4. I see that PIA is "unsupported" and not recommended, but seems to be several folks that had previously made the converted PIA files via scripts from various GitHub projects... I've tried a couple of those converted CONF files with the new RC5 options without any luck.  If anyone finds a way to make those work with the "VPN tunneled access for docker" option in RC5, I'd be all ears to hear how (even if not fully supported).  I don't really want to switch to a new provider at the moment.

  5. 54 minutes ago, nathan47 said:
    root@TaylorPlex:~# zpool list -v
    NAME                                       SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
    boot-pool                                  936G  2.61G   933G        -         -     0%     0%  1.00x    ONLINE  -
      mirror-0                                 936G  2.61G   933G        -         -     0%  0.27%      -    ONLINE
        sdk3                                      -      -      -        -         -      -      -      -    ONLINE
        sdl3                                      -      -      -        -         -      -      -      -    ONLINE
    mainpool                                   674T   358T   316T        -       48G     1%    53%  1.00x    ONLINE  -
      raidz3-0                                 187T   173T  13.9T        -       16G     0%  92.5%      -    ONLINE
        95135db1-c66b-4dc1-af86-9294e996cfd0      -      -      -        -         -      -      -      -    ONLINE
        035d8726-5610-4b32-a260-b391e0aeb809      -      -      -        -         -      -      -      -    ONLINE
        d3a94833-9293-495a-b905-24d285d722ab      -      -      -        -         -      -      -      -    ONLINE
        672d7b6f-965c-415a-95a0-ad5cd974fe7d      -      -      -        -         -      -      -      -    ONLINE
        127da1c4-b2aa-4942-baba-bfae490d66fa      -      -      -        -         -      -      -      -    ONLINE
        150feebe-72b9-4ce5-8039-64018c024f27      -      -      -        -         -      -      -      -    ONLINE
        d3a32ea7-c354-40fe-9ced-828d1d56f4b8      -      -      -        -         -      -      -      -    ONLINE
        23086c7a-8632-4fae-8894-8d53df099b13      -      -      -        -         -      -      -      -    ONLINE
        b7fa0359-1c83-4c3e-a11d-7bf0c5c45c76      -      -      -        -         -      -      -      -    ONLINE
        778df321-8c7e-44dd-a9dd-fe7dbb512822      -      -      -        -         -      -      -      -    ONLINE
        520c23be-cea1-4438-a720-a39a6b516f18      -      -      -        -         -      -      -      -    ONLINE
        1a0f9a46-9c42-400a-8cb6-f394ed7a6ec1      -      -      -        -         -      -      -      -    ONLINE
        4224fdfb-8d0a-46bb-bf3a-516cac17f430      -      -      -        -         -      -      -      -    ONLINE
        a9a2e832-f13f-4f19-acd8-b37f0262a09e      -      -      -        -         -      -      -      -    ONLINE
        896bdbbb-7dc1-476f-bc77-8626de2aec66      -      -      -        -         -      -      -      -    ONLINE
      raidz3-1                                 136T   135T  1.36T        -       16G     5%  99.0%      -    ONLINE
        9afc98cc-e84b-451e-bdb1-f6759f62635e      -      -      -        -         -      -      -      -    ONLINE
        b2953602-932f-4900-a25d-278298762b7f      -      -      -        -         -      -      -      -    ONLINE
        ad53b00b-9d7b-4135-8b92-b1c1a99d6854      -      -      -        -         -      -      -      -    ONLINE
        c234663c-12b6-45dc-bb7b-42135ed53cb9      -      -      -        -         -      -      -      -    ONLINE
        39bd5a10-8e37-4bb1-ad79-dae4692143ba      -      -      -        -         -      -      -      -    ONLINE
        8ee21b30-63f9-4026-8d66-1e69b0ff4972      -      -      -        -         -      -      -      -    ONLINE
        a86e5df2-3a00-4e4c-aec4-cb23627d6215      -      -      -        -         -      -      -      -    ONLINE
        78f631c6-4bee-45fb-8578-36396683c759      -      -      -        -         -      -      -      -    ONLINE
        6def9ab5-9b7c-430a-86f2-ae03ed090493      -      -      -        -         -      -      -      -    ONLINE
        ebb7fbd2-6f7c-400e-ab75-8d664fb15762      -      -      -        -         -      -      -      -    ONLINE
        d83df2df-a0fe-4f0a-895e-c8a02ab44781      -      -      -        -         -      -      -      -    ONLINE
        82c424e4-6d1c-43a7-9ef1-bd9f4b7fe1d5      -      -      -        -         -      -      -      -    ONLINE
        0c988f98-8ae4-40d5-9a9e-a0ced36d5391      -      -      -        -         -      -      -      -    ONLINE
        bab6441a-9605-4683-9599-64efcdec8477      -      -      -        -         -      -      -      -    ONLINE
        827b4605-209e-43d0-bbb2-e44d2f2414d0      -      -      -        -         -      -      -      -    ONLINE
      raidz3-2                                 187T  49.7T   137T        -       16G     0%  26.6%      -    ONLINE
        28b0bf94-4328-4d4c-a3ae-46e010e21f66      -      -      -        -         -      -      -      -    ONLINE
        30a46b87-2ac4-4c40-bf53-e84cf222f5c3      -      -      -        -         -      -      -      -    ONLINE
        e89b48ad-4d6e-4cae-9932-7fda1220d491      -      -      -        -         -      -      -      -    ONLINE
        a16701ab-a151-4b1b-9afc-ca5303d1b53a      -      -      -        -         -      -      -      -    ONLINE
        1a6ee52c-94a8-463a-9edb-b3db277863f0      -      -      -        -         -      -      -      -    ONLINE
        826de601-2706-491b-af3e-e2916fe223c2      -      -      -        -         -      -      -      -    ONLINE
        84571fba-f1ba-4af0-9dd0-1ed54e8ffd1e      -      -      -        -         -      -      -      -    ONLINE
        534c0af8-304d-4296-9133-921bd90a4dee      -      -      -        -         -      -      -      -    ONLINE
        4486918f-d8b1-4479-9439-259b06b3d3c6      -      -      -        -         -      -      -      -    ONLINE
        0435633d-612a-471b-aa56-345caac43ba7      -      -      -        -         -      -      -      -    ONLINE
        6eecb4ff-c9e9-423a-810a-0b65a6a1dccd      -      -      -        -         -      -      -      -    ONLINE
        1b488a53-247d-4786-ba8f-40c29c6ea5e3      -      -      -        -         -      -      -      -    ONLINE
        6f901e50-0b53-4ea8-b83b-712766853919      -      -      -        -         -      -      -      -    ONLINE
        c6d66210-4621-4d59-a751-a5dc9a327d84      -      -      -        -         -      -      -      -    ONLINE
        777da20a-67e6-4452-b892-7a5d548e41cd      -      -      -        -         -      -      -      -    ONLINE
      raidz3-3                                 164T   186G   164T        -         -     0%  0.11%      -    ONLINE
        8056a492-c16a-4bdc-93c1-bb13dfb88af5      -      -      -        -         -      -      -      -    ONLINE
        2ba06a18-4c8b-44d5-b858-f77e03581051      -      -      -        -         -      -      -      -    ONLINE
        f882076c-76af-4bc7-b531-30a9369a73fc      -      -      -        -         -      -      -      -    ONLINE
        47a89ace-81b4-4d71-9851-d4e7bdd0bd88      -      -      -        -         -      -      -      -    ONLINE
        8d9e4c4f-c7a2-4bee-b1ff-4e412f9841ba      -      -      -        -         -      -      -      -    ONLINE
        e30045b7-4a60-40f7-9899-45e4ce166cca      -      -      -        -         -      -      -      -    ONLINE
        0a09baed-9f62-407f-9be8-4909ab3c1060      -      -      -        -         -      -      -      -    ONLINE
        0f571f77-cf5b-493a-bf81-1b4b7e416b61      -      -      -        -         -      -      -      -    ONLINE
        fa835582-aef7-461b-99b4-803ffb30d13b      -      -      -        -         -      -      -      -    ONLINE
        2ce51f18-a0f1-4071-99ac-f3b3896ec42d      -      -      -        -         -      -      -      -    ONLINE
        14792535-5e65-4eab-8993-9cdcaaa4799d      -      -      -        -         -      -      -      -    ONLINE
        33e560ce-e50e-492a-8de4-b823767dd3f6      -      -      -        -         -      -      -      -    ONLINE
        b96570e2-b608-474a-aec5-053506cf0479      -      -      -        -         -      -      -      -    ONLINE
        3a64abe6-379a-4be4-9f4b-b043243fad54      -      -      -        -         -      -      -      -    ONLINE
        c7ee0ddf-17b0-4853-9bb5-9d32e03619f3      -      -      -        -         -      -      -      -    ONLINE
    cache                                         -      -      -        -         -      -      -      -  -
      0e4c710e-b0e0-4b23-bf5c-40db6bc681d4    1.75T   205G  1.55T        -         -     0%  11.5%      -    ONLINE
    spare                                         -      -      -        -         -      -      -      -  -
      79a8d09a-a4dc-467a-866d-e364f4a30c79        -      -      -        -         -      -      -      -     AVAIL
      c6effcbe-3c88-445f-9d02-91b5ec741ec5        -      -      -        -         -      -      -      -     AVAIL
      7121a1a9-21f4-43b1-be4a-a4842ab63d90        -      -      -        -         -      -      -      -     AVAIL
      b8336d4d-0b11-490c-9bd0-77a9b80ce584        -      -      -        -         -      -      -      -     AVAIL
      07ceebe0-b976-43ed-bcc2-2e9737f31666        -      -      -        -         -      -      -      -     AVAIL
      1e8efebc-da56-471b-a46d-1a27d559a7d3        -      -      -        -         -      -      -      -     AVAIL
    ssdpool                                   11.6T  2.79T  8.84T        -         -     2%    23%  1.00x    ONLINE  -
      raidz1-0                                5.81T  1.39T  4.42T        -         -     2%  23.9%      -    ONLINE
        scsi-35000cca05068a8d0                    -      -      -        -         -      -      -      -    ONLINE
        scsi-35000cca050697eac                    -      -      -        -         -      -      -      -    ONLINE
        scsi-35000cca05069d390                    -      -      -        -         -      -      -      -    ONLINE
        scsi-35000cca0506a1718                    -      -      -        -         -      -      -      -    ONLINE
      raidz1-1                                5.81T  1.40T  4.41T        -         -     2%  24.1%      -    ONLINE
        scsi-35000cca0506a4cd8                    -      -      -        -         -      -      -      -    ONLINE
        scsi-35000cca0506a87e4                    -      -      -        -         -      -      -      -    ONLINE
        scsi-35000cca0531605e4                    -      -      -        -         -      -      -      -    ONLINE
        scsi-35000cca0531606f0                    -      -      -        -         -      -      -      -    ONLINE
    cache                                         -      -      -        -         -      -      -      -  -
      d54e0d6a-41f2-4d79-a344-7f3f93793e04    1.75T   884M  1.75T        -         -     0%  0.04%      -    ONLINE
    spare                                         -      -      -        -         -      -      -      -  -
      scsi-35000cca0532a531c                      -      -      -        -         -      -      -      -     AVAIL
      scsi-35000cca053410650                      -      -      -        -         -      -      -      -     AVAIL
    root@TaylorPlex:~# 

    I recently tried to re-import my "main" pool as "mainpool" to see if it helped. It didn't.

    WOW!!! That's a lot of disks :) 

  6. On 4/16/2022 at 7:51 AM, nathan47 said:

    Appreciate the plugin and the work that goes into it. One thing I've noticed is that it doesn't see one of my pools. It's missing my pool named "main".

    I have the exact same issue with my server...

  7. 14 minutes ago, shutterbug said:

    Well I finally got the macinbox vm working, I formatted my 107gig disk, started the OS reinstall of bigsur, it ran for about 1/2hr, appeared to complete without errors, then when it rebooted and I'm back to the screen that has macos base system, macos installer, recovery, uefi shell, shutdown and reset nvram.  If I reinstall again, same things happens.  I seem to be stuck in a loop and never get an option to boot into the OS.

    Exact same on mine, first attempt yesterday, on 6.9RC1 - Completely removed everything, rebooted and getting the same thing on 2nd Try (attempting to install BigSur).

    YvHMQuP.png

    • Like 1
  8. Thanks so much for all that the LinuxServer.Io team does... just got this working on 6.7.0-rc5 with my new 1660 ti and also tested with the Decode patch/script... all appear to be working as expected!

     

    Sent a couple chits for donation...will add some more when I get more in my PayPal account!

     

    -Sw2

  9. 21 hours ago, RandomUser345 said:

    Hey,

     

    @SuperW2

     

    How did you get it working with the Nvidia passthrough?

     

    Let me explain a little.

     

    I have a working OSXHS 10.12.6 that I want to boot on unraid. The install is done. The nvidia drivers are installed (GTX 970), networking works. This is on Ubuntu 18.04.1 and using qemu command line and not libvirt. 

     

    How ever when I try to mimic (including the chipset type - 2.11) the setup on unRaid 6.6.6, the machine keeps rebooting. I tried to do a clean install of a brand new OS X HS but once again the machine keeps rebooting after the apple logo popups. Running clover with the -v option shows that it just reboots after the plus signs. 

     

    Any help would be appreciated since this is the last VM I am trying to set up and would love to have everything working with libvirt as per the video posted. I have been stuck on this for 3-4 days and don't know how to fix it.

    Far from an Expert... but are you passing through a Graphics ROM BIOS?  I have a GTX1080 that I had setup to passthru to my Win10 VM.  I installed the Card in a standalone Win10PC, downloaded the GPU BIOS ROM file with CPU-Z (following one of the processes in SIO Windows VM Videos), then reinstalled back into my unRAID server... I used that same GPU Rom file to the High Sierra VM... before I added the ROM to the VM Config, it wouldn't boot at all with NVidia Card added to Mac VM, once I added that, it booted and I was able to install the nVidia drivers per the SIO Video.  Doubt that helps much, but the ROM file did it for me.

  10. 7 hours ago, david279 said:

    You should be able to do updates. Make sure to keep your clover up to date and any kext you use.

    Sent from my SM-N960U using Tapatalk
     

    I'm going to make a backup copy of the entire VM and try to update again... I did confirm it was the iTunes/OS Security updates... not exactly sure how to update the Clover or kext, I'm just using whatever versions SIO included in the video links.

  11. Thanks again for this great stuff... I re-setup my High Sierra VM with the new video and passed through my Nvidia card and everything was working good...then the OS did an update (iTunes, 10.13.6 security stuff, etc), which I think crashed the whole setup...when it went to reboot just had the circle with slash through it after the Clover boot screen.

     

    So I blew it all away and started over (didn't yet have any data).  My question is what is everyone doing for system/os updates?  Should I be able to do them (not upgrading to Mojave from the App Store) but anything else that Apple tries to push down.  Should I disable all updates (which doesn't sound terribly "safe").

     

    what is everyone else doing for OS/SW updates on the VM's?

    -Wade

  12. 6 hours ago, SuperW2 said:

    OK, I deleted and redownloaded everything (including re-downloading the MacOS High Sierra Installer), new USB Stick, re-downloaded Clover 2.4K r4674, and it's actually booting now and beginning the install process.  So it's not totally complete yet but a lot further along.  I am using Q35-3.0 so far. 

    Well, it boots once at least, which I guess is something... I get as far as installing Clover on the macOS shutting down the VM and restarting (@ About 17:30 in the video where you remove the Boot IMG from the XML) and can never get it to reboot again.  Just get a static Apple Logo on the VNC Window and nothing ever happens after...maybe I'll just wait to see if SIO does an update for the new OS.

     

    -SW2

  13. 1 hour ago, methanoid said:

    Try booting the USB stick in a PC.. Any EFI PC... it should load Clover. If not then you failed at the making your USB stick. If that works then I suggest you post your XML ?

    OK, I deleted and redownloaded everything (including re-downloading the MacOS High Sierra Installer), new USB Stick, re-downloaded Clover 2.4K r4674, and it's actually booting now and beginning the install process.  So it's not totally complete yet but a lot further along.  I am using Q35-3.0 so far. 

  14. 3 minutes ago, methanoid said:

    I wouldnt give up yet... but just try to make sure you know exactly what you have done when you seek help?

     

    You might take heart from this.... Mine failed totally yesterday. I restarted the VM just now and it suddenly decides to load the installer when yesterday it refuses. And I really HONESTLY have not touched any settings at all!!!

     

    FYI, I used Q35 3.0, Clover v2.4k r4674 (latest currently), macOS 10.13.6 (last version, Mojave releases tomorrow!) but the Clover options aren't same as SIO's video so I made some "educated guesses".  And unRAID 6.60

     

    It's installing now... fingers crossed it all finishes and boots okay!

     

    Regardless of how I've configured my VM, it isn't  booting to the initial  boot (I never see the Apple or Clover Screen) so it seems that it's not even recognizing the Primary VDisk boot IMG file made from the Boot USB (which I've recreated several times on multiple USB Sticks).  I guess I don't understand where Clover is even involved as there is no mention of it at all through the first 9 minutes of the video (where SIO boots the VM and gets the clover boot screen).  It feels like I'm missing something or should have watched another video to do other things to prepare for this one.

  15. 11 minutes ago, methanoid said:

     

    SIO=SpaceInvaderOne ;-)

     

    So you used 10.13.6 - he used 10.13.0 - note the MANY comments on video of people who couldnt get it working as they were on later versions of 10.13

    I suspect given you didnt spot that then you probably just used any old version of Clover... Did you use Q35 same version as SIO or the latest 3.0 version? ;-)

     

    Dont ASSume that its unRAID 6.6 (fix your sig BTW) thats at fault when you have clearly failed to follow his guide to the letter. I have tried 10.13.4 and 10.13.6 and failed. But I do know what versions of Clover I have tried and what settings....

     

    The safest thing to get it to work is to use the EXACT same versions of Clover and macOS as SIO with his file pack. There is no guarantee the files he supplies will work with other versions 😞

    Thanks... I did try to use the Q35-2.9 as shown in the video.  There is zero mention of any Clover versions in the updated video what-so-ever (at least up to the halfway point where I couldn't get anything to boot), so I'm not sure how or where I can I have any control over that.  I also have zero clue where to find a older 10.13.0 macOS installer, so I guess I'll just shelve this for other endeavours.  

     

    Sig was super old, forgot to update as I've gone through several HW iterations since last updated.

  16. 26 minutes ago, methanoid said:

    So you used 10.13.0 and the same Clover as SIO?

     


    Sent from my Redmi Note 4 using Tapatalk
     

     

    I created the USB Boot with 10.13.6 Macbook and I'm not sure what SIO is or what version of Clover...Following the SpaceInvader One Updated Video with the "unpatched" Clover.  Created the IMG from the USB, Created the VM, Edited the XML with the parts from the vm-ackintosh text file, boot VM and can't get anything other than "UEFI Interactive Shell v2.2" screen in the VNC.

  17. Updated the other day (maybe a couple weeks ago, whever the last update happened) now cannot start the Handbrake Docker... it had previously been working fine...

     

    sparklyballs/handbrake:latest

     

    Here is Log error.

     

    Fatal server error:

     

    Server is already active for display 1

    If this server is no longer running, remove /tmp/.X1-lock

    and start again.

     

    Openbox-Message: Failed to open the display from the DISPLAY environment variable.

  18. Just updated to the latest Binhex Sickbeard and Sabnzbd and now neither will start.  Both had been working flawlessly since install...

     

    Binhex Deluge also update, but it still seems to start OK...

     

    Here is SAB log file

    2016-02-21 19:54:59,397 DEBG fd 8 closed, stopped monitoring (stderr)>

    2016-02-21 19:54:59,397 DEBG fd 6 closed, stopped monitoring (stdout)>

    2016-02-21 19:54:59,397 INFO exited: sabnzbd (exit status 2; not expected)

    2016-02-21 19:54:59,398 DEBG received SIGCLD indicating a child quit

    2016-02-21 19:55:02,402 INFO spawned: 'sabnzbd' with pid 27

    2016-02-21 19:55:02,594 DEBG 'sabnzbd' stdout output:

    Error:

    Can't write to logfile

     

    2016-02-21 19:55:02,609 DEBG fd 8 closed, stopped monitoring (stderr)>

    2016-02-21 19:55:02,610 DEBG fd 6 closed, stopped monitoring (stdout)>

    2016-02-21 19:55:02,610 INFO exited: sabnzbd (exit status 2; not expected)

    2016-02-21 19:55:02,610 DEBG received SIGCLD indicating a child quit

    2016-02-21 19:55:03,611 INFO gave up: sabnzbd entered FATAL state, too many start retries too quickly

  19.  

    Yes you should.  If you have nothing on the display, that means your not successfully assigning the GPU yet.  There are steps in the wiki relating to GPU pass through that you can try.  I know we have had issues with the GTX 550 in the past, so the 560 may share a similar fate. It is a rather older GPU.  Some things you can try are in the wiki though.  If you have another GPU laying around, I'd give that a shot.

     

    OK, I found a Radeon HD5570 (which is probably a little older than the 560ti still), but re-created the VM with the new GPU, then seeing the video passthrough to the connected monitor.  I still had to click next for all of the default settings with the USB Keyboard on the server before the Kore would connect, but once I did, Kore on my Android tablet then saw the server and connected as I expected it too and am now browsing and adding my shares.

     

    Sorry for blowing up your Template support thread!  Thanks for your help and patience!

  20. You sure your Android device is connected to the same router (over Wifi)?  I can confirm in a test tonight that this works for me with a fresh setup and the Kore app just fine.  I didn't have to enter a username or password at all.  Just let the app search the network, it found the VM no problem.

     

    Most certainly sure, yes... have no issues connecting to my Plex Docker on my Media server from the same Android device(s) and my unRAID console via the browser, etc, I just removed the entire new VM, re-setup everything and no change, doesn't even appear to be getting an IP Address now from my Router, so I think time to call it a night and look at it again in the morning.

     

    -W

    I bet it's your default network bridge. Goto settings -> network settings and see if the network bridge is enabled.  If not, stop the array and enable it.  Once enabled, go to Settings -> VM Manager and make sure that the default bridge is set to br0 and not virbr0.

     

    Remove the existing OpenELEC from the VMs tab, then add a new OpenELEC VM and it will have this new bridge enabled by default. This will ensure you VM gets an IP on the network and is accessible by the Kore app.

     

    I'm been using a "br1" (which is what I changed the bridge name too in my network settings) bridge that I setup previously when playing with Win10 VM, not using virbr0.  It's getting a 192.168.1.xx IP address from my router that I can ping and see on my primary network just fine.

     

    This might be a dumb question, but If I physically plug a monitor into the GPU should I be seeing "something" on that monitor when the VM is running?  I'm getting absolutely nothing...

    Yes you should.  If you have nothing on the display, that means your not successfully assigning the GPU yet.  There are steps in the wiki relating to GPU pass through that you can try.  I know we have had issues with the GTX 550 in the past, so the 560 may share a similar fate. It is a rather older GPU.  Some things you can try are in the wiki though.  If you have another GPU laying around, I'd give that a shot.

     

    I think this was the least old of the old GPU's that I had in my "surplus" box but I will try one of the others.

×
×
  • Create New...