WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Should Qemu monitor be enabled by default

To: "Atsushi SAKAI" <sakaia@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Should Qemu monitor be enabled by default
From: "Christian Limpach" <christian.limpach@xxxxxxxxx>
Date: Wed, 11 Apr 2007 13:10:41 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "You, Yongkang" <yongkang.you@xxxxxxxxx>, Christian Limpach <Christian.Limpach@xxxxxxxxxxxxx>
Delivery-date: Wed, 11 Apr 2007 05:09:31 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BSYDhsxldn1V4lUC4OQfEjzHbOlmQrqoLVyptWl3RlbCAQXX1pxwZFBAOZf+zv3VrH0Tob8Z9Z/eS9tzibI5nj1gfHGz/xEdDgE6ivn4l5cZc+AobAIl5xZQCzGUEEHIceQH5qk4Q5A1me2kOX1vtj/7U9JWvMpXMZbwmNvWkdM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tjnKy5x7j8s7b+t8LNdkTY0dN7zrHa9R3YflyV3BgAOqlRysLdFDwZ4X9pfVX00ZJOYyyFy0B98BxSOcer2oCAzkOdz/hb0WlYq5YPn6PLYrwP2c5ZPzi1iWPW+BD8sj7OCZlMUbvcO5KpieEkX13uyJV28UckKIP1oebi3m0a4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200704111107.l3BB7W6g018316@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <3d8eece20704110224u47cedb24l247fba1632709a9a@xxxxxxxxxxxxxx> <200704111107.l3BB7W6g018316@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 4/11/07, Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx> wrote:
Thank you for consider config file option for domHVM.

I was hoping that you or one of the other people who are so desperate
for getting access to the monitor back was going to create a patch...

Are you try xm block-configure for physical devices(phy:/dev/cdrom)?
(not file(file:))

Works for me.

   christian


Thanks
Atsushi SAKAI

"Christian Limpach" <christian.limpach@xxxxxxxxx> wrote:

> On 4/11/07, Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx> wrote:
> >  Your suggested xm block-configure cannot solve this problem.
> > (to switch the CDROM from guest Domain.)
> >
> > Please explain how to do this.
>
> xm block-configure <vm-name> file:/path/to/the.iso hdd:cdrom r
> where hdd is a cdrom which was configured at boot time (',hdd:cdrom,r'
> in the disk list, doesn't need to be empty, but it can).
>
> > If not, suggested patch should revert it
> > until xm block-configure works.
>
> Making the monitor option configurable from the config file is really
> not that hard, since there's plenty of other options which you can set
> in the config file and which result in options getting added to the
> qemu command line.  The serial option is a good example of how to do
> this.
>
>     christian
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>