December 16, 20178 yr 1 hour ago, zin105 said: Ehm my log is absolutely filled with call traces since installing the latest RC. When I google it seems to have something to do with NICs and offloading. It actually continues all the way to the current time, but doens't show that in the diagnostics for some reason. htpc-diagnostics-20171216-1620.zip I have the same problem!!! unraid-diagnostics-20171216-1944.zip
December 16, 20178 yr 1 hour ago, zin105 said: Ehm my log is absolutely filled with call traces since installing the latest RC. When I google it seems to have something to do with NICs and offloading. It actually continues all the way to the current time, but doens't show that in the diagnostics for some reason. htpc-diagnostics-20171216-1620.zip Can you test again by starting your system in safemode.
December 16, 20178 yr 16 minutes ago, zin105 said: Update: I pulled the dual port NIC and used onboard only, with bonding obviously disabled. I am using both bonding, bridging and VLANs, and don't have this issue. Your are using a different ethernet driver (e1000e), perhaps this conflicts with the UDP fragmentation offload patch?
December 16, 20178 yr I localized my broblem! after i start privoxy docker container begans madness in syslog I watched a little more and noticed that nothing happens if the docker containers are not running .... rolled back to 15 Dec 16 20:27:16 unRaid kernel: do_softirq+0x4a/0x57 Dec 16 20:27:16 unRaid kernel: __local_bh_enable_ip+0x4c/0x65 Dec 16 20:27:16 unRaid kernel: ip_finish_output2+0x275/0x2ab Dec 16 20:27:16 unRaid kernel: ip_finish_output+0x17a/0x18a Dec 16 20:27:16 unRaid kernel: ? ip_finish_output+0x17a/0x18a Dec 16 20:27:16 unRaid kernel: ip_output+0xc0/0xcd Dec 16 20:27:16 unRaid kernel: ip_local_out+0x30/0x37 unraid-diagnostics-20171216-2027.zip Edited December 16, 20178 yr by vanes
December 16, 20178 yr 55 minutes ago, zin105 said: Update: I pulled the dual port NIC and used onboard only, with bonding obviously disabled. Still the same problem. I'm now in a "pick your poison" position and I've decided to downgrade to RC15..... Perhaps there is a conflict with the iftop package. Dec 16 11:31:52 HTPC root: Processing Packages... Dec 16 11:31:52 HTPC kernel: br0: port 1(bond0) entered disabled state Dec 16 11:31:52 HTPC nerdpack: Installing iftop-1.0pre2 package... Try without this package.
December 16, 20178 yr FYI, Upgraded from RC 13 to 16B on my Ryzen build and all has went well. Running a Windows 10 VM using my MSI RX 580 on pass though and all has worked well for the past 2 days 5 hours. No problem stopping and restarting plex and Windows 10 VM. Big Edited December 18, 20178 yr by Big Wig
December 16, 20178 yr 4 hours ago, vanes said: I localized my broblem! after i start privoxy docker container begans madness in syslog I watched a little more and noticed that nothing happens if the docker containers are not running .... rolled back to 15 I do not know what helped but now everything is fine! I restored the backup RC15, then i swicthed Use SSL/TLS: to "no" and update again! Now everything is fine Edited December 16, 20178 yr by vanes
December 17, 20178 yr Same issues as rc15 with call traces during VM startup. No custom XML. VM seem s to work fine though. servernas-diagnostics-20171216-2229.zip
December 17, 20178 yr Every now and again a VM would hang which would hang the webGui as well, consider detaching the front-end from the back-end. As to the VM hang, it seems destroying it did not help this time. A few times the webGui displayed "No VMs installed" which changed to a semi-loaded/hanged page after a couple of refreshes. Quote virsh # list Id Name State ---------------------------------------------------- 1 CentOS running virsh # reboot 1 error: Failed to reboot domain 1 error: Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainGetBlockInfo) virsh # destroy 1 error: Failed to destroy domain 1 error: Failed to terminate process 9607 with SIGKILL: Device or resource busy PS: It was not possible to terminated the QEMU process so the unRAID server had to be rebooted which indicated an unclean shutdown. Edited December 17, 20178 yr by realies
December 17, 20178 yr Updated my ryzen system from rc9 to rc16 and it seems to have reintroduced a problem I had prior to rc9 where the the system would be come totally unresponsive after running for a couple hrs and I have to power cycle the system to restore connectivity. Cpu - ryzen 1600 mb - asrock ab350m pro4
December 17, 20178 yr installed 16b. my first time with 6.4 got system call. - I see the Array Starting message continuously . accessing via ssh I see the disks mounted though - when I choose to download diagnostics, it says downloading ... without doing anything. - when I choose to downgrade, I get the script window but its empty doing nothing. made a copy of the syslog diagnostic is before the upgrade. in 6.4 10b same thing. system call 4:51:39 Tower avahi-daemon[16033]: Service "Tower" (/services/sftp-ssh.service) successfully established. Dec 17 14:51:39 Tower avahi-daemon[16033]: Service "Tower-AFP" (/services/afp.service) successfully established. Dec 17 14:51:39 Tower emhttpd: Starting Internet super-server daemon: /usr/sbin/inetd Dec 17 14:51:39 Tower tips.and.tweaks: Tweaks Applied Dec 17 14:51:39 Tower emhttpd: Mounting disks... Dec 17 14:51:39 Tower emhttpd: shcmd (36): /sbin/btrfs device scan Dec 17 14:51:40 Tower root: Scanning for Btrfs filesystems Dec 17 14:51:40 Tower emhttpd: shcmd (37): mkdir -p /mnt/disk1 Dec 17 14:51:40 Tower emhttpd: shcmd (38): mount -t xfs -o noatime,nodiratime /dev/md1 /mnt/disk1 Dec 17 14:51:40 Tower kernel: SGI XFS with ACLs, security attributes, no debug enabled Dec 17 14:51:40 Tower kernel: XFS (md1): Mounting V5 Filesystem Dec 17 14:51:40 Tower kernel: XFS (md1): Ending clean mount Dec 17 14:51:40 Tower emhttpd: shcmd (39): xfs_growfs /mnt/disk1 Dec 17 14:51:40 Tower root: meta-data=/dev/md1 isize=512 agcount=4, agsize=244188659 blks Dec 17 14:51:40 Tower root: = sectsz=512 attr=2, projid32bit=1 Dec 17 14:51:40 Tower root: = crc=1 finobt=1 spinodes=0 rmapbt=0 Dec 17 14:51:40 Tower root: = reflink=0 Dec 17 14:51:40 Tower root: data = bsize=4096 blocks=976754633, imaxpct=5 Dec 17 14:51:40 Tower root: = sunit=0 swidth=0 blks Dec 17 14:51:40 Tower root: naming =version 2 bsize=4096 ascii-ci=0 ftype=1 Dec 17 14:51:40 Tower root: log =internal bsize=4096 blocks=476930, version=2 Dec 17 14:51:40 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Dec 17 14:51:40 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Dec 17 14:51:40 Tower emhttpd: shcmd (40): mkdir -p /mnt/disk2 Dec 17 14:51:40 Tower emhttpd: shcmd (41): mount -t xfs -o noatime,nodiratime /dev/md2 /mnt/disk2 Dec 17 14:51:40 Tower kernel: XFS (md2): Mounting V5 Filesystem Dec 17 14:51:40 Tower kernel: XFS (md2): Ending clean mount Dec 17 14:51:40 Tower emhttpd: shcmd (42): xfs_growfs /mnt/disk2 Dec 17 14:51:40 Tower root: meta-data=/dev/md2 isize=512 agcount=4, agsize=122094660 blks Dec 17 14:51:40 Tower root: = sectsz=512 attr=2, projid32bit=1 Dec 17 14:51:40 Tower root: = crc=1 finobt=1 spinodes=0 rmapbt=0 Dec 17 14:51:40 Tower root: = reflink=0 Dec 17 14:51:40 Tower root: data = bsize=4096 blocks=488378638, imaxpct=5 Dec 17 14:51:40 Tower root: = sunit=0 swidth=0 blks Dec 17 14:51:40 Tower root: naming =version 2 bsize=4096 ascii-ci=0 ftype=1 Dec 17 14:51:40 Tower root: log =internal bsize=4096 blocks=238466, version=2 Dec 17 14:51:40 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Dec 17 14:51:40 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Dec 17 14:51:40 Tower emhttpd: shcmd (43): mkdir -p /mnt/cache Dec 17 14:51:40 Tower emhttpd: shcmd (44): mount -t btrfs -o noatime,nodiratime /dev/sdb1 /mnt/cache Dec 17 14:51:40 Tower kernel: BTRFS info (device sdb1): disk space caching is enabled Dec 17 14:51:40 Tower kernel: BTRFS info (device sdb1): has skinny extents Dec 17 14:51:40 Tower kernel: BTRFS info (device sdb1): bdev /dev/sdb1 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Dec 17 14:51:40 Tower kernel: BTRFS info (device sdb1): detected SSD devices, enabling SSD mode Dec 17 14:51:40 Tower emhttpd: shcmd (45): sync Dec 17 14:51:40 Tower emhttpd: shcmd (46): mkdir /mnt/user0 Dec 17 14:51:40 Tower emhttpd: shcmd (47): /usr/local/sbin/shfs /mnt/user0 -disks 6 -o noatime,big_writes,allow_other |& logger Dec 17 14:51:40 Tower emhttpd: shcmd (48): mkdir /mnt/user Dec 17 14:51:40 Tower emhttpd: shcmd (49): /usr/local/sbin/shfs /mnt/user -disks 7 2048000000 -o noatime,big_writes,allow_other -o remember=0 |& logger Dec 17 14:51:40 Tower emhttpd: shcmd (51): /usr/local/sbin/update_cron Dec 17 14:51:41 Tower root: Starting CA Auto Turbo Mode Dec 17 14:51:41 Tower root: Creating custom tabs Dec 17 14:51:41 Tower kernel: mdcmd (39): set md_write_method 1 Dec 17 14:51:41 Tower kernel: Dec 17 14:51:41 Tower cache_dirs: ============================================== Dec 17 14:51:41 Tower cache_dirs: Starting cache_dirs: Dec 17 14:51:41 Tower cache_dirs: Arguments=-u -i appdata Dec 17 14:51:41 Tower cache_dirs: Cache Pressure=10 Dec 17 14:51:41 Tower cache_dirs: Max Scan Secs=10, Min Scan Secs=1 Dec 17 14:51:41 Tower cache_dirs: Scan Type=adaptive Dec 17 14:51:41 Tower cache_dirs: Max Scan Depth=none Dec 17 14:51:41 Tower cache_dirs: Use Command='find -noleaf' Dec 17 14:51:41 Tower cache_dirs: Version=2.1.1 Dec 17 14:51:41 Tower cache_dirs: ---------- Caching Directories --------------- Dec 17 14:51:41 Tower cache_dirs: appdata Dec 17 14:51:41 Tower cache_dirs: ---------------------------------------------- Dec 17 14:51:41 Tower cache_dirs: cache_dirs process ID 16509 started Dec 17 14:51:41 Tower root: Fix Common Problems Version 2017.12.11a Dec 17 14:51:43 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at (null) Dec 17 14:51:43 Tower kernel: IP: isci_task_abort_task+0x1c/0x35d [isci] Dec 17 14:51:43 Tower kernel: PGD 835b97067 Dec 17 14:51:43 Tower kernel: P4D 835b97067 Dec 17 14:51:43 Tower kernel: PUD 8358d2067 Dec 17 14:51:43 Tower kernel: PMD 0 Dec 17 14:51:43 Tower kernel: Dec 17 14:51:43 Tower kernel: Oops: 0000 [#1] PREEMPT SMP Dec 17 14:51:43 Tower kernel: Modules linked in: xfs md_mod nct7904 bonding igb ptp pps_core i2c_algo_bit i2c_core mxm_wmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate isci intel_uncore libsas intel_rapl_perf ahci usblp scsi_transport_sas libahci wmi button [last unloaded: pps_core] Dec 17 14:51:43 Tower kernel: CPU: 0 PID: 1420 Comm: kworker/u64:1 Not tainted 4.13.10-unRAID #1 Dec 17 14:51:43 Tower kernel: Hardware name: Supermicro X9DAi/X9DAi, BIOS 3.2 05/09/2015 Dec 17 14:51:43 Tower kernel: Workqueue: scsi_tmf_1 scmd_eh_abort_handler Dec 17 14:51:43 Tower kernel: task: ffff88105adbc4c0 task.stack: ffffc90008250000 Dec 17 14:51:43 Tower kernel: RIP: 0010:isci_task_abort_task+0x1c/0x35d [isci] Dec 17 14:51:43 Tower kernel: RSP: 0018:ffffc90008253c98 EFLAGS: 00010292 Dec 17 14:51:43 Tower kernel: RAX: ffffffffa01c12fc RBX: ffff88085a2c05a8 RCX: 0000000000000000 Dec 17 14:51:43 Tower kernel: RDX: ffff88085f410420 RSI: 0000000000000800 RDI: 0000000000000000 Dec 17 14:51:43 Tower kernel: RBP: ffffc90008253e28 R08: 000000154d3b0000 R09: 0000000000000048 Dec 17 14:51:43 Tower kernel: R10: ffffffff81803dd0 R11: 071c71c71c71c71c R12: 0000000000000000 Dec 17 14:51:43 Tower kernel: R13: ffff88085ba64000 R14: 0000000000000000 R15: 0000000000000008 Dec 17 14:51:43 Tower kernel: FS: 0000000000000000(0000) GS:ffff88085fa00000(0000) knlGS:0000000000000000 Dec 17 14:51:43 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 17 14:51:43 Tower kernel: CR2: 0000000000000000 CR3: 0000000839a12000 CR4: 00000000000406f0 Dec 17 14:51:43 Tower kernel: Call Trace: Dec 17 14:51:43 Tower kernel: ? load_balance+0x13f/0x774 Dec 17 14:51:43 Tower kernel: ? native_sched_clock+0x54/0x79 Dec 17 14:51:43 Tower kernel: ? __accumulate_pelt_segments+0x21/0x2f Dec 17 14:51:43 Tower kernel: ? __accumulate_pelt_segments+0x21/0x2f Dec 17 14:51:43 Tower kernel: ? __update_load_avg_cfs_rq.isra.2+0xaa/0x12d Dec 17 14:51:43 Tower kernel: ? dequeue_entity+0x4d2/0x4ec Dec 17 14:51:43 Tower kernel: ? put_prev_entity+0x26/0x2f8 Dec 17 14:51:43 Tower kernel: sas_eh_abort_handler+0x2e/0x49 [libsas] Dec 17 14:51:43 Tower kernel: scmd_eh_abort_handler+0x3a/0x93 Dec 17 14:51:43 Tower kernel: process_one_work+0x147/0x222 Dec 17 14:51:43 Tower kernel: ? rescuer_thread+0x258/0x258 Dec 17 14:51:43 Tower kernel: worker_thread+0x1d3/0x29e Dec 17 14:51:43 Tower kernel: ? rescuer_thread+0x258/0x258 Dec 17 14:51:43 Tower kernel: kthread+0x11c/0x124 Dec 17 14:51:43 Tower kernel: ? kthread_create_on_node+0x3a/0x3a Dec 17 14:51:43 Tower kernel: ret_from_fork+0x25/0x30 Dec 17 14:51:43 Tower kernel: Code: 89 e5 5d c3 55 b8 05 00 00 00 48 89 e5 5d c3 55 48 89 e5 41 57 41 56 41 55 41 54 49 89 fc 53 4d 8d 7c 24 08 48 81 ec 68 01 00 00 <48> 8b 07 c7 85 80 fe ff ff 00 00 00 00 c7 85 88 fe ff ff 00 00 Dec 17 14:51:43 Tower kernel: RIP: isci_task_abort_task+0x1c/0x35d [isci] RSP: ffffc90008253c98 Dec 17 14:51:43 Tower kernel: CR2: 0000000000000000 Dec 17 14:51:43 Tower kernel: ---[ end trace 5f59ab48db64fca8 ]--- system log 17Dec crash.txt tower-diagnostics-20171217-1213.zip Edited December 17, 20178 yr by dadarara
December 17, 20178 yr Just thought I'd chime in with my upgrade results. I upgraded last night directly from 6.3.5 with no issue. I specifically upgraded because I wanted 6.4's ability to bond dockers to VLAN-tagged sub-interfaces and that's working very well also. I hit a bit of a snag when I discovered that the host can't communicate directly with containers bonded to a different bridging interface, which results in every host on the network being able to reach the docker container except unRAID itself. Based on a post from bonienl in another thread it seems that that's a conscious design decision by the docker team, so in the end I just wound up doing a port forward between subnets in my router and moving on. 6.4 is looking good, can't wait for final release! -A
December 17, 20178 yr 20 minutes ago, vanes said: I yesterday also collided with call traces, I can share observations! 16 hours everything was fine, but recently today, after the evening torrenting, i get a full log of call-traces. Call-traces start right after the torrent starts! Stopping transmission container stops call-traces. Disabling of the bond did not help. In the end, I switched the transmission docker container to the host mode and now no call traces while torrenting! in this log i start torrenting in host mode with no call-traces then switch container to bridge mode and recieve full log of call-traces..... sorry for my google-translator english =) unraid-diagnostics-20171217-1934.zip
December 17, 20178 yr I have an issue for which I don't know whether the source is unRAID, UAD or preclear (or another plugin), but at least on the symptom side unRAID could do something, so I post it here. When I opened a browser session to the web GUI for upgrading from rc14 to , I got a page with only the titles, but no content. Next I logged into using ssh and quickly found out that the RAMdisk in which unRAID places its root file system was completely filled up. I tried to launch diagnostics from the command line and while it completed, it created an empty file, not unexpected given that there was no disk space available. Below is the output of some commands root@Tower:~# mount proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) tmpfs on /dev/shm type tmpfs (rw) tmpfs on /var/log type tmpfs (rw,size=128m,mode=0755) /dev/sdb1 on /boot type vfat (rw,noatime,nodiratime,umask=0,shortname=mixed) /boot/bzmodules on /lib/modules type squashfs (ro) /boot/bzfirmware on /lib/firmware type squashfs (ro) /mnt on /mnt type none (rw,bind) root@Tower:~# tail -f /var/log/syslog Dec 16 17:41:18 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sda Dec 16 17:41:18 Tower emhttpd: device /dev/sda problem getting size Dec 16 17:41:19 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sda Dec 16 17:41:19 Tower emhttpd: device /dev/sda problem getting size Dec 16 17:41:20 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sda Dec 16 17:41:20 Tower emhttpd: device /dev/sda problem getting size root@Tower:/var/log# df -H Filesystem Size Used Avail Use% Mounted on rootfs 17G 17G 0 100% / tmpfs 34M 312k 34M 1% /run devtmpfs 17G 0 17G 0% /dev tmpfs 17G 38M 17G 1% /dev/shm cgroup_root 8.4M 0 8.4M 0% /sys/fs/cgroup tmpfs 135M 85M 50M 64% /var/log /dev/sdb1 16G 379M 16G 3% /boot /dev/loop0 7.1M 7.1M 0 100% /lib/modules /dev/loop1 4.6M 4.6M 0 100% /lib/firmware /dev/md1 8.0T 7.3T 778G 91% /mnt/disk1 /dev/mapper/md2 8.0T 7.5T 588G 93% /mnt/disk2 /dev/mapper/md3 8.0T 4.3T 3.8T 53% /mnt/disk3 /dev/mapper/md4 8.0T 6.6T 1.5T 82% /mnt/disk4 /dev/mapper/md5 8.0T 442G 7.6T 6% /mnt/disk5 /dev/mapper/md6 8.0T 1.3T 6.8T 17% /mnt/disk6 /dev/mapper/md7 8.0T 5.3T 2.8T 66% /mnt/disk7 shfs 72T 40T 33T 56% /mnt/user /dev/loop2 22G 21M 20G 1% /var/lib/docker /dev/loop3 1.1G 18M 949M 2% /etc/libvirt /dev/sdj1 257G 48G 209G 19% /mnt/disks/ssd256c /dev/mapper/md8 8.0T 1.8T 6.3T 23% /mnt/disk8 /dev/mapper/md9 8.0T 5.9T 2.2T 74% /mnt/disk9 In other words it seems that log messages complaining about /dev/sda are using up disk space. I did a reboot, then upgraded from rc14 to rc16, but the issue with /dev/sda persisted. As far as I know, unRAID assigns sda to the Kingston MobileLite G3 SD Card Reader itself, while sdb is the SDCard with the software. I don't know since when I have these logs, I had rc14 running longer than any release before, so others I maybe just rebooted early enough. I only know that last time I looked at syslog a few releases back, this didn't occur. Questions: 1. do others with a MobileLite based boot device also get their log filled with those warnings? 2. what has changed in unRAID or plugins? 3. Would it be possible to add a protection (log rotation) in order to avoid such lockups
December 17, 20178 yr 6 minutes ago, tstor said: log messages complaining about /dev/sda are using up disk space. They would be logged in /var/log which is only 64% full 8 minutes ago, tstor said: tail -f /var/log/syslog What about cat /var/log/syslog | grep bread 9 minutes ago, tstor said: what has changed in unRAID or plugins? Lots, but if you started unRaid on 6.1+ and only installed via Community Applications, you won't have any problems 9 minutes ago, tstor said: Would it be possible to add a protection (log rotation) in order to avoid such lockups Already there 10 minutes ago, tstor said: rootfs 17G 17G 0 100% / Most obvious answer though not necessarily correct is that you've got some docker application storing downloads / whatnot into RAM, or are creating the docker.img in RAM
December 17, 20178 yr 14 minutes ago, tstor said: Kingston MobileLite G3 SD Card Reader itself, while sdb is the SDCard with the software. These messages would probably only appear while the array is stopped, and is by itself not a real big issue.
December 17, 20178 yr 3 hours ago, Squid said: They would be logged in /var/log which is only 64% full Thanks for pointing it out, I overlooked that, but it confirms my other thought: I did an estimate of number of bytes written to syslog per second for the /dev/sda issue and came to the conclusion that this alone could never have filled up 16 GB since the last boot. Regarding your other points: I cannot grep for "bread" in the old syslog because I have rebooted for the upgrade since then. Would you mind to elaborate what you're suspecting? I have only started with unRAID after dual parity and encryption became available, in other words with some earlier release candidate of 6.4 and I currently only use it for file storage. There are no dockers or VMs. At least when the problem occurred on rc14 , the log messages for /dev/sda happened during a time when the array was started. When I did check with rc16 however the array was stopped because I did not want to start the array before having an idea of what could have happened. When the lockup happened, two things were going on in parallel: preclear (started from web GUI) was clearing three 12 TB drives. The fastest of the three had finished preclear, the other two not. I have seen other forum entries describing issues with preclear, so this could be a trace to follow. another computer copied data to an array drive using rsync and reconstruct writes. This was still ongoing and the the source computer did not signal any errors until I cancelled the transfer in order to upgrade/reboot unRAID. I had started all three preclears at the same time and when I looked at the progress a day later I could see that they were a only a few minutes apart. I think it is quite unlikely although still possible that a completely unrelated issue would fill up rootfs exactly between the first drive finishing and the next following.
December 17, 20178 yr Just had KVM hang on me, here is the diagnostics logs and XMLs from my VMs. <domain type='kvm' id='4'> <name>Ubuntu Server</name> <uuid>37d13441-f940-0f78-bf97-6f9a8e092716</uuid> <description>Ubuntu Server</description> <metadata> <vmtemplate xmlns="unraid" name="Ubuntu" icon="ubuntu.png" os="ubuntu"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='10'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.10'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='2'/> </cpu> <clock offset='utc'> <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='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Ubuntu Server/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/ubuntu-17.10-server-amd64.iso'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:0c:f9:ef'/> <source bridge='br0'/> <target dev='vnet3'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/3'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/3'> <source path='/dev/pts/3'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-4-Ubuntu Server/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5901' autoport='yes' websocket='5701' 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' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> <domain type='kvm' id='1'> <name>Windows 10 Nvidia Gaming VM</name> <uuid>10d6836f-792f-cbea-c446-7c5006378601</uuid> <description>Windows 10 Nvidia Gaming VM</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows_teamgreen.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='13'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='14'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/10d6836f-792f-cbea-c446-7c5006378601_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='4' threads='2'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10 Nvidia Gaming VM/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows/Desktop/Windows10.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.126-2.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:80:7e:0f'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 10 Nvidia Ga/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <sound model='ich9'> <alias name='sound0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </sound> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x21' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <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='0x21' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> <domain type='kvm' id='2'> <name>Windows 10 Test VM</name> <uuid>3b0e8e8c-0a1d-882d-dfa6-983bb288c07d</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='10'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/3b0e8e8c-0a1d-882d-dfa6-983bb288c07d_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='2'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10 Test VM/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows/Desktop/Windows10.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.126-2.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:21:97:cb'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-2-Windows 10 Test VM/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <sound model='ich9'> <alias name='sound0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </sound> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <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='0x0d' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> <domain type='kvm' id='3'> <name>pfSense</name> <uuid>a88a096d-20e4-2cc4-0d4d-48787381d881</uuid> <description>pfSense Firewall</description> <metadata> <vmtemplate xmlns="unraid" name="FreeBSD" icon="freebsd.png" os="freebsd"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='2'/> </cpu> <clock offset='utc'> <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='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/pfSense/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Firewalls/pfSense/pfSense-CE-2.4.0-RELEASE-amd64.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:5f:5a:e0'/> <source bridge='br0'/> <target dev='vnet2'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/2'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-3-pfSense/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' 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' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x24' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> server-diagnostics-20171217-1638.zip
December 18, 20178 yr Appreciate the addition of the Tehuti drivers but can't seem to boot with this update. I am getting bonding errors even though bonding is not setup and my networking doesn't seem to ever start properly giving me recursive errors during boot. I can boot in safe mode but it hasn't provided me much help. I have rolled back to 15e for now.
December 18, 20178 yr I'm having the same KVM hanging problem. Just wondering how do I downgrade to rc15c?
December 18, 20178 yr 9 minutes ago, ren88 said: anybody know how to remove the pause status in unraid os windows 10 A VM usually pauses if it's running out of space, not the vdisk itself but the device where the vdisk is stored.
December 18, 20178 yr ok, i have 750gb as a parity, while my 200gb is on windows 10 my 250gb is extra space
December 18, 20178 yr 8 minutes ago, ren88 said: ok, i have 750gb as a parity, while my 200gb is on windows 10 my 250gb is extra space Can't say I understood that, can you post your diagnostics: Tools -> Diagnostics
Archived
This topic is now archived and is closed to further replies.