On Wed, Mar 26, 2008 at 02:25:11PM +0800, Yunfeng Zhao wrote:
2. booting smp windows guests has 30% chance of hang
https://sourceforge.net/tracker/?func=detailatid=893831aid=1910923group_id=180599
Does it hang or bluescreen? What if you disable the FlexPriority
optimization?
On Wed, Mar 12, 2008 at 11:05:21AM +0200, Dor Laor wrote:
Can you try the following patch that disables flex priority:
FWIW, Your MUA ate the patch.
kvm: vmx: for 4.0 disable Flex-Priority and always use Avi's tpr
optimization
TPR patching doesn't work for SMP which is what he reported.
On Mon, Mar 10, 2008 at 05:27:32PM +0800, Yunfeng Zhao wrote:
One new issue:
1. booting smp windows guests has 30% chance of hang
https://sourceforge.net/tracker/?func=detailatid=893831aid=1910923group_id=180599
PlatformWoodcrest
CPU 4
Memory size
On Thu, Feb 28, 2008 at 09:40:00AM +0100, Tomas Rusnak wrote:
I test virtio block device. I can boot from vda as root partition, but
if I want to install lilo into boot sector, lilo give me this error:
Fatal: Linux experimental device 0x04x needs to be defined.
Check 'man lilo.conf' under
On Thu, Feb 28, 2008 at 10:11:30AM +0100, Tomas Rusnak wrote:
Check 'man lilo.conf' under 'disk=' and 'max-partitions='
Thank you for your quick answer, but this doesn't help. After i run
lilo, it give me the same error message.
did you try adding 'max-partitions=16' or similar?
On Thu, Feb 28, 2008 at 10:25:49AM +0100, Tomas Rusnak wrote:
But max-partitions=16 give you bad value.
I suggested 16 because that's what the called to alloc_disk in the
virtio block driver is using. I'm not sure why lilo dislikes that
value.
Now I can boot it correctly. Thank you very much
On Fri, Feb 22, 2008 at 11:12:42AM +0100, Soren Hansen wrote:
vmware_vga.c uses functions in vga.c to do some things. They
need to agree on which parts of their state struct is common
and which aren't, otherwise they'll overwrite parts of each
other's state. This patch makes it so.
I tried
On Thu, Feb 21, 2008 at 10:16:27AM +0100, Alexander Graf wrote:
On Feb 21, 2008, at 10:05 AM, Avi Kivity wrote:
I guess it needs the same treatment as cirrus and stdvga (register the
framebuffer with kvm as a memory slot).
So my guess would be, that Linux targets with vmware vga should be
