TheExplorographer
-
Posts
83 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by TheExplorographer
-
-
On 1/28/2020 at 12:05 PM, 1812 said:
step 1: backup your .img os
step 2: make a new vm but have the disk location point to your old image instead of creating a new one
step 3: boot with vnc only and verify .img os works
step 4: shut down vm, reassign GPU
step 5: boot vm
step 6: report findings
Too late. Already dumped that VM and created a new one from scratch. So far it is working. But, I have no confidence in it at this point.
-
8 hours ago, johnnie.black said:
No, you posted on the general support forum and I moved it since this was about KVM, bug reports are here:
https://forums.unraid.net/bug-reports/stable-releases/
Okay, Well I thought I posted it to the right place. That was my mistake. Maybe next time, tell the person where to properly post it when they get it wrong. Rather than moving it to what is basically a junk forum as I don't see a lot of support here. At this point to avoid further frustration, Ill just find another solution and/or wait for an update as well as hold off on building my 2nd unraid server.
-
Well, I posted it in Bug Reports, then someone moved it to here. 😕 So I run a Win 10 VM with a GTX1060 pass through. And have for years now. 6.8.1 ended that. With the boot up freezing at the TianoCore logo after the windows spinner spins 2.5 times. All 4 assigned cores peg at 100% and stay there. It never leaves that point unless I force stop it. I have several Linux installs as well. I have not tried them. As I have said, I use the Windows VM as a streaming computer and I stream every day. So after updating I really have limited time to get the VM back up and running. I have tried just about every setting. Someone mentioned a corrupt NVRAM file but I have no idea on how I would fix that.
-
I am stuck here and rather furious that there is no support for this.
-
Well I just tried to update to 6.8.2 and my VM is frozen again with 100% CPU usage on assigned cores. Something major changed in 6.8.1 that was not in 6.8.0 and is stopping me from upgrading. How do I get support on this? I use this VM as a streaming VM for my work. Right now I am dead in the water.
-
1 hour ago, bland328 said:
For the record, I solved this...but I'm not sure what to make of it. And it almost surely has nothing to do with the OP's problem, but I'll leave the solution here anyway, in case it helps someone else:
Apparently, the 'OVMF_VARS.fd' file (OVMF NVRAM backing for the VM) for that VM became corrupt. It is stored in an unassigned btrfs volume on an NVME drive, and the btrfs volume itself does not appear to be corrupt.
I've no idea what happened there, but hopefully (and probably) it has nothing to do with Unraid 6.8.1.
So what did you do? Erase the file? Just curious. Also when my VM looked as if it was running but failed, the cores assigned to it were pegged at 100% until I manually stopped it.
-
Nothing??
-
Rolled back to V6.8.0 and the VM started right up. This is a problem with the update.
-
Well it's worse than that. I restarted my UNraid server via Shutdown on the menu... now the server will not start. No drive errors that I know of. Passed my last parity check with flying colors as usual. This all happened after I updated tonight to 6.8.1. I need my server back. -
<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
<name>Windows 10</name>
<uuid>4e855806-e29f-cb54-f4b6-7d4897952465</uuid>
<metadata>
<vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
</metadata>
<memory unit='KiB'>16777216</memory>
<currentMemory unit='KiB'>16777216</currentMemory>
<memoryBacking>
<nosharepages/>
</memoryBacking>
<vcpu placement='static'>4</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='1'/>
<vcpupin vcpu='1' cpuset='5'/>
<vcpupin vcpu='2' cpuset='3'/>
<vcpupin vcpu='3' cpuset='7'/>
</cputune>
<os>
<type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type>
<loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
<nvram>/etc/libvirt/qemu/nvram/4e855806-e29f-cb54-f4b6-7d4897952465_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='none'/>
<source file='/mnt/user/domains/Windows 10/vdisk1.img'/>
<target dev='hdc' bus='virtio'/>
<boot order='1'/>
<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/Windows10.iso'/>
<target dev='hda' bus='ide'/>
<readonly/>
<boot order='2'/>
<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.160-1.iso'/>
<target dev='hdb' bus='ide'/>
<readonly/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</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='ide' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
</controller>
<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:54:22:8f'/>
<source bridge='br0'/>
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</interface>
<serial type='pty'>
<target type='isa-serial' port='0'>
<model name='isa-serial'/>
</target>
</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='0x01' 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='0x01' 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='0x082d'/>
</source>
<address type='usb' bus='0' port='1'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x046d'/>
<product id='0xc06b'/>
</source>
<address type='usb' bus='0' port='2'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x0557'/>
<product id='0x2419'/>
</source>
<address type='usb' bus='0' port='3'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x05af'/>
<product id='0x8277'/>
</source>
<address type='usb' bus='0' port='4'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x0a12'/>
<product id='0x0001'/>
</source>
<address type='usb' bus='0' port='5'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x0fd9'/>
<product id='0x005c'/>
</source>
<address type='usb' bus='0' port='6'/>
</hostdev>
<memballoon model='none'/>
</devices>
</domain>
-
My Windows 10 VM won't start now. It begins to boot then the assigned CPU's jam to 100% and stay there. Spinner below the TIANOCORE logo stuck. I have to force kill it. Prior to 6.8.1 it worked great. Log file shows no errors.
-
OMG hardest contest EVER!! Name 1 thing... well.. the one thing, if I must. The community! UNraid was born from it and is sustained today because of it. I love this OS so much I am about to build my 2nd 40tb beast! Just keep on being awesome!!
-
1
-
-
6 hours ago, illsnryhybrid said:
I was able to downgrade to the last release from 3 days ago. If you edit the booksonic docker and change the repository line to "linuxserver/booksonic:1.1.Release-ls46" no quotes. I'll hold it here and try and update later once we see a fix for the 404 error, as I too was getting the same issue.
Thanks for the tip. It took me a second to find the "tags" page on the dockerHub page, but once I did, I was able to use the information to downgrade.
Thank you for the detailed explanation and line.
-
1 hour ago, saarg said:
Can you try using the previous tag on docker hub? Link in the first post.
I will be honest here, No. I have no idea how to do that, there is no TAG option on my docker config for this app. The previous version worked fine.
-
I am getting the 404 error here too.
-
Wow, what is not to like? Reliability, flexibility, and amazing support. My unRAID server has been one of the best things I have ever built for my home. There is not much more I can say.
-
Okay. Well that solves that. Docker deleted. Thanks for the update.
-
6 hours ago, jonathanm said:
Since the dev posted here literally a few posts above yours less than 7 HOURS before your comment, what do you think?
Well, since it hasn't been updated with this fix...I wonder why I think that? Keep your CAPS SLAMS to yourself. The plugin has been broken for quite a while. So before I donate to the cause...I asked the question.
-
So has the dev just abandoned this?
-
On 2/21/2019 at 9:22 AM, jowi said:
I've installed the Dropbox folder on a XFS formatted SSD, and manually upgraded the glibc in the docker to 2.23 using https://slackware.pkgs.org/14.2/slackware-patches-x86_64/glibc-2.23-x86_64-4_slack14.2.txz.html since Dropbox logging was also complaining that it needed a glibc version >2.19 (docker has 2.17) and now it is working again.
Glad you got it fixed. Any chance that you can explain the procedure for manually updating the LIB? I am having the same issue and need to fix asap.
-
Just updated to 6.8.1 and VM failed
in VM Engine (KVM)
Posted
Well, lets just agree to disagree then. I'll weigh this exchange against my view of "support" going forward.