I looked at the various FAQs and googled all around for my answer and came up 
dry. If this is a newbie question, please point me to the right resource and 
I’ll go educate myself.

That said, I installed Win10 under qemu on a linux host over a year ago. It has 
run beautifully.

Recently I transferred the image to my OSX laptop so I could run a windows 
program there. The boot script I had under linux doesn’t work. I knew I’d have 
to change the networking configuration a little bit, but I’m running into a 
more fundamental problem. Windows won’t boot.

On bootup, Win10 goes into an endless loop of “repairing” the installation 
which never succeeds.

I assume this is because I needed to change the CPU definition for qemu and now 
Windows is missing some drivers in order to boot. 

I am going to inline my ORIGINAL script (that booted fine on linux) and my 
REVISED script which goes into an infinite repair loop on OSX. I am hopeful 
someone can suggest an edit to get it working. Alternately, if I need to 
reinstall windows please suggest the right emulated hardware setup that will 
make it easiest to copy the image back and forth between linux and OSX.

ORIGINAL boot script

#!/bin/bash
qemu-system-x86_64 -enable-kvm -m 8G -cpu host \
          -machine pc-q35-2.4 \
          -smp cores=2 \
          -usb -device usb-kbd -device usb-tablet \
          -smbios type=2 \
          -soundhw all \
          -hda win10.img \
          -netdev 
bridge,id=net0,br=br0,"helper=/usr/lib/qemu/qemu-bridge-helper" -device 
e1000-82545em,netdev=net0,mac=00:0c:29:0f:1d:aa \
          -device 
qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16 \
          -uuid 564defd0-b124-a042-570f-561d0axxxxx

REVISED script

#!/bin/bash
qemu-system-x86_64 -m 8G \
          -no-kvm \
          -smp cores=2 \
          -usb -device usb-kbd -device usb-tablet \
          -smbios type=2 \
          -soundhw all \
          -hda win10.img \
          -netdev user,id=n0 -device rtl8139,netdev=n0,mac=00:0c:29:0f:1d:aa \
          -uuid 564defd0-b124-a042-570f-561d0xxxxxx

Thank you for your help!


Reply via email to