Tried through both the application launcher in KDE and on a terminal. There’s nothing except for a bunch of GTK warnings that pop up on every GTK application.
Actually there is one line among the output:
I/O warning : failed to load external entity "/etc/vmware/hostd/proxy.xml"
Not sure how relevant that is though?
Hadn’t tested that yet, so created a new one and unfortunately no
I was just spit-balling things that should be available thru DNF. I’m afraid I mostly do the QEMU thing through vmm / cockpit, but can;t hurt to be a sounding board?
Also I went the path of least resistance going 'Buntu, with gnome.
Yeah I might go QEMU eventually too. The only reason I was going for vmware player was because at the time I wanted to get weebshin impact to run, but since that’s pretty much dead already anyway it’s not a necessity anymore. It just kinda bothered me today and I wanted to try it again (also need a Windows VM for something else, doesn’t need GPU acceleration tho).
I used virtualbox on Windows too because it was an easy solution (also didn’t know VMware was sort of free at the time), but both VirtualBox and qemu don’t have good working hardware GPU acceleration from what I read, while vmware-player has… supposedly.
Anyway tho, installed VirtualBox and VM didn’t start due to missing Kernel module so… gonna reboot.
OK so I don’t seem to be able to create a QEMU VM through virt-manager, gone through the wizard and at the end it tells me Unable to complete install: 'unsupported configuration: 'directory' storage format is not directly supported by QEMU, use 'dir' disk type instead'. I can’t even select directory or dir anywhere…
So back to VirtualBox… When starting the VM I get AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).. I’m confused cause I’m fairly sure that is enabled in BIOS… gonna check.
Yes created a new one since I never had a QEMU image to begin with.
Back from my tour through the BIOS and unless the option is in a really obscure place I can’t even disable Virtualisation if I wanted to… or enable for that matter. But I’m fairly sure I ran a Linux VM back on Windows so that shouldn’t be an issue.
As for grub, I’m not sure where to start but my kernel parameters don’t have anything Virtualisation related from what I can tell:
set default_kernelopts="root=/dev/mapper/fedora_localhost--live-root ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet "
On a sidenote: a bit odd that Vbox is the only one of the 3 that is complaining about it, would think all 3 had such checks in place…
That is odd, and if that was the problem, I guess the others should have errored out with it.
It appears that AMD-V might also be called SVM mode, which you probably came across, and is probably already set.
it seems some people used
dmesg | grep “AMD-V”
to check for iommu groups, which came up with a bunch of iommu lines. If you have lines like it, then I’d say it must be enabled, and that tree is the wrong one to bark at?
(I had to ctl-f to find then AMD-V bit, which had a bunch of AMD-Vi listings in the OP’s section. I understand this link is for QEMU, but that one check should be agnostic VFIO in 2020 Fedora 32 - An alternate route )
Try to use the update-alternatives system instead of aliases. Shell aliases only work for interactive shells.
On my Ubuntu vi has an alternatives entry already. update-alternatives --display vi shows all the options. You can choose one with update-alternatives --config vi. If your nvim isn’t in there, then you’re going to need to add a new alternative of your own. Read the manpage because I forget the details of how to do that.
I know what the variable is for and I figure maybe someone used single quotes instead of double quotes somewhere (I am using a few plugins), but why would it only happen when I use sudo?
I guess I’ll turn off some plugins and see if it goes away.
You can always make your own symlinks in /usr/bin, /usr/local/bin or similar locations. Just make sure it appears earlier in PATH than the actual vi. You may need to rename vi to vi.basic or whatever.