Jump to content

thomas

Members
  • Content Count

    69
  • Joined

  • Last visited

  • Days Won

    1

thomas last won the day on April 6 2018

thomas had the most liked content!

Community Reputation

9 Neutral

About thomas

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. You can use virt-manager from linux or a virt-manager docker, if you're running mac or windows, and all your XML changes will remain when making hardware changes.
  2. If it's the main graphic card (the one that displays the unraid boot sequence) you'll always need it. This is my case also.
  3. I like how easy is to create VMs. I'd like to see KVM/QEMU with virtio-gpu virgl support.
  4. Q35 is under machine type, below the memory size and it has to be chosen instead of i440fx. It will be best to create a new VM from scratch and choose Q35 and reinstall Windows. Reusing the old VM is still possible by manually choosing the old VM's vdisk.
  5. Have you tried to use http://kb.macrium.com/KnowledgebaseArticle50005.aspx?Keywords=VHD and then convert the VHD to IMG with something like qemu-img convert -f vpc -O raw lamp-3-x86.vhd lamp.raw ?
  6. I'm also using Legacy Mode, because with the UEFI it never worked properly. Also the vbios is required for me to actually show the image before fully loading the OS...
  7. "Summary Add emulation of the ICH9 host chipset as an alternative to the current I440FX emulation. This will allow for better support of PCI-E passthrough since ICH9 uses a PCI-E bus whereas the I440FX only supports a PCI bus." from https://wiki.qemu.org/Features/Q35 You can read more in forum, but this is a good post I also have an AMD graphic card and I have seen a lot of your issues.
  8. This is just to confirm the fix is working properly in your case.
  9. Use virt-manager on linux or djaydev/docker-virt-manager, you can find it under Apps.
  10. For me, when a VM gets stuck at Tianocore it usually after a force stop of a VM and the graphic card remaining in an unknown power state. My only way to recover is to power down the server, then power it up and the VM with passthrough graphic card will start properly. Try that and see how it goes...
  11. After more testing it seems the option "Local gateway uses NAT: Yes" is the problem. If you choose "No" the docker works properly and it seems that I can still connect through Wireguard to my server
  12. Indeed, if you stop the wireguard you can access the webpage of the Adguard docker.
  13. I have the same issue. The docker works fine until I start the VM. After that the web page is not accessible and I can't even ping it. I have to stop the VM and then the docker start working again and responding to pings. Docker is configured to use Custom : br0 with a unique IP and the VM is using a different fixed IP. Before updating to 6.8.0 -rcX was working fine. unraid-diagnostics-20191019-0131.zip
  14. diskutil apfs resizeContainer disk0s2 0 In this case, diskutil automatically claims all available free space on the physical storage device, but you can also replace 0 with a size value, if you want a specific one