Getting adobe XD working on Linux (plus passthrough stuff)

[nickelghost]

Hello there!

I got quite a bit into design recently. I’m almost finished with designing one project, but then there are many issues that arose. I have to reboot into Windows to do the designs, which is simply annoying. The other, more important issue is that even when I finish a project, I can’t access the dimensions, relations and colours easily. Perhaps there is a piece of software that would make that easier from pdf or png files?

Since as far as I know, nobody got it working with Wine, so I tried running it on Virtualbox. However, I’m out of luck again. It gives me the following error:

So it looks like my only option is to do a GPU passthrough for Virtualbox, so I have a few questions. My hardware is an i7 8770 and an RX590.

1. Can I do the pass for my Intel GPU and just use XD with it, whilst using the RX for everything else?
2. Is there a way to do it without Synergy?
3. Is switching between OSes only done through a monitor input change?
4. If I pass the RX, will I have to use my Intel GPU everywhere else?

[Enwyn]

I dont have a straight yes to you, but if then this might get you started:

HowTo: Headless VFIO Host

Figured I would document my recent success in getting a Threadripper system to pass through both GPUs to VMs without requiring a third video card, or any kernel patches. This will be just a quick rundown for those that are looking to do the same, I will not be providing help or support on this, but it should get you started should you be looking to do the same. Requirements: The primary video card MUST be something that can be re-posted, such as Intel or NVidia If you are using a VEGA, it must be the secondary card and must NOT post at boot as at this time FLR on this card is broken. If your primary is a NVidia card and it won’t post first, enable CSM, this was the only way I could achive this on my Gigabyte AORUS x399 Gaming 7. Follow the usual method of setting up your host for VFIO, be sure you have a method of remote access (SSH) as once it’s booted headless you will not be able to use the machine. As many have found, blacklisting the primary video driver is not enough to allow the video device to be passed through to a VM as the efifb kernel driver will mmap the BAR of the video card. To prevent this you can add the following to your kernel boot arguments: video=efifb:off Once this is done, after the bios boots the kernel, you should see no further screen updates, the system will appear frozen, but it isn’t. The card is now free to be passed through into a VM. If you want to see the technical of why this works, see the source code here. If you are using a NVidia card as your primary device, after posting the VGA BIOS will not be accessible, to work around this dump the BIOS first and provide it to the vfio device in qemu as romfile=/path/to/the/vgabios.rom. You can use the nouveau driver to dump the rom. Using the above information I have two VM’s operating, one running Windows 10 with a GeForce 1080Ti, and the other running Linux on an AMD Vega 56. The host is headless as it now has no VGA adapter at all.

Also iommu groups for your motherboard might be an issue.

2. Looking glass? Or Remote desktop.
3. Or Looking glass?
4. Unless you want to restart your screen session when you unbind stuff.