Could you attach the kernel message info dumped by dmesg after breaking windows ? Actually, I am not aware of this. Xiantao -----Original Message----- From: Jes Sorensen [mailto:jes@xxxxxxx] Sent: Saturday, March 28, 2009 12:20 AM To: Zhang, Xiantao Cc: kvm-ia64@xxxxxxxxxxxxxxx Subject: Re: windows patch seems to have broken allocation on demand patches Zhang, Xiantao wrote: > Which patches ? > Xiantao This is the one I keep applying - but modified to be against the latest kernel, which is broken. You came up with this due to the long startup time for KVM when booting large guests, like 64GB+ etc. Cheers, Jes > -----Original Message----- > From: Jes Sorensen [mailto:jes@xxxxxxx] > Sent: Saturday, March 28, 2009 12:00 AM > To: Zhang, Xiantao > Cc: kvm-ia64@xxxxxxxxxxxxxxx > Subject: windows patch seems to have broken allocation on demand patches > > Hi Xiantao, > > The recent changes adding support for windows to KVM/ia64, seems to have > broken the allocation on demand patches, needed to boot with large > memory support. > > Is there any chance you have an update version of these patches? > > Cheers, > Jes -- To unsubscribe from this list: send the line "unsubscribe kvm-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html