bungee91

That would explain it!.. I can't exactly "dial his digits" but will see what's what on the Emby forum. Thanks for checking into it for me!

He's bragging about it here https://emby.media/community/index.php?/topic/40166-new-install-db-performance/page-1 Since I can't get to Emby manage server/logs to grab a server log (the way I typically do this when needed) Is there a way to complete this attaching to the container and entering a command to download it? Or is it just sitting in my /config directory for the container and I can grab/attach from there?

Yeah, I was hoping to complete a fresh install to checkout the DB improvements Luke has been bragging about. Hmm...... Well I'm uncertain, just know it is completely dead for me at the moment and I grab a fresh image and get the same thing. I wouldn't think it's the changes to Emby itself, since I rolled back to a backup from last week (which was certainly working), and had the same issue(s). I'm attaching the log entry from the Docker log in UnRAID hoping there is something obvious in there. Currently any trying to run the beta container causes me enough issue with UnRAID UI that I have to issue an SSH docker stop EmbyServerBeta in order for things to work again. I have no idea how I could have broken this, but if it is working for others then I'm at a miss. I may post on the Emby forum, if not may just have to run the stable for now. I currently see this in the log, repeats multiple times: Info, Main, Emby Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /config -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 4.8.7.0 64-Bit OS: True 64-Bit Process: True Mono: 4.6.1 (Stable 4.6.1.5/ef43c15 Sat Oct 22 13:52:40 UTC 2016) Processor count: 12 Program data path: /config Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe Info, ImageMagick, ImageMagick version: ImageMagick 6.9.5-5 Q8 x86_64 2016-10-01 http://www.imagemagick.org appHost.Init Info, App, Application version: 3.1.218.0 Info, App, Application configuration: {"EnableUPnP":true,"PublicPort":8096,"PublicHttpsPort":8920,"HttpServerPortNumber":8096,"HttpsPortNumber":8920,"EnableHttps":false,"EnableInternetProviders":true,"IsPortAuthorized":false,"EnableCaseSensitiveItemIds":false,"SeasonZeroDisplayName":"Specials","SaveLocalMeta":false,"PreferredMetadataLanguage":"en","MetadataCountryCode":"US","SortReplaceCharacters":[".","+","%"],"SortRemoveCharacters":[",","&","-","{","}","'"],"SortRemoveWords":["the","a","an"],"MinResumePct":5,"MaxResumePct":90,"MinResumeDurationSeconds":300,"LibraryMonitorDelay":60,"EnableDashboardResponseCaching":true,"EnableDashboardResourceMinification":true,"ImageSavingConvention":"Compatible","MetadataOptions":[{"ItemType":"Book","ImageOptions":[{"Type":"Backdrop","Limit":1,"MinWidth":1280}],"DisabledMetadataSavers":[],"LocalMetadataReaderOrder":[],"DisabledMetadataFetchers":[],"MetadataFetcherOrder":[],"DisabledImageFetchers":[],"ImageFetcherOrder":[]},{"ItemType":"Movie","ImageOptions":[{"Type":"Backdrop","Limit":1,"MinWidth":1280},{"Type":"Art","Limit":0,"MinWidth":0},{"Type":"Disc","Limit":0,"MinWidth":0},{"Type":"Primary","Limit":1,"MinWidth":0},{"Type":"Banner","Limit":0,"MinWidth":0},{"Type":"Thumb","Limit":1,"MinWidth":0},{"Type":"Logo","Limit":1,"MinWidth":0}],"DisabledMetadataSavers":[],"LocalMetadataReaderOrder":[],"DisabledMetadataFetchers":[],"MetadataFetcherOrder":[],"DisabledImageFetchers":[],"ImageFetcherOrder":[]},{"ItemType":"MusicVideo","ImageOptions":[{"Type":"Backdrop","Limit":1,"MinWidth":1280},{"Type":"Art","Limit":0,"MinWidth":0},{"Type":"Disc","Limit":0,"MinWidth":0},{"Type":"Primary","Limit":1,"MinWidth":0},{"Type":"Banner","Limit":0,"MinWidth":0},{"Type":"Thumb","Limit":1,"MinWidth":0},{"Type":"Logo","Limit":1,"MinWidth":0}],"DisabledMetadataSavers":[],"LocalMetadataReaderOrder":[],"DisabledMetadataFetchers":[],"MetadataFetcherOrder":[],"DisabledImageFetchers":[],"ImageFetcherOrder":[]},{"ItemType":"Series","ImageOptions":[{"Type":"Backdrop","Limit":1,"MinWidth":1280},{"Type":"Art","Limit":0,"MinWidth":0},{"Type":"Primary","Limit":1,"MinWidth":0},{"Type":"Banner","Limit":1,"MinWidth":0},{"Type":"Thumb","Limit":1,"MinWidth":0},{"Type":"Logo","Limit":1,"MinWidth":0}],"DisabledMetadataSavers":[],"LocalMetadataReaderOrder":[],"DisabledMetadataFetchers":[],"MetadataFetcherOrder":[],"DisabledImageFetchers":[],"ImageFetcherOrder":[]},{"ItemType":"MusicAlbum","ImageOptions":[{"Type":"Backdrop","Limit":0,"MinWidth":1280},{"Type":"Disc","Limit":0,"MinWidth":0}],"DisabledMetadataSavers":[],"LocalMetadataReaderOrder":[],"DisabledMetadataFetchers":["TheAudioDB"],"MetadataFetcherOrder":[],"DisabledImageFetchers":[],"ImageFetcherOrder":[]},{"ItemType":"MusicArtist","ImageOptions":[{"Type":"Backdrop","Limit":1,"MinWidth":1280},{"Type":"Banner","Limit":0,"MinWidth":0},{"Type":"Art","Limit":0,"MinWidth":0},{"Type":"Logo","Limit":0,"MinWidth":0}],"DisabledMetadataSavers":[],"LocalMetadataReaderOrder":[],"DisabledMetadataFetchers":["TheAudioDB"],"MetadataFetcherOrder":[],"DisabledImageFetchers":[],"ImageFetcherOrder":[]},{"ItemType":"BoxSet","ImageOptions":[{"Type":"Backdrop","Limit":1,"MinWidth":1280},{"Type":"Primary","Limit":1,"MinWidth":0},{"Type":"Thumb","Limit":1,"MinWidth":0},{"Type":"Logo","Limit":1,"MinWidth":0},{"Type":"Art","Limit":0,"MinWidth":0},{"Type":"Disc","Limit":0,"MinWidth":0},{"Type":"Banner","Limit":0,"MinWidth":0}],"DisabledMetadataSavers":[],"LocalMetadataReaderOrder":[],"DisabledMetadataFetchers":[],"MetadataFetcherOrder":[],"DisabledImageFetchers":[],"ImageFetcherOrder":[]},{"ItemType":"Season","ImageOptions":[{"Type":"Backdrop","Limit":0,"MinWidth":1280},{"Type":"Primary","Limit":1,"MinWidth":0},{"Type":"Banner","Limit":0,"MinWidth":0},{"Type":"Thumb","Limit":0,"MinWidth":0}],"DisabledMetadataSavers":[],"LocalMetadataReaderOrder":[],"DisabledMetadataFetchers":["The Open Movie Database","TheMovieDb"],"MetadataFetcherOrder":[],"DisabledImageFetchers":[],"ImageFetcherOrder":[]},{"ItemType":"Episode","ImageOptions":[{"Type":"Backdrop","Limit":0,"MinWidth":1280},{"Type":"Primary","Limit":1,"MinWidth":0}],"DisabledMetadataSavers":[],"LocalMetadataReaderOrder":[],"DisabledMetadataFetchers":["The Open Movie Database"],"MetadataFetcherOrder":[],"DisabledImageFetchers":["TheMovieDb"],"ImageFetcherOrder":[]}],"EnableAutomaticRestart":true,"SkipDeserializationForBasicTypes":false,"SkipDeserializationForPrograms":false,"SkipDeserializationForAudio":false,"PathSubstitutions":[],"UICulture":"en-us","PeopleMetadataOptions":{"DownloadActorMetadata":true,"DownloadDirectorMetadata":true,"DownloadProducerMetadata":false,"DownloadWriterMetadata":false,"DownloadComposerMetadata":false,"DownloadOtherPeopleMetadata":false,"DownloadGuestStarMetadata":false},"SaveMetadataHidden":false,"ContentTypes":[],"RemoteClientBitrateLimit":0,"SharingExpirationDays":30,"Migrations":[],"MigrationVersion":0,"SchemaVersion":0,"SqliteCacheSize":0,"EnableAnonymousUsageReporting":true,"EnableStandaloneMusicKeys":false,"EnableLocalizedGuids":true,"EnableFolderView":true,"EnableGroupingIntoCollections":false,"DisplaySpecialsWithinSeasons":true,"DisplayCollectionsView":false,"LocalNetworkAddresses":[],"CodecsUsed":[],"EnableChannelView":false,"EnableExternalContentInSuggestions":true,"EnableSimpleArtistDetection":false,"ImageExtractionTimeoutMs":0,"EnableDebugLevelLogging":false,"EnableAutoUpdate":true,"SystemUpdateLevel":"Release","LogFileRetentionDays":3,"RunAtStartup":false,"IsStartupWizardCompleted":false} Error, Main, UnhandledException *** Error Report *** Version: 3.1.218.0 Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /config -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 4.8.7.0 64-Bit OS: True 64-Bit Process: True Mono: 4.6.1 (Stable 4.6.1.5/ef43c15 Sat Oct 22 13:52:40 UTC 2016) Processor count: 12 Program data path: /config Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe One or more errors occurred. System.AggregateException at System.Threading.Tasks.Task.WaitAll (System.Threading.Tasks.Task[] tasks, System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00242] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 at System.Threading.Tasks.Task.WaitAll (System.Threading.Tasks.Task[] tasks, System.Int32 millisecondsTimeout) [0x00000] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 at System.Threading.Tasks.Task.WaitAll (System.Threading.Tasks.Task[] tasks) [0x00000] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 at MediaBrowser.Server.Mono.MainClass.RunApplication (Emby.Server.Core.ServerApplicationPaths appPaths, MediaBrowser.Model.Logging.ILogManager logManager, Emby.Server.Core.StartupOptions options) [0x00166] in <23532ed855cb4ae29716d75e2cb84a3f>:0 at MediaBrowser.Server.Mono.MainClass.Main (System.String[] args) [0x0008a] in <23532ed855cb4ae29716d75e2cb84a3f>:0 InnerException: System.IO.FileNotFoundException Could not load file or assembly or one of its dependencies. at Emby.Common.Implementations.BaseApplicationHost`1[TApplicationPathsType].DiscoverTypes () [0x0000b] in <844fc8ef344c43128068ee1b7b9c24a8>:0 at Emby.Common.Implementations.BaseApplicationHost`1+<Init>d__104[TApplicationPathsType].MoveNext () [0x0010c] in <844fc8ef344c43128068ee1b7b9c24a8>:0 UnhandledException One or more errors occurred. System.AggregateException at System.Threading.Tasks.Task.WaitAll (System.Threading.Tasks.Task[] tasks, System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00242] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 at System.Threading.Tasks.Task.WaitAll (System.Threading.Tasks.Task[] tasks, System.Int32 millisecondsTimeout) [0x00000] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 at System.Threading.Tasks.Task.WaitAll (System.Threading.Tasks.Task[] tasks) [0x00000] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 at MediaBrowser.Server.Mono.MainClass.RunApplication (Emby.Server.Core.ServerApplicationPaths appPaths, MediaBrowser.Model.Logging.ILogManager logManager, Emby.Server.Core.StartupOptions options) [0x00166] in <23532ed855cb4ae29716d75e2cb84a3f>:0 at MediaBrowser.Server.Mono.MainClass.Main (System.String[] args) [0x0008a] in <23532ed855cb4ae29716d75e2cb84a3f>:0 InnerException: System.IO.FileNotFoundException Could not load file or assembly or one of its dependencies. at Emby.Common.Implementations.BaseApplicationHost`1[TApplicationPathsType].DiscoverTypes () [0x0000b] in <844fc8ef344c43128068ee1b7b9c24a8>:0 at Emby.Common.Implementations.BaseApplicationHost`1+<Init>d__104[TApplicationPathsType].MoveNext () [0x0010c] in <844fc8ef344c43128068ee1b7b9c24a8>:0 EmbyServerBeta-DockerLog.txt

If I can provide any information from attaching to the Docker, or the log from it that would be helpful in diagnosing this issue, please let me know. Been running the beta for 6+ months now without any issues that were this large of an issue (in that for me it isn't working at all currently).

I understand, and appreciate the support here. However, for me anyhow after the update and also trying a fresh install, the Beta version is completely hosed at the moment.. I'm pretty certain you've moved away from UnRAID (thank you for the continued support BTW!), so I'm uncertain if you can test this or not. I updated to 6.3RC4, and also took the update showing for the EmbyServerBeta Docker. Reboot, Emby won't connect at all. Put back my week old backed up /config folder (local appdata user location) thinking that would help, start the Docker, nope, still nothing, refuses to connect. Stop that Docker, install a fresh copy of the stable version, connects right away. So unless I did something, I think the Beta Docker we're currently pulling doesn't work. Or somehow it is just me, IDK, I wouldn't think so, but who knows!

Took an update to the beta Emby container, now Emby seems broken (won't connect, seems to hang UnRAID WebUI also). I see you posted this in the Linux thread (not specifically the Docker one) on Emby website that "Yes some of the repos became corrupt. They had to be completely purged and rebuilt." https://emby.media/community/index.php?/topic/13029-ubuntu/page-40. Not sure if this is still the case, I tried removing image and reinstalling, with the same result. Anyway to put in the old base image so that I can get the beta version back up and running? I stopped the beta Docker and installed the stable release and it worked without issue.

It's not specific to you, or your setup, others have reported the same condition when installing Avast. I do not believe they found a solution, other than using an alternative antivirus. If you're interested in their thoughts, a quick search should be able to find those postings.

-Setting MSI Interrupt can likely be added to this section, if not list this somewhere. -Information on not being able to assign the same USB device ID if multiple same devices are present. May be useful to give direction that a passed USB card can alleviate this issue. -Information/recommendation for assigning thread pairs (dlandon's performance improvement sticky presents this info currently). Can't recall, do we currently give good direction for stubbing to use the VM editor to assign stubbed devices?

Alright, this is now very interesting!! I've taken the advice that I don't want to be true, but know damn well something is not right with my setup.. These errors started to occur with the GT720 assigned (so my previous thoughts were incorrect). So, I purchased a new MB, CPU and using my "new" ram (recently replaced from Crucial, thought it was related to my issue) which is also on the QVL for this board (Currently have an ASRock Extreme4, 5820k, and Crucial 3X8GB DDR4). I will say I didn't run Memtest on this new setup, just left it at auto and booted up. All settings in the BIOS set to default/auto with the exception of VTx and VT-d set to enabled. The exact same order 4 page allocation failure is showing up!. Considering it seems to always be associated with only the CPU cores to a specific VM titled "Main" (cores 4,5,10,11), I'm going to make a new VM from scratch and see if this is resolved. I can't for the life of me think what the VM could be doing to cause these errors!?! My previous (and keeping) hardware MB/CPU/RAM is currently undergoing grueling stress testing and Memtest's to likely find zero issues, since it is highly unlikely (IMHO) that the exact same error is present on completely different CPU/MB/Ram. Always open to opinions and insight, I will figure this out! Attached newest diagnostics with new hardware installed. It could be some kind of bug with Haswell-E, however no one else seems to have this issue, so that is pretty unlikely. Current theory: Somehow, someway my VM seems to be violating a RAM related rule, causing this to occur. I don't know of any process in particular within Windows that is triggered or occurs to make this happen. The "Main" VM only has 4GB assigned with this new hardware, vs the 12GB prior on my regular CPU/MB/RAM. No other changes with the exception of removing pass through of a USB controller. Edit: Added my XML for "Main" VM (renamed to .txt), nothing special going on within it, the editor was used for the most recent edits. Uncertain the virtio drivers currently installed, but fast-startup off, high performance on, installed all drivers at time of install in recommended order, all wiki best practices followed. server-diagnostics-20161026-1311.zip Main.txt

Provide VM XML's at a minimum, diagnostic output would also be helpful.

Thanks, I had found the same when I investigated it after that post. If I can be of any help, I can provide logs, etc... to help in finding the culprit of this issue, just let me know.

Glad to hear, it looked like that was the culprit.

Well, that was short lived... I'm out of ideas.. It looks different now, but it's back. Oct 18 16:12:59 Server kernel: qemu-system-x86: page allocation failure: order:4, mode:0x260c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO|__GFP_NOTRACK) Oct 18 16:12:59 Server kernel: CPU: 5 PID: 11355 Comm: qemu-system-x86 Not tainted 4.7.6-unRAID #1 and Oct 18 16:13:28 Server kernel: WARNING: CPU: 5 PID: 11355 at arch/x86/events/intel/ds.c:334 reserve_ds_buffers+0x119/0x353 Oct 18 16:13:28 Server kernel: alloc_bts_buffer: BTS buffer allocation failure Oct 18 16:13:28 Server kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod ipmi_devintf igb mxm_wmi x86_pkg_temp_thermal coretemp kvm_intel kvm fbcon bitblit fbcon_rotate fbcon_ccw fbcon_ud fbcon_cw softcursor font ast e1000e drm_kms_helper cfbfillrect cfbimgblt cfbcopyarea ttm drm i2c_i801 agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops fb ptp fbdev pps_core i2c_algo_bit i2c_core ahci libahci sata_mv ipmi_si wmi [last unloaded: igb] Repeat 3-4 times. Attached newest diagnostics, no idea, will switch back to the GT720 and see what happens. server-diagnostics-20161019-1309.zip

This isn't only you, I have noticed this also after the update to 6.3. I think this may be more common than we surmise, but the thing is, most users don't look at the VM log's, and this hasn't specifically caused any stability issues that I'm aware of. In comparison, I updated 4 VM's to the newest i440fx-2.7, and only the one VM shows these errors. So with that in mind, I'm uncertain as to the culprit here. In Windows I have an uninstalled device listed as "HID Button over Interrupt Driver" that I don't have a driver for. This wasn't listed previously that I'm aware of, so I think this is also in line with the update to 6.3. I haven't looked into this yet, just thought I'd mention it. Mine looks like this, the error is logged very shortly after reaching the desktop in Windows: 2016-10-12 21:33:57.936+0000: starting up libvirt version: 1.3.1, qemu version: 2.7.0, hostname: Server LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name Main -S -machine pc-i440fx-2.7,accel=kvm,usb=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/ad11552f-014f-6edd-a63c-a523ae4afdbc_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 12288 -realtime mlock=on -smp 4,sockets=1,cores=2,threads=2 -uuid ad11552f-014f-6edd-a63c-a523ae4afdbc -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Main/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive file=/mnt/cache/VMs/Main/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:c2:26:c8,bus=pci.0,addr=0x2 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-Main/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device vfio-pci,host=04:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device vfio-pci,host=00:1b.0,id=hostdev2,bus=pci.0,addr=0x8 -device vfio-pci,host=05:00.0,id=hostdev3,bus=pci.0,addr=0x9 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xa -msg timestamp=on Domain id=3 is tainted: high-privileges Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/2 (label charserial0) 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've attached my VM QEMU log for comparison, I had to rename it ".txt" for it to upload here. Main.txt

Ok, I'd start with the USB to ethernet adapter as the log entries start right after that device is listed.

The warning is pointing to a USB controller, specifically this one: 09:00.0 USB controller [0c03]: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller [1912:0014] (rev 03) Subsystem: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller [1912:0014] Kernel driver in use: xhci_hcd Do you have any options you can change that relate to this controller, such as XHCI mode, or settings (there's typically 3 of them for MB based USB cards?). I looked at your syslog, what do you have plugged into this controller? It doesn't look as if you're assigning it to your VM, do you have a USB/ethernet plugged into this? Either way I'd remove any devices from this controller, and see if the message disappears. It looks as if the warning starts 2 minutes after booting up, so it should be pretty easy to know if you've removed or changed a setting that removes this message from your syslog.

Thanks for taking another look Rob, and as always the continued support from LT/Jon. Well it may be a little early to drink to it (I can and will drink to other random things however), I think this issue is resolved in the newest kernel/QEMU!! I have not seen any indication of this fragmentation within my logs lately, it has been rather peaceful (and somewhat boring to be honest). Anyhow, I still don't know why only I have had these issues, but if they are truly gone I could give 2 shits as to the answer to that question! So I'll give it some more time/usage, and if it doesn't come back up again I'll then update this as solved. No idea what commits in the most recent kernel may have addressed this, but it's looking like a winner so far.

Sounds like this is progressing somewhat, so that's good to hear. I'd recommend trying the 6.3RC as you may have better luck with newer kernel/qemu. This would also give you the 2.7 i440fx, however I doubt that within itself will resolve much in regards to your situation.

Have you looked at the log for the VM, or any Windows sys logs to see if there's any indication within them that may be helpful?

Have you set the power settings in Windows to high performance, and any related settings in advanced power settings (I like to ensure selective USB, sleep, and some others are also disabled)? Normally speaking a VM sleeps from either: a) it actually is set to sleep b)over committing of ram, not enough for the host (I've also seen this force stop the VM).

You're going to have much more success overall with Windows 10 vs Windows 7 especially when passing through devices. Since you say that Windows 7 gives you a screen output, I tend to think that your 7850 supports UEFI boot (some cards do not). I'd recommend sticking with Windows 10 create a new Windows VM template, and toggle the advanced view button in the top right corner. You can then set the BIOS to SeaBIOS instead of OVMF/UEFI. You can also set the machine type under advanced view, recommend leaving that at the default which should be i440FX-2.7 If you wanted to stick with OVMF, you can also supply the rom to the GPU in order to possibly alleviate the black screen, however what I suggested above is just easier to do. Update with your success or failure, if failure I'd try the rom option which has details in both the Wiki and also in posts here in the forum.

For multiple vdisk VM's, the boot order could get set incorrectly. If you go into the edit XML option you will see a boot order=1 or something of that nature, try moving that to the correct system vdisk if it is incorrect. As for restart/freeze issues, I want to make sure within the VM that you deselected the "Fast startup" option? This is in the power settings somewhere (I think if you click the "What does the power button do"), and you want to disable this. This can cause device initialization issues for VM's with devices assigned. Setting this and other useful recommendations/instructions are in the Wiki. As for data on the vdisk, the data is still certainly there so you could assign it to most VM's and retrieve the data. Certainly preferred to get it working with this VM, but you can access the files with something as simple as a "live" Linux install or something of the sort if you had to. I would even guess that Unassigned Devices could likely mount it and share access to it, but never tried so can't say for certain.

Nope, but I am now. Changes from my "good" setup: remove one GT720, remove USB3 card (in slot that double card blocks). Install GTX950, remove USB 3 card from XML, switch to i440fx-2.7 (newest now included in 6.3), assign MB USB controller to VM. Start VM, run DDU to clean out any old drivers, install fresh drivers, set MSI interrupt to on. Now we wait... Give me a few days and I'll let you know how it goes. I grabbed a clean diagnostics from my 3 days on 6.3 RC1 prior to shutdown. If it does reappear (I would like to be confident, but my previous experiences make that difficult), maybe in comparison something will be more obvious. Also (previously done testing) while ruling things out and testing my hardware, I thought maybe some specific CPU PCIe lanes/traces were damaged, so I moved the GTX950 to the next PCIe 16x (length, not wired) slot that other VM's use without issue. These log files entries were the same as before following the VM/GPU, the other VM now using the primary PCIe slot worked as well as it always did prior.

You are correct in that all of your components are suspect of issue. I know you already replaced the board, but perhaps "damage has been done" or perhaps the board wasn't really to blame at all. In order of least to most costly tests you can perform: 1 - Try reducing the amount of total system memory you have installed and if the issues persist, switch the chips that you removed for the ones that you left in and try again. 2 - Try replacing the power supply and then repeat test 1 if issues persist 3 - Replace all memory on the system with new memory 4 - Try a different GPU (GTX 960, 970, 980, or 1080 have all been tested by us here at LT) If this was an issue in software, I think it would be more widespread and reported. The fact that we can't recreate it and you seem to be isolated in this situation points very heavily at this still being a hardware related issue. Memtest is a great tool, but is not the end-all be-all for diagnosing memory issues. In fact, there are no tools that can fully diagnose each hardware component in a computer (certainly not any available to the consumer market). So while memtest can reveal glaring problems like a chip that has been physically damaged, if there are other issues related to the memory controller or the data paths in between, these may not be as easily detected. Thanks John, but unfortunately I've been through all of that and here I am... Let me go through this line by line. 1 - Try reducing the amount of total system memory you have installed and if the issues persist, switch the chips that you removed for the ones that you left in and try again. Not exactly what you asked, but I changed out memory completely (even though no errors), went from 32GB (4X8GB, Crucial) to 64GB (4X16GB G. Skill) with the exact same issue. Memtest 24 hours, 9+ passes successful. 2 - Try replacing the power supply and then repeat test 1 if issues persist Did that, replaced a perfectly good Corsair TX650 with a (fancy!) HX850i 3 - Replace all memory on the system with new memory See #1 4 - Try a different GPU (GTX 960, 970, 980, or 1080 have all been tested by us here at LT) I kind of did, well I had a R260X, bought a new (second-hand) EVGA GTX950 with the same results. Used my 3rd GT720, and the issue is resolved. Adding one 5 - I thought maybe my CPU was damaged when my motherboard died (RIP), so I borrowed a 5920k, and received the exact same issues on the exact same CPU cores/VM's with it installed. So knowing all of that, everything is either new or tested against a new product, and still I see these messages. I've looked extensively at memory mapping, various kernel parameters (related to memory, page file, MTRR, etc.) with nothing making any change. I'm honestly happier than a pig in shit that removing these GPU's from my system has solved this issue, however something still isn't right. I understand what you're saying, I'm just stumped, completely.. I'm normally pretty good with this kind of stuff, this one is just plain strange! I also completely wiped my flash drive and started fresh (basically everything), just in case, and no difference. I'm pretty confident if you had my GPU you'd test it and also tell me it is fine, no issues.... However with them removed, issue gone. Edit: IDK, does this sound similar (albeit quite old) https://groups.google.com/forum/#!topic/linux.kernel/scXkSlZ5EMQ

Need to update this, and ask for continued support.. Yes I know I'm the only one seeing this. Reminder that Memtest 24+ hours with 0 errors, no actual instability issues. This also (somewhat) makes sense I only starting seeing these when they replaced my GPU with a newer refurbished one (different model, R260X). This is what I know now, this is only evident (for me with the components I have here) when I pass through either my replacement R260X, or GTX950, so basically "gaming able" GPU's. This error "alloc_bts_buffer" from extensive Googling details a memory fragmentation error, which in the past has been requested to stop "spamming the logs". If I remove either of those cards, and assign a GT720 to this VM, the issue is completely gone, 8+ days on 6.2 final (there have been frequent updates, causing me to reboot). I removed the R260X, tried my new GTX950 (same issue), I assigned a GT720 and the problem is completely non existent (it's almost too peaceful in my syslog!) . I'm currently running the following: 3 GT 720's (Win 8.1 MCE, Win 10 X2), 1 GT 710 (Librelec), and one headless, all working as expected. So, if I keep it just like this, this is likely solved... However if I add back in either GPU, I'm pretty confident within 24 hours these messages will appear again, always following the VM that the card is assigned to. I've attached a clean log from my 8+ days using the 720's and 710 prior to upgrading to 6.3 RC1. Other logs to compare to above, I don't see anything obviously different between the two to help diagnose this. server-diagnostics-20161009-1000_Clean_8_Days_GT720s.zip