Bugs item #2314737, was opened at 2008-11-19 13:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2314737&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: amd Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: krwi (krwi) Assigned to: Nobody/Anonymous (nobody) Summary: 100% host CPU usage with Win2k guest Initial Comment: After installing Windows 2000 guest with sp4 all seems work fine. But after short time Windows download a large pack of updates (about 68), when I installed this updates and rebooted guest host CPU utilization rised to 100% even if guest is idle. Before installing updates this problem was not observed. I trying with two Win2k installation with the same results. Host CPU utilization is equal to number of vCPUs, for example with -smp 2 host CPU usage is 200%. Host: 2x Quad Core Opteron 8356 64GB RAM OS: Gentoo 64bit kernel: 2.6.25 KVM-78 (modules from package not from kernel) Guest: Windows 2000 sp4 32bit started with command: kvm -M pc -m 2048 -smp 2 -name Win200032sp4 -monitor pty -localtime -boot d -drive file=/dev/MDvg_InstallVM/Win200032sp4,if=ide,index=0 -drive file=/mnt/MD_isos/Windows32/pl_win2000_pro_win2000_server.iso,if=ide,media=cdrom,index=2 -net nic,macaddr=00:16:3e:44:b2:45,vlan=0,model=virtio -net tap,fd=44,script=,vlan=0,ifname=vnet9 On the guest was installed virtio net driver. On the same host I running several other guests systems including Win2003 Server sp2 32bit, WinXP sp2 32bit and Linux Gentoo 64bit without problem like this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2314737&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
