Install vmware workstation on fedora 29 driver#

I do have the spice guest tools installed, did that first, then updates, then installed the desired programming software.

Install vmware workstation on fedora 29 driver#

In the VM I can see the offending device as a pci device, that I cannot load a driver for. That leaves the software I need functional, but only partially since I cannot connect to external devices to download the programs I write for them. In boxes, I can use normal USB connected things like thumb drives and keyboards/mice/tablets, but not communication devices since they don’t get mapped to /proc/bus/usb but to /dev/bus/usb. On Silverblue, I can get the image to work in Boxes, but not with Virt-Manager layered. It works on Virt-Manager, at least it did for me when I ran Fedora Workstation. I have used qemu-img for converting vmdk images to qcow2 in the past. I’ll do some testing tomorrow with software I run normally on Windows to see how it behaves. I had to adjust the screen resolution, and it seems a bit sluggish and unresponsive. I found a Win7 Pro vmware image I was able to get going in boxes. I know I can use virt-manager and libvirt on a standard workstation of Fedora 29 to achieve this goal, and will do that if needed, but I would like to try it first with Silverblue and was wondering of someone else has already done this. I’ll check out the msdn link you mention, I don’t mind lurking about the site. Plus, some of the things I’m going to have to figure out will be applicable for the guide I am working on for Silverblue.

If I have to I’m going to go the route of a Fedora Workstation laptop with the VM’s but I would like to try this way first so I can do everything on my Silverblue desktop and get it working, then make the laptop switch. Mainly I just want to replicate my windows capabilities and make my laptop into a Silverblue laptop. I’ll try the other images I have this was the bare bones original I started with for all of them. It is reporting as corrupt on the Windows box by vmware. It appears that one particular image I tried to use is the problem in this case.