1812

Members
  • Content count

    879
  • Joined

  • Last visited

  • Days Won

    2

1812 last won the day on April 25

1812 had the most liked content!

Community Reputation

42 Good

About 1812

  • Rank
    ¯\_(ツ)_/¯ Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

320 profile views
  1. Here is something interesting, I experienced a similar problem with the same model card recently. I have 2 of them, used them both for 6 months, connected to a LB4M. In one server, about a week ago, the card disappeared from it while running. The server then complained that eth0 was missing (as it is set to that.) I rebooted and it was not in the device list. I figured the card died. But as a check, I moved it to another slot and it worked. After needing to upgrade a video card a few days later, I cycled power again, and again it disappeared. A few days later, and after some data transfers via the backup networking, I cycled the power again, and it again came back. On a nearly identical machine, that card has had no problems ever. So, maybe it is a flaky card? Not sure. Time will tell.
  2. either use seabios instead of ovmf or click the restart command/button on the VNC window, and when the bios loads, go in it an select your startup disc from there and see if it will persist after reboot.
  3. You only need 1 emulator pin, so use 4. The word on the street is that unRaid prefers to use 0. You also have to realize the core count comes into play when looking at my "0" percent. There is 3% load on one thread, but that rounds down to zero because of the total load. Here is another server running 2 vm's (one OS X, one pfSense-firewall/router for the network) and the following dockers: DuckDNS, Plex, Krusader, NetData. Threads 0-3 are isolated for unRaid and dockers. OS X is on threads 6-9, and pfSense is 4-5. Both vm's use emulator pin 1. Total usage shows 4%. If I were to minimize that down to your 8 cores, then my total usage would be 12% with what is currently active on my server. Take away the pfSense vm and that number would probably be cut in half with your core count. I wouldn't expect for you to hit a consistent 0 utilization since you still have to have some resources used to manage the vm, even when it is doing nothing but running the OS clock and other background tasks. And that number will only get bigger with the fewer cores your have. What are you seeing for overall utilization when the vm is twiddling its idle?
  4. Like I said, I don't believe the issue is the setup in this case. You need to investigate the errors I listed.
  5. what guide did you follow in creating the vm? 90% of initial windows vm issues are due to people "winging" it and not following a guide. But I do not believe that to be the problem in this case. you have this error: 2017-05-21 21:12:28.978+0000: 12072: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks 2017-05-21 21:12:28.978+0000: 12072: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id which may be attributable to May 21 20:48:49 Tower kernel: TSC synchronization [CPU#0 -> CPU#1]: May 21 20:48:49 Tower kernel: Measured 14831673997 cycles TSC warp between CPUs, turning off TSC clock. May 21 20:48:49 Tower kernel: tsc: Marking TSC unstable due to check_tsc_sync_source failed
  6. Thanks for chiming in new user who is probably not affiliated with this company in any way... I'm sure we're all convinced to signup now!
  7. 6 threads only used by unraid. Rest for vm's. all 3 vm's use an emulator pin set to use one of the 6 unraid threads. 2 use vnc, 1 uses gpu. If you leave vnc connected, it will never idle at next to nothing because the vnc needs CPU power to process. I set each of the vm's to allow thier "monitor" to sleep and disable screen saver (otherwise it is using CPU to run a screensaver on a closed vnc connection- a waste.
  8. I believe there is an easier way to make the card a bridge in unraid and then just assign the virtual bridge to pfsense. Then pfsense doesn't need the driver and unraid already has it.
  9. system stats netdata-docker by ip... not unless unRaid is running your firewall via pfsense or something similar.
  10. no. http://www.ebay.com/sch/i.html?_odkw=hard+drive+array&_osacat=0&_from=R40&_trksid=p2045573.m570.l1313.TR0.TRC0.H0.Xhard+drive+array+jbod.TRS1&_nkw=hard+drive+array+jbod&_sacat=0
  11. no
  12. I suppose "your mileage may vary."
  13. Without knowing the specifics of your setup/vm's: IF you really wanted to give it a go using sleep, you would probably need to pass through an entire usb card or port to the vm (for hot plugging.) That "should" allow you the possibility to allow the vm to wake. But it may also trigger the KVM hibernate/sleep state, which I don't believe allows user keystrokes to wake it up. If you're using a physical monitor, you can use monitor sleep without issue and still wake the monitor via keystroke using usb card passthrough (and maybe port passthrough.) When I first started on unRaid about a year ago, sleep caused me multiple problems with vm's until ultimately just disabling it. Now, no problems.
  14. Also, here is a screenshot of one of my servers with 3 vm's currently running on threads 6-23, with threads 0-5 isolated for only unraid/dockers. Sleep is disabled on all vm's.
Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.