Jorge - Just wanted to drop you a message to say a belated "thanks" (been so busy didn't have time to check everything on both systems until yesterday)! Anyway, your mention that you were successfully running Windows Server 2003 inspired me to redouble my efforts. I did a new, clean installation using kvm-35 and, much to my satisfaction, it worked straightaway on the AMD box. I then copied the drive image over to the Intel box and that, too, worked without a hitch.
So, something was hosed in my original drive image. Not sure what, but whereas time is at a premium these days, I've already deleted them and am happily testing my working installation with visions of going production in the next couple of months. I very much appreciate your help and (especially) the respect with which you treated my inquiry. Many, many thanks! - Clive Jorge Lucángeli Obes wrote: > On 8/16/07, Clive Stewell <[EMAIL PROTECTED]> wrote: >> I have been attempting to get Windows Server 2003 running under KVM and >> am having some difficulty in doing so. I have tried it on both AMD and >> Intel-based machines and it crashes on each. Below is some basic >> information about my setup followed by the output from the crashes. >> >> ===== >> Additional Information >> >> Both systems are running Ubuntu Feisty and each is entirely current on >> its patches. When using the Ubuntu-installed tools Windows 2003 Server >> runs on the Intel box, but not the AMD box. > > I'm running a 32-bit Windows 2003 Server guest on a 64-bit Xubuntu > Feisty host (Core 2 Duo 5600) using kvm-35 with no problem: don't > despair, it can be done =). > >> In both cases the build was configured as follows: >> >> ./configure --prefix=/opt/kvm-35 --qemu-cc="/usr/bin/gcc-3.[34]" >> >> Note that I am unclear as to when to use the --with-patched-kernel >> option (wasn't sure if this was just for when you wanted kvm baked >> directly into the kernel -- would love clarification on exactly what a >> "patched kernel" is). > > --with-patched-kernel simply uses the kernel modules bundled with your > kernel (since 2.6.20) instead of using the modules bundled with the > kvm release. Most of the times, the modules bundled with the release > are newer than the ones in the kernel, with the (only?) exception of > using git repos directly (for example kvm.git). > >> been doing. I assume that what I did above was right as I can run Ubuntu >> Feisty as a guest without any issues whatsoever on KVM-35. > > It seems what you are doing is correct. However, try removing > 'no-acpi' from your command line. Right now I'm not using 'no-acpi' on > my 2003 command line: > > qemu-system-x86_64 -m 512 -no-reboot -localtime -net nic,model=rtl8139 > stuff/qemu/2003.img -net user > > And when I add it I get the same unhandled VM exit as you. > > Cheers, > Jorge > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
