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: "Stefano Stabellini" <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Disabling cirrus-vga
From: "billy lau" <billylau@xxxxxxxxx>
Date: Fri, 12 Dec 2008 19:58:48 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Jun Koi <junkoi2004@xxxxxxxxx>
Delivery-date: Fri, 12 Dec 2008 16:59:24 -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=knNWOBVMsO10bePAqZ6UQaGpuqxoi2JuuLX4JjpBoW8=; b=oLHCAMqXAL2ZlQe4D6Q2PF7b1POF7Rc5YeJME9QdimQb3CNVRdyFtsd83/+C+aEgHY hVqSG49GhHhjVKnmgjOwAbTdiDkINwf5b5diAdNZf3aVj4C9X/oZi0ovtm61Ihcw/p22 gxLfIAOCCG/kxmbeeuQWCthVegnA9KldFGPwE=
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=ttSYCQ3nLCEo0JRZMLho9QCt3vIR35rCgrKYJCVvrE+WwiFXl9IS9v60d+ZIB7zQvE OPAJ6IuHdLPIEFLshVqb00OfTczB+0K8RqU42kWb8iWYiRoq4hNtRVQL9VlCmpvlD/2Y T+TXYEWY53IsV9Ir2OvJwMq54aPjfmy8isNsM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <6b5ba5140812120446q7afb3244of5e705a1e6e7b274@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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.
qemu_map_cache_init nr_buckets = 10000 size 3145728
shared page at pfn 3fffe
buffered io page at pfn 3fffc
Time offset set 0
register_real_device: Assigning real physical device 02:00.0 ...
pt_register_regions: IO region registered (size=0x01000000 base_addr=0xfa000000)
pt_register_regions: IO region registered (size=0x10000000 base_addr=0xd0000000)
pt_register_regions: IO region registered (size=0x02000000 base_addr=0xf8000000)
pt_register_regions: IO region registered (size=0x00000080 base_addr=0x0000dc80)
pt_register_regions: Expansion ROM registered (size=0x00020000 base_addr=0xfbd00000)
register_real_device: Real physical device 02:00.0 registered successfuly!
Register xen platform.
Done register platform.
xs_read(/local/domain/0/device-model/1/xen_extended_power_mgmt): read error
medium change watch on `hdc' (index: 1): /home/billy/windowsxp/winxp_sp3.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
pt_iomem_map: e_phys=f0000000 maddr=f8000000 type=0 len=33554432 index=3 first_map=1
pt_iomem_map: e_phys=f3000000 maddr=fa000000 type=0 len=16777216 index=0 first_map=1
pt_iomem_map: e_phys=f4000000 maddr=fbd00000 type=8 len=131072 index=6 first_map=1
pt_ioport_map: e_phys=c200 pio_base=dc80 len=128 index=5 first_map=1

But I cannot connect to my guess (I have been using vncviewer to connect to it). And it seems that the guest domain just stops, with no status. But there is no error in the log. Any advice?

thanks,
- billy


On Fri, Dec 12, 2008 at 7:46 AM, billy lau <billylau@xxxxxxxxx> wrote:


On Fri, Dec 12, 2008 at 5:33 AM, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> wrote:
billy lau wrote:

>
>
> On Thu, Dec 11, 2008 at 8:09 PM, Jun Koi <junkoi2004@xxxxxxxxx
> <mailto:junkoi2004@xxxxxxxxx>> wrote:
>
>     On Fri, Dec 12, 2008 at 9:49 AM, billy lau <billylau@xxxxxxxxx
>     <mailto:billylau@xxxxxxxxx>> wrote:
>     > Hi xen developers,
>     >
>     > Does any of you know how to disable the cirrus-vga emulation for
>     hvm in xen?
>     > I have been trying to disable that from the source codes, but even
>     with
>     > that, I still see a VGA controller when I boot up my guest domain. In
>     > particular, I would like to do this because I am passing through a
>     graphics
>     > card to my guest domain using direct pass through.
>
>     Sorry that I dont understand your motivation. If your card is
>     passthrough, the guest would load the appropriate driver for that. So
>     why do you care about the cirrus-vga driver?
>
>
> This is because, even after installing the appropriate driver, there is
> a conflict of device. Even after I disabled the cirrus driver, the
> actual driver was reported to be "unable to access resources". Does that
> sound reasonable then?


I think at the moment there is no way to do it from the command line.
You have to comment out any call to pci_cirrus_vga_init,
isa_cirrus_vga_init, pci_vmsvga_init, pci_vga_init and isa_vga_init in
hw/pc.c (lines 939-962).

You may also want to disable loadind the vgabios, also in hw/pc.c
(load_image_targphys).

Alright, I will give that a try, and get back to you guys again. Thanks for the input.

- billy


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