captain134

Members
  • Posts

    53
  • Joined

  • Last visited

Everything posted by captain134

  1. This is incorrect. You can use a gpu with multiple dockers(I use it with plex and unmanic) fine. You shouldn't share it if it is passed through to a VM though.
  2. Your question was answered 6 posts below your original post.
  3. I have figured it out. Had to enable SSL. Thanks
  4. I have run into an issue. Any help would be greatly appreciated. I had to give Plex docker its own IP for another project which works great but has broken Plexpy. I added the new IP of plex in the plexpy settings and if I click verify I get a check mark but plexpy can't actually communicate with plex and I get the "There was an error communicating with your Plex Server."
  5. I am not able to get tvhProxy to work. I have assigned plex, tvheadend and tvhproxy their own ips. I have tried many different configs but get the same 500 internal server error. ANY help would be greatly appreciated. Thanks in advance.
  6. I just installed for the first time and can confirm the same.
  7. Hi Thanks for all your hard work with these dockers. I am having trouble with the PlexRequests docker that previously worked great. I have deleted the docker and image and tried re-installing but I get the same following error: Starting container on Tue Nov 22 13:29:36 MST 2016 Updating repository HEAD is now at bd6572d Version bump Already up-to-date. Selecting the desired branch Using the master branch Already on 'master' Your branch is up-to-date with 'origin/master'. Fixing permissions Updating meteor. . . may take a while if meteor servers are being slow. The web gui will not go up until update is completed and there will be another message about PlexRquests starting Changes to your project's package version selections from updating the release: accounts-base upgraded from 1.2.2 to 1.2.14 accounts-password upgraded from 1.1.4 to 1.3.3 allow-deny added, version 1.0.5 autoupdate upgraded from 1.2.4 to 1.2.8 babel-compiler* upgraded from 5.8.24_1 to 6.13.0 babel-runtime* upgraded from 0.1.4 to 1.0.1 base64 upgraded from 1.0.4 to 1.0.10 binary-heap upgraded from 1.0.4 to 1.0.10 blaze upgraded from 2.1.3 to 2.1.8 blaze-tools upgraded from 1.0.4 to 1.0.9 boilerplate-generator upgraded from 1.0.4 to 1.0.11 caching-compiler upgraded from 1.0.0 to 1.0.4 caching-html-compiler upgraded from 1.0.2 to 1.0.6 callback-hook upgraded from 1.0.4 to 1.0.10 check upgraded from 1.1.0 to 1.2.4 ddp upgraded from 1.2.2 to 1.2.5 ddp-client upgraded from 1.2.1 to 1.2.5 ddp-common upgraded from 1.2.2 to 1.2.5 ddp-rate-limiter upgraded from 1.0.0 to 1.0.6 ddp-server upgraded from 1.2.2 to 1.2.6 deps upgraded from 1.0.9 to 1.0.12 diff-sequence upgraded from 1.0.1 to 1.0.7 ecmascript upgraded from 0.1.6 to 0.6.1 ecmascript-runtime upgraded from 0.2.6 to 0.3.15 ejson upgraded from 1.0.7 to 1.0.13 email upgraded from 1.0.8 to 1.1.18 fastclick upgraded from 1.0.7 to 1.0.11 geojson-utils upgraded from 1.0.4 to 1.0.10 hot-code-push upgraded from 1.0.0 to 1.0.4 html-tools upgraded from 1.0.5 to 1.0.10 htmljs upgraded from 1.0.5 to 1.0.10 http upgraded from 1.1.1 to 1.2.10 id-map upgraded from 1.0.4 to 1.0.9 jquery upgraded from 1.11.4 to 1.11.10 launch-screen upgraded from 1.0.4 to 1.0.11 livedata upgraded from 1.0.15 to 1.0.18 localstorage upgraded from 1.0.5 to 1.0.12 logging upgraded from 1.0.8 to 1.1.16 meteor upgraded from 1.1.10 to 1.6.0 meteor-base upgraded from 1.0.1 to 1.0.4 minifier-css added, version 1.1.13 minifier-js added, version 1.1.13 minifiers removed from your project minimongo upgraded from 1.0.10 to 1.0.18 mobile-experience upgraded from 1.0.1 to 1.0.4 mobile-status-bar upgraded from 1.0.6 to 1.0.12 modules added, version 0.7.7 modules-runtime added, version 0.7.7 mongo upgraded from 1.1.3 to 1.1.14 mongo-id upgraded from 1.0.1 to 1.0.6 npm-bcrypt upgraded from 0.7.8_2 to 0.9.2 npm-mongo* upgraded from 1.4.39_1 to 2.2.11_2 observe-sequence upgraded from 1.0.7 to 1.0.12 ordered-dict upgraded from 1.0.4 to 1.0.9 promise upgraded from 0.5.1 to 0.8.8 random upgraded from 1.0.5 to 1.0.10 rate-limit upgraded from 1.0.0 to 1.0.6 reactive-dict upgraded from 1.1.3 to 1.1.8 reactive-var upgraded from 1.0.6 to 1.0.11 reload upgraded from 1.1.4 to 1.1.11 retry upgraded from 1.0.4 to 1.0.7 routepolicy upgraded from 1.0.6 to 1.0.12 service-configuration upgraded from 1.0.5 to 1.0.11 session upgraded from 1.1.1 to 1.1.7 sha upgraded from 1.0.4 to 1.0.9 spacebars upgraded from 1.0.7 to 1.0.12 spacebars-compiler upgraded from 1.0.7 to 1.0.12 srp upgraded from 1.0.4 to 1.0.10 standard-minifier-css added, version 1.0.8 standard-minifier-js added, version 1.0.8 standard-minifiers upgraded from 1.0.2 to 1.0.6 templating upgraded from 1.1.5 to 1.1.9 templating-tools upgraded from 1.0.0 to 1.0.4 tracker upgraded from 1.0.9 to 1.1.1 ui upgraded from 1.0.8 to 1.0.11 underscore upgraded from 1.0.4 to 1.0.10 url upgraded from 1.0.5 to 1.0.11 webapp upgraded from 1.2.3 to 1.3.12 webapp-hashing upgraded from 1.0.5 to 1.0.9 * These packages have been updated to new versions that are not backwards compatible. plexrequests-meteor: updated to Meteor 1.4.2.3. Changes to your project's package version selections from updating package : alanning:roles upgraded from 1.2.14 to 1.2.15 aldeed:autoform upgraded from 5.7.1 to 5.8.1 aldeed:collection2 upgraded from 2.5.0 to 2.10.0 aldeed:collection2-core added, version 1.2.0 aldeed:schema-deny added, version 1.1.0 aldeed:schema-index added, version 1.1.1 aldeed:simple-schema upgraded from 1.3.3 to 1.5.3 aslagle:reactive-table upgraded from 0.8.18 to 0.8.38 autoupdate upgraded from 1.2.8 to 1.2.11 blaze upgraded from 2.1.8 to 2.1.9 blaze-html-templates upgraded from 1.0.1 to 1.0.5 blaze-tools upgraded from 1.0.9 to 1.0.10 caching-compiler upgraded from 1.0.4 to 1.1.9 caching-html-compiler upgraded from 1.0.6 to 1.0.7 coffeescript upgraded from 1.0.11 to 1.0.17 dburles:collection-helpers upgraded from 1.0.4 to 1.1.0 ddp-client upgraded from 1.2.5 to 1.2.9 ddp-common upgraded from 1.2.5 to 1.2.8 ddp-server upgraded from 1.2.6 to 1.2.10 fastclick upgraded from 1.0.11 to 1.0.13 fortawesome:fontawesome upgraded from 4.4.0 to 4.7.0 fourseven:scss upgraded from 3.4.1 to 3.10.1 html-tools upgraded from 1.0.10 to 1.0.11 htmljs upgraded from 1.0.10 to 1.0.11 iron:router upgraded from 1.0.12 to 1.0.13 launch-screen upgraded from 1.0.11 to 1.0.12 less upgraded from 2.5.1 to 2.5.7 mdg:validation-error added, version 0.2.0 minifier-css upgraded from 1.1.13 to 1.2.15 minifier-js upgraded from 1.1.13 to 1.2.15 minimongo upgraded from 1.0.18 to 1.0.19 mobile-status-bar upgraded from 1.0.12 to 1.0.13 momentjs:moment upgraded from 2.10.6 to 2.17.0 observe-sequence upgraded from 1.0.12 to 1.0.14 percolate:synced-cron upgraded from 1.3.0 to 1.3.2 raix:eventemitter added, version 0.1.3 retry upgraded from 1.0.7 to 1.0.9 shell-server added, version 0.2.1 softwarerero:accounts-t9n upgraded from 1.1.6 to 1.3.6 spacebars upgraded from 1.0.12 to 1.0.13 spacebars-compiler upgraded from 1.0.12 to 1.0.13 standard-minifier-css upgraded from 1.0.8 to 1.3.2 standard-minifier-js upgraded from 1.0.8 to 1.2.1 standard-minifiers removed from your project templating upgraded from 1.1.9 to 1.2.15 templating-compiler added, version 1.2.15 templating-runtime added, version 1.2.15 templating-tools upgraded from 1.0.4 to 1.0.5 themeteorchef:bert upgraded from 2.1.0 to 2.1.1 ui upgraded from 1.0.11 to 1.0.12 useraccounts:bootstrap upgraded from 1.12.4 to 1.14.2 useraccounts:core upgraded from 1.12.4 to 1.14.2 The following top-level dependencies were not updated to the very latest version available: * ongoworks:security 1.3.0 (2.0.1 is available) * twbs:bootstrap 4.0.0-alpha (4.0.0-alpha2 is available) Newer versions of the following indirect dependencies are available: * autoupdate 1.2.11 (1.3.12 is available) * blaze 2.1.9 (2.2.0 is available) * coffeescript 1.0.17 (1.11.1_4 is available) * ddp-client 1.2.9 (1.3.2 is available) * ddp-server 1.2.10 (1.3.12 is available) * launch-screen 1.0.12 (1.1.0 is available) * less 2.5.7 (2.7.8 is available) * mdg:validation-error 0.2.0 (0.5.1 is available) To update one or more of these packages, pass their names to `meteor update`, or just run `meteor update --all-packages`. Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 115 Nov 22 13:30:11 c11fa061e596 syslog-ng[122]: syslog-ng starting up; version='3.5.3' Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 115 Nov 22 13:30:11 c11fa061e596 syslog-ng[122]: syslog-ng starting up; version='3.5.3' [[[[[ /config/plexrequests-meteor ]]]]] => Started proxy. Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/ => Started MongoDB. [34mW20161122-13:30:27.524(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:27.550(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 [34mW20161122-13:30:28.778(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 => Your application is crashing. Waiting for file change. [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 [34mW20161122-13:30:28.778(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 => Your application is crashing. Waiting for file change. I am wondering if anyone else has this issue. Also any help would be appreciated. Thanks in advance.
  8. For me, pinning and isolating cpus is what solved this issue. See : https://lime-technology.com/forum/index.php?topic=49051.0
  9. That's good I hope you have better luck with that GPU. What a good idea to attach a mouse before installation! I have never thought of doing that I just fought my way through the vnc mouse installation trying to convince myself its kinda fun! Has anyone tried passing bluetooth and using a bluetooth mouse and keyboard? My Server is in another room within bluetooth range. Was thinking of doing HDMI over CAT6 to desk but i don't have a way to get keyboard and mouse over there. I have passed through both my internal bluetooth and a bluetooth dongle and they work as expected in Sierra with a Apple Magic Trackpad.
  10. Interesting that you get it with a OSX vm. I was thinking it was related to Windows because of the fact the it doesn't show until after the desktop has loaded.
  11. You don't "need" IGPU. See https://lime-technology.com/forum/index.php?topic=52960.0
  12. Still experiencing this on 6.3 RC3. Can anyone else on 6.3 confirm if they are getting this as well?
  13. Can you verify that Hyper V is enabled in edit VM menu? Maybe try toggling it even if it is enabled.
  14. I see you're already stubbing 2 devices via vfio-pci in your kernel append line: vfio-pci.ids=1b21:0612,144d:a802 Can you try adding the gigabit ethernet to that as well, reboot and see if the smbus errors still happen?: vfio-pci.ids=1b21:0612,144d:a802,8086:10d3 Yeah I don't remember why I stopped stubbing the NIC but I added it back to syslinux and no change in the error. I have added another diagnostic in case it is of help. Thanks for looking. unjosh-diagnostics-20161020-1907.zip
  15. Thanks for adding more info. For the record the HID Button driver issue seems to be a spelling mistake by windows devs. See https://bugzilla.redhat.com/show_bug.cgi?id=1377155 Also I upgraded to 6.3.0 RC2 and the smbus error is still there.
  16. Thanks a lot for looking at it. I will see if I can find anything about the firmware error. For the record, I have always had the reset mechanism error. Do you know what it means/if it is harmful?
  17. Hello All of a sudden my Windows 10 VM log is filled with the following error, repeated over and over. smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 I am not finding much info on the internet about the error so any help would be greatly appreciated. For the record, the vm continues to work normally. Thanks in advance to anyone who takes the time to have a look. unjosh-diagnostics-20161017-1451.zip
  18. Off the top of my head but goto Device manager, find the mouse, right click and goto properties, goto power management, uncheck "Allow windows to put this device to sleep". Something like that. Sent from my Nexus 6P using Tapatalk
  19. Hi, First thanks for your guide. I followed the instructions, and tried to boot using VNC. However the loading takes ages(hours and never completes) and I don't know why ... Here is my XML <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>macOS</name> <uuid>7b5d8655-5ac8-b824-eb8c-5435faf61f66</uuid> <metadata> <vmtemplate xmlns="unraid" name="macOS" icon="/mnt/user/ISOS/OSX/OSX-10.12.png"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/7b5d8655-5ac8-b824-eb8c-5435faf61f66_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>Penryn</model> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/disks/Samsung_SSD_850_EVO_250GB_S2R6NX0H750197X/Mac OS Sierra/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='sata'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOS/OSX/sierra_usb'/> <backingStore/> <target dev='hda' bus='sata'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:00:20:30'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </interface> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x07' function='0x0'/> </memballoon> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=OSKEYS/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel'/> </qemu:commandline> </domain> Any idea? Thanks "64 Character OSK Key (You will need a real Mac to get this and I will NOT provide one). Read the references below for more information on this."
  20. Hi I am having very similar issues. Basically transferring from an Unraid share to a second windows Vdisk shows very poor performance and will make unraid webui and dockers etc... unreachable. I am really pulling my hair out over this so ANY help would be appreciated. I tried changing vdisk type to qcow instead of raw and got the best results yet as in most SMB transfers would finish without breaking unraid however things like allocating disk space in steam would crash. One similarity I noticed with OP is x99 platform. Maybe a clue? I have reset cmos, wiped unraid flash and started fresh, removed all hardware that was not needed. Tried all different network configs. Diagnostics attached. unjosh-diagnostics-20161008-1115.zip
  21. In my experience, if you stub the GPU, you wont get the ghosting and will have better results.
  22. I also get these in log with same setup. Asus x99-deluxe. However my windows 10 VM doesn't crash so maybe your issue is elsewhere.