>>> On 23.09.11 at 15:57, "Kulkarni, Shanti" <[email protected]> wrote: > On Fri, Sep 23, 2011 at 7:24 AM, Jan Beulich <[email protected]> wrote: >>>>> On 22.09.11 at 17:44, "Kulkarni, Shanti" <[email protected]> wrote: >>> It works properly using the last OS 11.2 2.6.31 kernel on top of 11.4, >>> so I opened a bug >>> (https://bugzilla.novell.com/show_bug.cgi?id=719858). Thanks for your >>> help. >> >> Seems like I was wrong with the assumption that this would be a >> problem with the native kernel too. There was a resource handling >> change in 2.6.37 that isn't compatible with the Xen kernel's memory >> handling, which precludes resource re-assignment on any system >> with (roughly) memory extending past the 4G boundary. >> >> Jan >> > > My system has 8G, so that would explain it. Thank you. > > I assume I'll have to remove memory
Not physically of course. Just using e.g. dom0_mem=2G on the Xen command should be usable as a workaround. > or keep my kernel < 2.6.37 for the > time being, but do you know if it's likely that this situation will > change with the 3.0-final kernel now that Xen's been merged into it? The upstream 3.x kernels don't have this problem, as they adjust the memory layout as passed from Xen to match the raw machine's E820 table. Since the way you ask it makes me think that you think that we would use that upstream Xen implementation right away: That would be a wrong assumption, as what is upstream is still lacking quite a few features we want to provide. Jan -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
