Jump to content

waschbenzin

Members
  • Content count

    68
  • Joined

  • Last visited

About waschbenzin

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

1,578 profile views
  1. Welcome to the thread and thumbs up for reading the thread first! Getting it to work in a window first and passing the graphic card through later, sound like a good plan. You will be fine, with one set of mouse and keyboard. You have a few options to go with: 1) Pass your mouse and keyboard through qemu window (click inside window - strg+alt to release mouse and keyboard from vm) 2) Pass your usb input devices to the vm 3) Pass your usb controller to the vm 4) No mouse/keyboard in the vm - Controll it via remote desktop/synergy I'm using option 3) with an additional ps2 keyboard to controll the host, if needed (hardly ever the case... if you vm is stable you can just ssh into the host). I suggest starting with option 1) and switch to one of the others if needed. You can use option 1) even if you passthrough your graphics card. Again you have multiple options to use as a disk. 1) image file (with a virtual hard disk) 2) partition/disk (with a virtual hard disk) 3) passing a controller (with a real hard disk) 4) network shares (don't know if that boots) I'm using option 2) (encrypted logical volume) for the root partition and 4) for additional data (served from the host). Performance wasn't an issue so far. About the graphics card, you should probably use something recommend for hackintoshes. Have a look at some (buyers) guide, what to get or search the forums what has been used successfully (on a real hackintosh). For cheap 4k, you might want to get a Gigabyte GTX 950 OC. I haven't tried this card, but it is on a recommendation list and it supports 4k displays.
  2. @Hameer Abbasi Could you share your Clover configuration? Right now I can't boot cpu models beyond core2duo, but I had it working at some point. If I recall correctly, I was able to boot with cpu models up to SandyBridge.
  3. Here is my usb qemu command: # unbind usb controller devices echo "8086 8cb1" > /sys/bus/pci/drivers/vfio-pci/new_id echo 0000:00:14.0 > /sys/bus/pci/devices/0000\:00\:14.0/driver/unbind echo 0000:00:14.0 > /sys/bus/pci/drivers/vfio-pci/bind echo "8086 8cad" > /sys/bus/pci/drivers/vfio-pci/new_id echo 0000:00:1a.0 > /sys/bus/pci/devices/0000\:00\:1a.0/driver/unbind echo 0000:00:1a.0 > /sys/bus/pci/drivers/vfio-pci/bind echo "8086 8ca6" > /sys/bus/pci/drivers/vfio-pci/new_id echo 0000:00:1d.0 > /sys/bus/pci/devices/0000\:00\:1d.0/driver/unbind echo 0000:00:1d.0 > /sys/bus/pci/drivers/vfio-pci/bind # unbind nvidia gpu echo "10de 1184" > /sys/bus/pci/drivers/vfio-pci/new_id echo 0000:01:00.0 > /sys/bus/pci/devices/0000\:01\:00.0/driver/unbind echo 0000:01:00.0 > /sys/bus/pci/drivers/vfio-pci/bind echo "10de 0e0a" > /sys/bus/pci/drivers/vfio-pci/new_id echo 0000:01:00.1 > /sys/bus/pci/devices/0000\:01\:00.1/driver/unbind echo 0000:01:00.1 > /sys/bus/pci/drivers/vfio-pci/bind echo 1 > /sys/module/kvm/parameters/ignore_msrs nice -n -10 qemu-system-x86_64 \ -enable-kvm \ -m 16384 \ -cpu core2duo,kvm=off,vendor=GenuineIntel \ -smp 6,sockets=1,cores=3,threads=2 \ -M q35 \ -vga none \ -bios OVMF-pure-efi.fd \ -realtime mlock=on \ -smbios type=2 \ -balloon none \ -device ahci,id=hdbus,bus=pcie.0 \ -device ide-drive,bus=hdbus.1,drive=Clover \ -drive id=Clover,if=none,file=clover-image.dd,format=raw \ -device ide-drive,bus=ide.3,drive=MacOSX \ -drive id=MacOSX,if=none,file=/dev/mapper/mac,format=raw \ -netdev user,id=usr0,net=192.168.76.0/24,dhcpstart=192.168.76.9 \ -device e1000-82545em,netdev=usr0,id=vnet0,bus=pcie.0,addr=5,mac=01:02:03:04:05:06 \ -device isa-applesmc,osk="youshouldknowwhattoputhere" \ -device vfio-pci,host=01:00.0,bus=pcie.0,multifunction=on \ -device vfio-pci,host=01:00.1,bus=pcie.0 \ -device vfio-pci,host=00:14.0,bus=pcie.0 \ -device vfio-pci,host=00:1a.0,bus=pcie.0 \ -device vfio-pci,host=00:1d.0,bus=pcie.0 \ -serial stdio # bin usb controller to linux echo 0000:00:14.0 > /sys/bus/pci/devices/0000\:00\:14.0/driver/unbind echo 0000:00:14.0 > /sys/bus/pci/drivers/xhci_hcd/bind echo 0000:00:1a.0 > /sys/bus/pci/devices/0000\:00\:1a.0/driver/unbind echo 0000:00:1a.0 > /sys/bus/pci/drivers/ehci-pci/bind echo 0000:00:1d.0 > /sys/bus/pci/devices/0000\:00\:1d.0/driver/unbind echo 0000:00:1d.0 > /sys/bus/pci/drivers/ehci-pci/bind While this is my usb configuration: Bus 002 Device 002: ID 8087:8001 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8009 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 004: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 003: ID 045b:0210 Hitachi, Ltd Bus 004 Device 002: ID 05e3:0732 Genesys Logic, Inc. All-in-One Cardreader Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 007: ID 1e7d:3232 ROCCAT Bus 003 Device 006: ID 1e7d:2dbe ROCCAT Bus 003 Device 003: ID 1e7d:2ee1 ROCCAT Bus 003 Device 005: ID 06f8:c000 Guillemot Corp. Hercules Muse Pocket Bus 003 Device 004: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 002: ID 045b:0209 Hitachi, Ltd Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Hope that helps. You will lose the ability to control linux with your usb devices until you power down the vm! I use a PS2 keyboard for emergencies. You also cannot use any usb devices connected to that controller in any other vm. You might want to try a secondary add-in usb controller for this (but my luck with that was rather limited - due to hardware incompatibilities). Off-Topic: Anyone who want to expand their qemu experience with another operation system: Try Remix OS to get Android on your PC. Works fine in qemu for me (32-bit version without uefi and without gpu passthrough). I used the installer to create a usb installer. Dumped it using dd and now I'm running off that image. You can use a virtual audio device ( -soundhw es1370 ... thanks to reddit for that). Edit: lspci -nn | grep USB 00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB xHCI Controller [8086:8cb1] 00:1a.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 [8086:8cad] 00:1d.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 [8086:8ca6]
  4. Be sure to compare the right values. Linux process CPU% can go beyond 100% with multiple cores. Idling in Mac OS X gives me 1-2% in OSX and on the Linux host, while the qemu process is at about 10% (4 core ... 8 with HyperThreading). Regarding audio issues: My opinion is, that the virtualized Mac is not suitable for audio editing with low latency stuff. Spare yourself the trouble and use a USB audio adapter, if you can't get HDMI/on-board sound working. Regarding memory usage: AFAIK the VM will use the complete assigned memory when booting as soon as PCI Passthrough is used (at least that was the case when I started researching this - late 2014).
  5. It is just a display bug. I provided the patch and being the C noob I am, I used %d to display the speed of the FSB. Correct would be %lu since it is a 64-bit wide unsigned integer.
  6. This method can be used on Linux (with all the goodies like KVM and PCI Passthrough) or on Mac OSX (but its slow due to the missing KVM). To get QEMU on Mac OSX I would recommend to use homebrew ( see http://brew.sh/... then its probably just brew install qemu to install qemu)
  7. Did anyone update to 10.11.3 yet? Any issues?
  8. Maybe you need to modify something inside Clover. This is mostly hardware specific and you should look at a guide for your graphics card. I don't think, that booting a virtual machine makes a huge difference...
  9. I had it working at some point to boot with up to IvyBridge, but I can't get it to work right now :-\.
  10. @DaGr8Gatzby a) I think the graphics card needs to support UEFI. I'm not sure about this one, but your graphics card is quite old and might not support this. One reason to build a VM with Clover is to get rid of the legacy BIOS and VGA (VGA passthrough is a bit more tricky than PCIe passthrough). Do you see OVMF showing up on the display connected to the card, when you boot without "-vga std" ? Try Linux or Windows guests first. Both are so much easier to deal with. c) Can you confirm your graphics card is attached to the VM? Does it show up in the system profiler (or an lspci equivalent) in Mac OSX? If you are using an up to date version of Clover configurator you can set the QEMU setting with Clover configurator. Older versions didn't show the setting and removed it from the file, but that is history now :-).
  11. My screen tearing was related to a mismatched resolution in OVMF and Clover. OVMF has a default of 800x600 and if I didn't match that in Clover I had screen tearing issues. You can change the resolution in OVMF but I didn't manage to get OSX booting (consistently) with a split OVMF image (to persist the resolution). So for a higher resolution I see two options: a ) fix split image OVMF support for OSX b ) compile OVMF with a different default resolution
  12. I used Ozmosis+OVMF for Yosemite, but it didn't work with El Capitan out of the box, when I started this thread. Also it was problematic because of hardware support, but that was because I used an older version of OVMF. I still plan on giving it another try with the new Ozmosis, although I prefer the Clover solution now. Clover seems to be more widely used, is open source and seems to be updated faster to new versions of OSX.
  13. @NSCXP2005 I completely agree with KillerKelvUK: Get Linux and Windows running first in a Linux hosted QEMU-VM with passthrough. Then try Mac OSX. @KillerKelvUK In Virtualbox the vm needs to be modified to run OSX from command line. It's a few commands and it pretty much works out of the box. Googling things like EfiGopMode, SmcDeviceKey and cpuidset should get you to a working Virtualbox VM - I don't have the commands at hand and I'd rather not spam this thread with an alternative method. Though VirtualBox offers PCI passthrough on Linux, I couldn't manage to attach my graphics card to the VM (vaguly remembering that the machine configuration for PCI passthrough and running OSX are incompatible)
  14. @NSCXP2005: The "insanely fast" part in the thread topic is due to a misconfigured busspeed that makes Mac OS X run at up to 40 times the normal speed. This can be fixed with the new Clover version and the information available in the thread. Who should and who shouldn't use this solution? The way to boot a virtual Mac OSX presented here is rather special and thus only relevant to a minority of users. Using it on Windows or Mac OSX hosts doesn't make much sense, since without KVM the QEMU virtualisation is slow compared to VMware/Parallels/VirtualBox. Even with a Linux host you will have less trouble booting Mac OSX with VirtualBox. So this is most interesting for Linux Users with KVM and PCI passthrough, since none of the other solutions offers that. You could also go one step further and virtualise your whole system with ESXi and use PCI passthrough there... Though its not easy, what you get is huge (in my opinion). I'm running a Linux server (encrypted raid, file server, media server ...) and in cases where I'm not satisfied with the Linux Desktop experience I can fire up Windows or Mac OSX having almost the full power of my machine available in those VMs without rebooting or interrupting the server. My recommendation: Don't use this solution, unless you have a good reason to do so. It's a pretty hard way to go...
  15. @Maclarentosh Are you trying with the provided Clover debug image? Have you checked dmesg for errors from kvm? Have you enabled ignoring MSR? echo 1 > /sys/module/kvm/parameters/ignore_msrs I haven't been lucky using ISO-images much. I would recommend creating an bootable usb drive, dumping it and using that.
×