Woodpusherghd

Members
  • Posts

    236
  • Joined

  • Last visited

Report Comments posted by Woodpusherghd

  1. Upgraded to RC6 and experienced spontaneous shut downs.  I also experienced lock ups when attempting to attach my IPhone via usb. No problems with RC5 which I have down graded to.  I've attached my syslog which I have been mirroring to my flash drive as well as my diagnostics file from RC5. I'll upgrade again to obtain a diagnostic file from RC6 if that would be helpful  Let me know.  I suspect the culprit may be the latest qemu which is implemented in RC6.  Another suspect is the auto fan plugin which I disabled when I noticed my cpu temps were spiking which may have caused the shut downs but doesn't explain the lock ups when attaching my phone.

    tower-diagnostics-20191120-1239.zip syslog.txt

  2. Quote

    Tried 6.8.0-RC1 and ran into a problem with my Windows 10 VM.  I have a wireless mouse and keyboard connected through a Logitech Unifying Receiver.  Under V6.7.2 when I booted unRaid into GUI mode I could use the mouse and keyboard.  When I started the Windows 10 VM (passing through an AMD 5450 GPU) the unifying receiver was also passed through and I could use the mouse and keyboard in the VM.  When I booted 6.8.0-RC1, the mouse and key board were not usable in the VM and when I tried to hot plug the receiver, I got an error messge that it was already being used by Qemu.  BTW, I have an additional video card that unRaid boots into and I can switch back and forth from unRaid and the VM using a hdmi switch.  In the case of v6.7.2, when the mouse and keyboard were usable in the VM, they were not usable in unRaid. In V6.8.0-RC1 the mouse and keyboard were usable in unRaid even after the VM booted.  It's as though V6.7.2 would release the mouse and keyboard to the VM while V6..8.0-RC1 doesn't.  Anyone else experience this problem?

    I didn't have this problem with RC5 which reverted qemu but I have it once again with RC6 with the latest stable qemu.  I posted in the usb hot plug thread and the plugin author said it wan't a problem with his plugin. A minor annoyance.

  3. On 10/18/2019 at 8:31 AM, Woodpusherghd said:

    Tried 6.8.0-RC1 and ran into a problem with my Windows 10 VM.  I have a wireless mouse and keyboard connected through a Logitech Unifying Receiver.  Under V6.7.2 when I booted unRaid into GUI mode I could use the mouse and keyboard.  When I started the Windows 10 VM (passing through an AMD 5450 GPU) the unifying receiver was also passed through and I could use the mouse and keyboard in the VM.  When I booted 6.8.0-RC1, the mouse and key board were not usable in the VM and when I tried to hot plug the receiver, I got an error messge that it was already being used by Qemu.  BTW, I have an additional video card that unRaid boots into and I can switch back and forth from unRaid and the VM using a hdmi switch.  In the case of v6.7.2, when the mouse and keyboard were usable in the VM, they were not usable in unRaid. In V6.8.0-RC1 the mouse and keyboard were usable in unRaid even after the VM booted.  It's as though V6.7.2 would release the mouse and keyboard to the VM while V6..8.0-RC1 doesn't.  Anyone else experience this problem?Same issue with RC3.  Tried normal boot (Not GUI) same problem. I can use my VM with a wired mouse and keyboard so the issue lies with the Logitech unifying receiver.

     

    Diagnostics attached.

     

    I made some progress.  After booting into my Windows 10 VM I switched back to the unRaid GUI and using the libvirt hotplug usb plugin, I detached the unifying receiver from the VM and then reattached it.  Now I can use my wireless mouse and keyboard in ther VM. I'm starting to believe that the plugin is not fully compatible with RC3. I've attached diagnostics.

    tower-diagnostics-20191023-1127.zip

  4. Quote

    Tried 6.8.0-RC1 and ran into a problem with my Windows 10 VM.  I have a wireless mouse and keyboard connected through a Logitech Unifying Receiver.  Under V6.7.2 when I booted unRaid into GUI mode I could use the mouse and keyboard.  When I started the Windows 10 VM (passing through an AMD 5450 GPU) the unifying receiver was also passed through and I could use the mouse and keyboard in the VM.  When I booted 6.8.0-RC1, the mouse and key board were not usable in the VM and when I tried to hot plug the receiver, I got an error messge that it was already being used by Qemu.  BTW, I have an additional video card that unRaid boots into and I can switch back and forth from unRaid and the VM using a hdmi switch.  In the case of v6.7.2, when the mouse and keyboard were usable in the VM, they were not usable in unRaid. In V6.8.0-RC1 the mouse and keyboard were usable in unRaid even after the VM booted.  It's as though V6.7.2 would release the mouse and keyboard to the VM while V6..8.0-RC1 doesn't.  Anyone else experience this problem?

    Same issue with RC3.  Tried normal boot (Not GUI) same problem. I can use my VM with a wired mouse and keyboard so the issue lies with the Logitech unifying receiver.

     

    Diagnostics attached.

    tower-diagnostics-20191019-1140.zip

  5. Tried 6.8.0-RC1 and ran into a problem with my Windows 10 VM.  I have a wireless mouse and keyboard connected through a Logitech Unifying Receiver.  Under V6.7.2 when I booted unRaid into GUI mode I could use the mouse and keyboard.  When I started the Windows 10 VM (passing through an AMD 5450 GPU) the unifying receiver was also passed through and I could use the mouse and keyboard in the VM.  When I booted 6.8.0-RC1, the mouse and key board were not usable in the VM and when I tried to hot plug the receiver, I got an error messge that it was already being used by Qemu.  BTW, I have an additional video card that unRaid boots into and I can switch back and forth from unRaid and the VM using a hdmi switch.  In the case of v6.7.2, when the mouse and keyboard were usable in the VM, they were not usable in unRaid. In V6.8.0-RC1 the mouse and keyboard were usable in unRaid even after the VM booted.  It's as though V6.7.2 would release the mouse and keyboard to the VM while V6..8.0-RC1 doesn't.  Anyone else experience this problem?