frodr Posted October 7, 2019 Share Posted October 7, 2019 The MacOS kvm starts, but I can not connect. Kvm log show a red line. 2019-10-07 14:15:37.291+0000: Domain id=2 is tainted: high-privileges 2019-10-07 14:15:37.291+0000: Domain id=2 is tainted: custom-argv 2019-10-07 14:15:37.291+0000: Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/1 (label charserial0) Syslog: Oct 7 16:25:15 Maxx kernel: FAT-fs (nvme0n1p1): Directory bread(block 6334) failed The nvme0n1p1 is a ssd Passthrough another kvm. I can't see any reference to this drive in the xml, but then again I am not an xml pro. Hope anyone can help. xml.rtf Quote Link to comment
frodr Posted October 7, 2019 Author Share Posted October 7, 2019 It used to work fine with the onboard AsMedia GPU. Going back to VNC, and later ASMedia it failed. Supermicro X11DAI-N, version 1.02 | AMI 3.1 | dual Xeon Silver 4116 | 64 MB RAM | 4 x WD SSD in RAID 10 Cache l Unraid 6.72 l Quadro RTX4000 for Plex docker l GTX 1070 for MacOS kvm l Samsung 970 Pro nvme for MacOS kvm Quote Link to comment
johngc Posted January 31, 2020 Share Posted January 31, 2020 Did you ever get to the bottom of this - I am in the same position. I set up an OSX VM using VNC and it worked. Installed an AMD RX470 card and passed it through and get a blank screen. Switch back to VNC and I get the above "Guest has not...." error. The OSX VM will not boot - I have splash top installed and it never gets that far 😞 VM logs show the same last four lines as above... Quote Link to comment
caplam Posted March 1, 2020 Share Posted March 1, 2020 (edited) I also have the exact same problem. edit: i drop. I'm fed up with editing xml twice as soon as i make a minor change. Think i'll be back to proxmox for my vms. Edited March 1, 2020 by caplam Quote Link to comment
swallace Posted March 2, 2020 Share Posted March 2, 2020 (edited) I’ve run into this issue before. I think something in the XML gets screwed up when switching between, adding, and removing Graphics passthrough. If you’re using macinabox, I’d recommend deleting the XML file for your VM (the actual file, not its contents) and letting macinabox generate a new one. It ought to boot afterwards into VNC, but you’ll have to go back through to customize your config. Edited March 2, 2020 by swallace Wrong terminology Quote Link to comment
[email protected] Posted December 15, 2020 Share Posted December 15, 2020 I had the same issue recently. My solution was to use the User Scripts '1_macinabox_helper' to re-generate the VM's xml and this works for me. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.