Comment 8 for bug 379991

I have also had a similar problem. Booting Windows XP worked fine this morning until I received an auto-update that included a new kernel. When I boot 2.6.28-13-generic, it fails. When I boot 2.6.28-11-generic, it works fine.

When it fails: The bios screen shows. I can get into the windows boot menu fine but once I start the actual OS boot process, it seems to just sit and spin on the processor.

When it works: It seems to spin the processor around 50% for a few seconds but the screen flickers and it eventually breaks out of it. When it fails, it seems like it just never gets passed whatever it was doing there.

BTW, I have another XP machine that seems to work fine. Difference is that I don't run it as root and it probably doesn't have all of its updates.

My info (using same command as Bob Manners):

pcross@pcross-laptop:~$ ps -wwfp $(pgrep -d, -x kvm)
UID PID PPID C STIME TTY TIME CMD
root 4135 1 42 15:29 ? 00:05:49 /usr/bin/kvm -S -M pc -m 512 -smp 1 -name WindowsXP_root -uuid deaeb78d-5ded-d124-8870-d3748ce4f5ab -monitor pty -pidfile /var/run/libvirt/qemu//WindowsXP_root.pid -localtime -no-acpi -boot c -drive file=/var/lib/libvirt/images/WindowsXP_root.img,if=ide,index=0,boot=on -net nic,macaddr=54:52:00:3e:98:a5,vlan=0 -net tap,fd=16,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:0 -k en-us -soundhw es1370