Bugs item #2411975, was opened at 2008-12-09 07:24 Message generated for change (Comment added) made by jiajun You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2411975&group_id=180599
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Jiajun Xu (jiajun) Assigned to: Nobody/Anonymous (nobody) >Summary: PAE Vista Guest display broken Initial Comment: Testing Environment: Kernel Commit:9ff66047142bd6a22825ada67eeaebbdf60c0280 Userspace Commit:8eae225cf8cd82316fcc78569aeb1adbbc077cb8 Host Kernel Version: 2.6.28-rc6 Bug detailed description: -------------------------- PAE Vista guest may not be able to boot on PAE host. (1) If with 2 vcpus assigned, vista guest can never boot up. (2) If 1 vcpus assigned, sometimes Vista guest can boot up and get network up, but the guest display always shows nothing(black). (3) on 32e platform PAE and IA32e Vista guest can boot up well with smp=1 and smp=2. Reproduce steps: ---------------- (1) qemu-img create -b /share/xvs/img/Windows/ia32p_vista.img -f qcow2 /share/xvs/var/tmp-img_gbp18_1228724677_1 (2) qemu-system-x86_64 -m 768 -smp 2 -net nic,macaddr=00:16:3e:0a:52:36,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /share/xvs/var/tmp-img_gbp18_1228730668_1 ---------------------------------------------------------------------- >Comment By: Jiajun Xu (jiajun) Date: 2008-12-16 00:51 Message: I changed the bug title since the commit 18b8d7e31fda064559e5ddb06e6dd3a2ff21cca0 is for display issue on 32bit host. And we verified with the commit, the issue is fixed. ---------------------------------------------------------------------- Comment By: Avi Kivity (avik) Date: 2008-12-14 05:19 Message: Fixed by: commit 18b8d7e31fda064559e5ddb06e6dd3a2ff21cca0 Author: Avi Kivity <[email protected]> Date: Sun Dec 14 15:16:27 2008 +0200 kvm: libkvm: check for slot overlap using 64-bit arithmetic otherwise, a slot that ends on the 4GB boundary wraps around, resulting in a false positive, and leading to an early failure when attempting to get the bios slot's dirty log (which doesn't have dirty logging enabled). fixed broken display on 32-bit userspace. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2411975&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
