henriquelb

Today's log Same behavior, after a while the whole server seems frozen, VMs, WebUI, Terminal, everything. FCPsyslog_tail.txt inefavel-diagnostics-20170524-1600.zip

Since I updated to 6.3.4 my server get unresponsive after a few(3-15) hours, regardless of whether it use a VM or docker. syslog tail and diagnostics attached. Some one can bring a light? FCPsyslog_tail.txt inefavel-diagnostics-20170522-1929.zip

I need some help, got stuck in this step after reboot:

It's cristal clear, my setup have no love for 6.3.0/1/2 I tested every Windows VM combination, great performance under 6.2.4, but when I update it get hit hard! If I just replace the bzimage file from 6.2.4, all great again.

XML - 6.2.4 <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows 10</name> <uuid>8dc6acd0-fa75-7995-ccde-29b0107fe2a3</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>46137344</memory> <currentMemory unit='KiB'>46137344</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> <vcpupin vcpu='6' cpuset='12'/> <vcpupin vcpu='7' cpuset='13'/> <vcpupin vcpu='8' cpuset='14'/> <vcpupin vcpu='9' cpuset='15'/> <vcpupin vcpu='10' cpuset='16'/> <vcpupin vcpu='11' cpuset='17'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-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/8dc6acd0-fa75-7995-ccde-29b0107fe2a3_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='6' threads='2'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-FCCT256M4SSD1_00000000130203623002'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:28:d9:fb'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc07d'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04d9'/> <product id='0xa096'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-machine'/> <qemu:arg value='max-ram-below-4g=1G'/> </qemu:commandline> </domain> On the 6.3.0/1 the only change is <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> to <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type> There is a way to have the 6.3.0-rc1 version? I want to test a different kernel version, perhaps my hardware don't run smooth with newer version...

Sorry, but in this case is irrelevant. The main point is to figure out what is incompatible, hardware or my settings. Again, I had performance issues upgrading from 6.2.4 to 6.3.0 or 3.2.1 so I wanted to test a new config from scratch. It's kind obviously that my performance tests were made when there aren't any parity check or parity rebuild running. A lot of stuffs in the 6.3.0 version got updated. There is a way to download the 6.3.0-rc1, rc2 etc? So I can try narrow down what is causing it?

Fresh formatted drives. If you did that your system will be rebuilding parity right now.. And that WILL slow it down... Is that what is happening maybe ? Also.. There is no reason I can imagine why formatting your parity drives will have any effect... They do not even require formatting... Why are you trying to deviate the center point? That's really weird. I just made a fresh install to test. I thought that the performance issue could be something with my settings on 6.2.4 being wrong in the 6.3.1, that's why I tested with a fresh install. However on both, fresh installed 6.3.1 or upgraded from 6.2.4 the performance took a giant hit.

Fresh formatted drives.

We need to get some more information from you to help diagnose. Please explain what you mean by "horrible performance". how are you testing / validating this? What was the experience in 6.2.4 vs. 6.3.0/6.3.1? By "horrible performance" I mean: 6.2.4 - Able to use Adobe Premiere, After Effects, Photoshop and Google Chrome with several tabs. 6.3.0/1 - Barely able to use Google Chrome with 5 tabs. Premiere takes 10x longer to open. There is any diagnostic software or something I could do to help? -------------- I made a clean 6.3.1 install, clean parity, 3 ssd as cache (diagnostics attached). Performance still bad as before. So far there aren't any new hardware limitation? My hardware: Evga SR-2 X58 - NF200 bridge chip - Intel 5520 chipset 2x Xeon X5675 Quadro NVS 295 + 2x GTX 960 4gb inefavel-diagnostics-20170209-2227.zip

VM's performance still horrible for me with 6.3.1. Downgrading to 6.2.4. Diagnostics attached, however nothing out of normal. Anyone running X58 motherboards? All normal with this release? EDIT: Could be my drives setup? I don't have cache disk and for VM drive I passthrough one SSD for each VM. EDIT 2: Even when it freezes the CPU load is normal, perhaps the issue is with passthrough GPU? There is any way to test it? inefavel-diagnostics-20170209-0937.zip

Thanks Jonp! As far I looked up, I do believe that this unstable TSC happen due to my old hardware. Just downgraded to 6.2.4, everything runs smooth now. I'll wait for the next release to update, hope my hardware likes it.

I updated from 6.2.4 to 6.3.0 yesterday. I usually use just 2 VM's, after update it's really bad to use, watch a youtube video is practically impossible. When I look my logs I don't see nothing out of normal. inefavel-diagnostics-20170206-1353.zip

I got several lines of the same error: Mar 21 00:16:55 Inefavel kernel: pcieport 0000:00:07.0: AER: Multiple Uncorrected (Non-Fatal) error received: id=0000 Mar 21 00:16:55 Inefavel kernel: pcieport 0000:00:07.0: can't find device of ID0000 00:07.0 is a graphics card GTX 960, however I have another GTX 960 exactly same model, running in a exactly the same VM configuration giving me no errors. As far I'm aware, I never saw it in past releases. syslog.zip

Since I updated I'm getting some crashes(server became unusable via terminal or webGUI and all VMs are stopped, restart is needed). However until now I wasn't able to see any thing different in the log file. I left the log popup window running for a while until I got a crash, here is what happened: Edit: on VM's log I got "2016-03-18 14:23:06.913+0000: shutting down" Edit2: Log from another "crash":

I was wondering what is the best config for using 3 ssds on 6.2. My machine is splitted in two workstations, so I was using on version 6.18: Parity: 5tb hd Drive 1: 5tb hd (general storage) Drive 2: 256gb ssd (workstation 1 system only) Drive 3: 256gb ssd (workstation 2 system only) Cache: 256gb ssd (to speed up overall transfers) Now on the 6.2 appears that system(OS) is cache only by default. So, to have the most efficient use of those ssds, I should assign all 3 to cache? I bought a license about 2 weeks ago, so I'm very noob in it.