From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Manschwetus Subject: virsh dumpxml didn't reflect viridian=1 Date: Sat, 10 Oct 2009 17:40:03 +0200 Message-ID: <4AD0AAD3.6000201@gmx.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0695187731==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Xen discuss Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org This is a cryptographically signed message in MIME format. --===============0695187731== Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms060509080603010308050608" This is a cryptographically signed message in MIME format. --------------ms060509080603010308050608 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Just the output of one of the viridian enabled windows hvm machines: Florian virsh dumpxml titan titan cedb6201-82d6-3c96-4da3-e0bfad6a7501 2097152 2097152 2 hvm /usr/lib/xen/boot/hvmloader destroy restart restart /usr/lib/xen/bin/qemu-dm