He may have set this up before the first time he booted Xen. I've used Xen and Precise before, without setting dom0_mem, and I haven't run into this problem myself. I can't recall the last 3.2 kernel I used that worked, though. Bob, I suppose we could just install the last 10 or so and see if we can track down the fail.
I'm a collegue of "the collegue" that Bob mentioned. I just logged into "the collegue's" computer, and he's got dom0_mem=2048M in his Xen commandline:
GRUB_CMDLINE_ XEN_DEFAULT= "dom0_mem= 2048M console=com1 com1=38400,8n1 loglvl=all guest_loglvl=all"
He may have set this up before the first time he booted Xen. I've used Xen and Precise before, without setting dom0_mem, and I haven't run into this problem myself. I can't recall the last 3.2 kernel I used that worked, though. Bob, I suppose we could just install the last 10 or so and see if we can track down the fail.