From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joanna Rutkowska Subject: Re: Handling of out of memory conditions Date: Fri, 22 Jun 2012 15:24:24 +0200 Message-ID: <4FE47208.7040207@invisiblethingslab.com> References: <4FE46366.8010104@invisiblethingslab.com> <4FE46486.8020502@invisiblethingslab.com> <4FE4835D020000780008B6B3@nat28.tlf.novell.com> <4FE46ABE.9010104@invisiblethingslab.com> <4FE48921020000780008B6D0@nat28.tlf.novell.com> <4FE46F0B.7080601@invisiblethingslab.com> <4FE48D70020000780008B6EB@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1876564328121686516==" Return-path: In-Reply-To: <4FE48D70020000780008B6EB@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Konrad Rzeszutek Wilk , Marek Marczykowski , xen-devel List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1876564328121686516== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFF57E6A938A00826B3874463" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFF57E6A938A00826B3874463 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 06/22/12 15:21, Jan Beulich wrote: >>>> On 22.06.12 at 15:11, Joanna Rutkowska wrote: >> > How about having the guest kernel (e.g. every time it is about to BU= G()) >> > write the cause of the Xen-related runtime errors (such as out of me= mory >> > conditions) to some predefined xenstore key, which would allow the >> > management tools/whatever other software to retrieve that easily and= >> > display a meaningful message to the user? Hm... access to the xensto= re >> > might not be easy at the early VM boot stage -- so perhaps writing i= t >> > into some predefined shared page, that could be easily read by the >> > toolstack? > That's the console shared page, isn't it? Yeah, but parsing and interpreting the console output is problematic -- e.g. how should an automatic tool know from the oops message I quoted in my first message, that the reason for not starting the VM was just an out of memory? I'm thinking about some simple form of Xen-related runtime error reporting (this would be mostly out of memory), that would be easily parse'able by scripts. Again, the goal is display a simple error message to the user, explaining why his or her VM doesn't start. joanna. --------------enigFF57E6A938A00826B3874463 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJP5HIIAAoJEDaIqHeRBUM073MIANVQrrXYzljrN5NXHKy8Cx8d DvWdUejSTxSe3YtirluCLa5ZDhknNtUahFJAhc7BSXESxQR1WnN0JtJnmzI5ttx/ h9jbleIqx/vZWC3MSasGuBGgEMGz515CPqKpHgtE72Pykefp/Bdqqya02hMUNcnV OAsQRs5XzzSQbXite7rD6aGI76EgVZ2fBLRBqRIHyNtdRxsMVFfp7OjDBPxkQ/Pe uhnkcqZcinHrfinJv0pNd+AtjIivVrpVIaSo1MR70h8YGhHBbLqu0krxb6WJvh8w Cc9VQ8pZp5Qd6Dm5TZxfNhwylatR2LUL8G2Rw4pkrIZamkq7Q8TbSphACC9ZkOU= =732p -----END PGP SIGNATURE----- --------------enigFF57E6A938A00826B3874463-- --===============1876564328121686516== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============1876564328121686516==--