>, and thread showed high cpu use. > >then I tried your next suggestion... > qemu-img create win1.img 20G > kvm -hda win1.img -cdrom win2003*.iso -m 1G -boot d > >my actual line was: > sudo kvm -hda win1.img -cdrom win2k3.iso -m 1G -boot d >and the returned the error "Could not initialize SDL - exiting" >next I did > sudo kvm -hda win1.img -cdrom win2k3.iso -m 1G -boot d -vga cirrus >still got the same error.
Ok, I see, so you're doing this remotely. >if I substitute >-drive file=win1.img >with >-drive file=/mnt/slices/newtuna.qcow2,if=virtio,index=0,boot=on,format=qcow2 > >it no longer works. Where did you get your virtio drivers from (/mnt/isos/virtio-win-1.1.11-0.iso and /mnt/isos/viostor-31-03-2010-floppy.img)? Those are pretty delicate, so thus far it would seem we should look into 1) the windows virtio drivers as your not-booting problem 2) either the virtio drivers or qcow causing your slow install -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/671163 Title: win2k3 guest has blank screen and high cpu on first boot -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
