After further experimenting, I note that kvm run from the command line
allows for -cpu phenom, while virt-manager doesn't.
Nonetheless, I'm getting the Windows XP install hanging very early in
the process, just after copying the files and rebooting into a graphical
environment. It does this more or less the same no matter which
processor I select.
The install isn't locked up. The message screen keeps changing, but it
never progresses past that point.
I had more luck earlier when I was trying to run existing images. At
least they would sometimes let me log in before freezing or blue-screening.
As I said in my previous e-mail, it appears that something is not
working in kvm on my system. If it's not the bulldozer processor, then
possibly it's the associated chip set.
The only clue I have is that the behaviour during the clean installs is
more consistent than what I was experiencing running pre-existing
images. When I select -cpu qemu64 or -cpu phenom the install hangs after
bringing up the graphical display showing "installing system" and 39
minutes remaining.
When I select -cpu kvm64, it locks up with a grey screen before bringing
up the "installing system" progress screen. If I shut down the vm and
restart it, I end up back at the same point as with the other cpus.
To be clear, my Debian/Wheezy system is otherwise functioning properly,
other than the occasional glitch to be expected from testing software.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
