mr-hexen

Members
  • Posts

    2300
  • Joined

  • Last visited

Posts posted by mr-hexen

  1. Mostly for transcoding, I would think you would want to assign at least two physical cores for transcoding, another two for x264 encoding, thats four physical cores already, 8 will give him extra head room.

     

    I see where you're coming from now. You should know that core / transcode isn't the best way to determine CPU requirements.. Plex has always recommended 2,000 passmarks per 1080p transcode. 2,000 passmarks does not translate into a single core.

     

    If the OP could use the handbrake docker instead, then all CPU horsepower is available to all process whenever its needed. An i7 would do nicely in this situation.

  2. Can do Jon... any idea how I can get Dockers back on 6.2.4?

     

    EDIT: Fixed it. If anyone else runs into this issue I had to 'stop' docker, delete the image, reboot, re-start docker and it's showing running again.

     

    Same steps I've used with bouncing between RC and 6.2.4 took some trial and error and I even included an extra reboot at the end.

     

    My guess is the docker version in 6.3.x upgrades the IMG file in some way and it becomes incompatible with earlier versions of docker, so when we revert back to 6.2.4 it doesn't work.

     

    Still confused as to why a reboot is required to get it going, even if the docker.img is deleted... above my head though.

  3. After upgrading from 6.2.4 to 6.3.0, I get the following in my VM/qemu log.

     

    2017-02-05T20:29:39.741418Z qemu-system-x86_64: -device vfio-pci,host=08:00.0,id=hostdev3,bus=pci.0,addr=0x9: Failed to mmap 0000:08:00.0 BAR 2. Performance may be slow
    2017-02-05T20:29:39.746332Z qemu-system-x86_64: warning: Unknown firmware file in legacy mode: etc/msr_feature_control

     

    I looked back at some old diagnostics from a couple of weeks ago and I did not get this message.  This is for an add-on USB 3.0 controller that I have passed through to the VM.  I have not fully tested the USB but can tell you that it is working on some level as I am typing and using a mouse that is plugged into this device....not sure that the performance may be slow means.

     

    I am post here vs KVM forum since I did not get this message previously.

     

    Any suggestions?

     

    Hi snoopin,

     

    Quick question:  is there any felt impact from the upgrade in terms of your VM, performance, or anything with your USB devices attached to that controller?  If not, the message is likely harmless, but curious if you can trace this back to any symptoms you notice when using the VM.

     

    I also get the same:

     

    2017-02-05T13:30:01.642740Z qemu-system-x86_64: warning: Unknown firmware file in legacy mode: etc/msr_feature_control

     

    And my Ubuntu VM now is terribly slow and laggy. Trying to type in a terminal will yield something like:

     

    apt-get upgggggggggggggggggggggggggggggggggggggggggggggggg

     

    and just hang, then eventually come back. Very bad performance. Was smooth as butter prior to the upgrade of 6.2.4 -> 6.3.0. No config changes, just upgrade through webui.

     

    Ok, assuming this is over VNC.  Can you try this solution from our upgrade notes to see if it fixes it for you?

     

    I was already on Q35 2.5, so I changed it to Q35 2.7 and I still have the same sluggish behavior, and same logs.

     

    And yes, I use the built in VNC interface.

    What about the vnc video driver?

     

    Sent from my SM-G930P using Tapatalk

     

    Same stuttered behavior when changing from QXL to Cirrus. Just tested.....

    Can you repost diagnostics?  Also please share your VM XML.

     

    Sent from my SM-G930P using Tapatalk

     

    Here you are (VM is off at the time of creation, as I can't use it) - I added a VM.xml inside the zip as well (note, I switched Video driver back since it made no difference).

     

    As a data point, I'm experiencing the EXACT issues with my ubuntu VNC VM. I've tried all types of combinations for machine type (440 v q35) and VNC driver (all 3).

     

    I even tried to create a NEW VM using ubuntu 16.04 and 16.10 and I can immediately tell the problem persists, dont even have to install the OS just in the installer it has issues.

     

    My Plex Media Player VM with HD5450 passthru seems to be working just fine.

     

    During the Ubuntu installer, the initial part that is a text only menu works fine, it's only when the GUI is loaded.

  4. <type arch='x86_64' machine='pc-q35-2.3'>hvm</type>

    to:

    <type arch='x86_64' machine='pc-q35-2.7'>hvm</type>

     

    Thanks Gary.  I was at pc-q35-2.5, however the key-presses did not work as expected.  Manually changed the XML to 2.7 and my ElementaryOS VM is back to humming as hoped for. 

     

    edit:    spoke to soon.  the keypresses are now working, however it takes 7 seconds for each press to register ;(  Too tired to dig ATM.

    edit 1:  Ok... 1 dig solved this.  The VM defaulted to using QXL after the 6.3 uprgrade rather than CIRRUS for the VNC driver.  The QXL VNC driver is a DOG on performance

     

    Outside of this, the update has been smooth on 2 machines :)  nice work LT

     

    This is the issue (delayed response in VNC from input) that I am seeing. I've tried all 3 VNC drivers (vmvga, QXL, cirrus). Tried changing q35 to 2.5, 2.6, 2.7.

     

    I'm even seeing this behaviour on new ubuntu VMs running 16.10. I've tried i440, OMVF, SeaBios, etc. and results do not change.

  5. Anyone else see a significant performance degradation in VM's? I have a ubuntu 16.04 vm that I use a test platform for learning linux. I always have used it via VNC and its been OK (usable), but since 3.0 its dog slow.

     

    I have 2 cores assigned, 2GB ram, Q35-2.7 (tried 2.5 and 2.6), none of these settings changed since 6.2.4.

  6. Are you sure you've set the subnet access correctly?

     

    what is the IP address of your unRAID server?

     

    run this command from a command line prompt:

    ifconfig 
    

     

    Either 'br0' or 'eth0' will have your unRAID ip address.

     

    The IP address is 192.168.0.2, and it says the same under eth0 when I run that command.

     

    There is this warning in the log, I'm not sure if this is the issue, what it is or how to fix it:

     

    [warn] iptable_mangle module not supported, you will not be able to connect to ruTorrent or Privoxy outside of your LAN

    [info] Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'

     

    OK, so the LAN_NETWORK entry is your problem.

     

    From your supervisor log

    2017-02-04 23:30:00.921672 [info] LAN_NETWORK defined as '192.168.1.0/24'

     

    This should be 192.168.0.0/24

  7. Are you sure you've set the subnet access correctly?

     

    what is the IP address of your unRAID server?

     

    run this command from a command line prompt:

    ifconfig 
    

     

    Either 'br0' or 'eth0' will have your unRAID ip address.

     

    The IP address is 192.168.0.2, and it says the same under eth0 when I run that command.

     

    There is this warning in the log, I'm not sure if this is the issue, what it is or how to fix it:

     

    [warn] iptable_mangle module not supported, you will not be able to connect to ruTorrent or Privoxy outside of your LAN

    [info] Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'

     

    You can try, but I've assumed these attempts to connect are from within the same network?

  8. @mr-hexen, im not sure if your aware of this but i now have a much slicker way of getting the iptable mangle support working than start-stop of vm, see my VPN FAQ link below in my sig, it works a treat!.

     

    Didnt know you had that in the FAQ, FYI, the "code" is missing a quotation at the start of the second echo command.

  9. I recently switched from the transmissionvpn docker to this delugevpn in hopes of getting a running torrent container. Sadly I have had no luck with either. I just do not understand why every container is broken now. I'd happily download an older build if I could figure that out.

     

    Either way, I've attached a log. If someone can find something in there and help out I'd be grateful. Thanks.

    OK firstly your in the wrong thread, this is for delugevpn not rtorrentvpn, so any replies in there please. So taking a look at your logs that is a successful start, there is nothing wrong there, are you attempting to connect to the webui from inside your lan yes? You would need to connect using http://<your unraid servers IP>:<host port mapped to 9080> I can assure you the VPN dockers I have authored are not "broken".

     

    Sent from my SM-G900F using Tapatalk

     

    Well I'm using the delugevpn so I figured I'd post in the delugevpn support thread. My mistake.

     

    Anyway neither 9080 or 8112 work for the webui. 8112 being the port used in the webui shortcut.

     

    edit: Starting it without the VPN enabled works. I can access the ui perfectly.

    edit2: Got it working.

     

    Did your solution have to do with enabling then disabling VM's ?

  10. Understand -- but clearly adding a rack doesn't cause an increase in your utilities by itself.

     

    I can, of course, understand the desire to "fill the rack" with nifty new toys that will consume more power  :)

     

    Don't feel too bad about your utilities though ... you're not the only place that has fairly high rates.  My water bill averages well over $100/month;  garbage collection is another $50; and my average electric bill is fairly close to yours.  Plus we have very high real estate taxes (~ $14,000/yr for our house).    My mortgage-free house costs me more/month than any mortgage payment I ever had !!

     

    Gary, if you dont mind how big (sqft) is your house? When comparing things like utility cost, size, among many many other factors, is relevant.

     

    I am in a 1300sqft townhome and my hydro (electric) bill ranges from 120 in the winter to 200 in the summer.