[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AW: [Xen-users] "maxmem" without "memory" in hvm-domU-config causesdom0 to reboot

  • To: "James Dingwall" <james.dingwall@xxxxxxxxxx>
  • From: "Ronney Meier Rorotec GmbH" <rm.meier@xxxxxxxxxx>
  • Date: Wed, 8 Jun 2011 11:44:31 +0200
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 08 Jun 2011 02:47:08 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcwlO9Hk36z/AwdkQFer7dvmgWVu/AAgEEjQAAEg1eA=
  • Thread-topic: [Xen-users] "maxmem" without "memory" in hvm-domU-config causes dom0 to reboot

> > Anyway I don't know if this is a known (or unknown?) bug (I couldn't

> > find any information about it) or if there's something wrong with my

> > system, so I'm just asking here if anybody ever had similar
> I think that this is the known (and expected) behaviour and I had 
> similar issues when I set memory < max_mem for an HVM.  My 
> understanding is that Xen is ballooning RAM for the HVM but the HVM 
> doesn't know how to correctly accept it as there is no balloon driver.

> At some point the HVM then tries to address RAM between memory and 
> max_mem but as it is not properly configured it crashes.
The problem is that it not only crashes (in my case reboots) the domU
(guest) but the dom0 (host) I don't think that a misconfigured guest
should be able to crash the whole host system.


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.