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] Disabling cirrus-vga

To: "Jun Koi" <junkoi2004@xxxxxxxxx>
Subject: Re: [Xen-devel] Disabling cirrus-vga
From: "billy lau" <billylau@xxxxxxxxx>
Date: Fri, 12 Dec 2008 22:28:26 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Fri, 12 Dec 2008 19:29:10 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=bcx+6IsR4qwsYKHH4/79o0k/7gdYyQSQhp/t0itamTs=; b=FDoDGBXmi723ysUL1o76bZMgbbExVi+6nkDZK4YRphkPEcG5hFoQnAbzJSzJLUcdRy +KUFCaK1NmCyG9oZXYRl/jEAtrEON19B2JilyS3GngOuoJ05XoZNYYDBa2KARtWp4VZX QqTPWaRsc4RiywPsrYgBaob9NIWNBz/dY9N58=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=AYHTV/HrpNmQpEU/XqxKIVZySEd7yHLtrCG0Bw9dDcPVyZf17IBnvyjpTmzvxE+cUu MVW6y71FvIlxwJSxSN7Nc08AFy/ptSm6lRBPpsAVmgGggpdACmps3+mGXvOSK03dkR8o iqvkPoIPnueah6cut4Oxp5za9fTh8Fp/hJXaQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <fdaac4d50812121858t6565c195y6779a38a8cf2940d@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <6b5ba5140812111649r4275a3cu3ece54d56965a733@xxxxxxxxxxxxxx> <fdaac4d50812111709k20ccac3g77c164d1f225880a@xxxxxxxxxxxxxx> <6b5ba5140812112130xcb532e8r5256651d2b37be86@xxxxxxxxxxxxxx> <49423DF4.4060709@xxxxxxxxxxxxx> <6b5ba5140812120446q7afb3244of5e705a1e6e7b274@xxxxxxxxxxxxxx> <6b5ba5140812121658u630657f0i232b6971d46d26f1@xxxxxxxxxxxxxx> <fdaac4d50812121858t6565c195y6779a38a8cf2940d@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


On Fri, Dec 12, 2008 at 9:58 PM, Jun Koi <junkoi2004@xxxxxxxxx> wrote:
On Sat, Dec 13, 2008 at 9:58 AM, billy lau <billylau@xxxxxxxxx> wrote:
> Okay, after commenting those lines out, I noticed that my hvmloader doesn't
> run anymore. What happens is that when I do a xm list, I see this
>
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                     0  2950     4     r-----
> 13.0
> vienna-windows                               1  1024     1     ------
> 1.0
>
> vienna-windows is my hvm guest. Then, looking at the log file,
>
> domid: 1
> qemu: the number of cpus is 1
> config qemu network with xen bridge for  tap1.0 xenbr0
> Watching /local/domain/0/device-model/1/logdirty/next-active
> Watching /local/domain/0/device-model/1/command
> xs_read(): vncpasswd get error.
> /vm/adeb6f31-4656-4a98-032f-14ebeb4b44a9/vncpasswd.

This looks like a bug??

I don't really know. It is there all the time, even before I did the modification.

- billy

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