xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Teo En Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"David TECHER" <davidtecher@yahoo.fr>,
	"Casey DeLorme" <cdelorme@gmail.com>,
	"Ian Campbell" <Ian.Campbell@citrix.com>,
	"Teo En Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com>,
	"Pasi Kärkkäinen" <pasik@iki.fi>
Subject: Help Needed with Xen VGA Passthrough with Xen 4.2-unstable Changeset 25070 in Ubuntu 11.10 amd64 Dom0
Date: Wed, 21 Mar 2012 15:45:44 +0800	[thread overview]
Message-ID: <4F698728.4080609@gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4006 bytes --]

Dear Xen developers, David Techer and Others,

I am yet unable to passthrough my VGA adapter NVIDIA Geforce 8400 GS to 
Windows XP Home Edition SP3 HVM domU. When Windows XP HVM is started 
with XL, the monitor is _BLANK_. I am able to vnc into into the VNC 
server for Win XP HVM domU 192.168.1.2:5901, where the IP address is 
that of my dom0 eth0 interface. But doing a CTRL-ALT-1 and CTRL-ALT-2 on 
the QEMU console only show the words serial and parallel console.

Please refer to the attached PDF file Xen VGA Passthrough - Version 
1.0.pdf which I have written. All the patching, building, installation, 
configuration files, and error logs in /var/log/xen are provided in the 
PDF file which I have written. I hope the PDF file can get through to 
xen-devel mailing list. It is only 88 kB.

Please do not say I have not submitted any meaningful and required 
information required for troubleshooting. Please read my attached PDF 
document. It is only 9 pages.

I want to ask whether the case of the following HEXADECIMAL values matter.

/* reserve MMIO BARs of gfx for 1:1 mapping */
DWordMemory(
ResourceProducer, PosDecode, MinFixed, MaxFixed,
Cacheable, ReadWrite,
0x00000000,
0xD2000000,
0xD2FFFFFF,
0x00000000,
0x01000000)

DWordMemory(
ResourceProducer, PosDecode, MinFixed, MaxFixed,
NonCacheable, ReadWrite,
0x00000000,
0xC0000000,
0xCFFFFFFF,
0x00000000,
0x10000000)

DWordMemory(
ResourceProducer, PosDecode, MinFixed, MaxFixed,
Cacheable, ReadWrite,
0x00000000,
0xD0000000,
0xD1FFFFFF,
0x00000000,
0x02000000)


Does it matter if all the hex values are in lower case?

Next,

*qemu-dm-WindowsXPHomeEditionSP3.log
*

domid: 1

Strip off blktap sub-type prefix to 
/var/lib/libvirt/images/Windows-XP-Home-Edition.img (drv 'aio')

Using file /var/lib/libvirt/images/Windows-XP-Home-Edition.img in 
read-write mode

Watching /local/domain/0/device-model/1/logdirty/cmd

Watching /local/domain/0/device-model/1/command

Watching /local/domain/1/cpu

qemu_map_cache_init nr_buckets = 10000 size 4194304

shared page at pfn feffd

buffered io page at pfn feffb

Guest uuid = a417a52a-68e4-48a1-89cc-3216184b8ed3

Register xen platform.

Done register platform.

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw 
state.

xs_read(/local/domain/0/device-model/1/xen_extended_power_mgmt): read error

Log-dirty: no command yet.

I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

vcpu-set: watch node error.

xs_read(/local/domain/1/log-throttling): read error

qemu: ignoring not-understood drive `/local/domain/1/log-throttling'

medium change watch on `/local/domain/1/log-throttling' - unknown 
device, ignored

dm-command: hot insert pass-through pci dev

register_real_device: Assigning real physical device 01:00.0 ...

pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: 
No such file or directory: 0x1:0x0.0x0

pt_register_regions: IO region registered (size=0x01000000 
base_addr=0xd2000000)

pt_register_regions: IO region registered (size=0x10000000 
base_addr=0xc000000c)

pt_register_regions: IO region registered (size=0x02000000 
base_addr=0xd000000c)

pt_register_regions: IO region registered (size=0x00000080 
base_addr=0x0000d001)

pt_register_regions: Expansion ROM registered (size=0x00080000 
base_addr=0xd3000002)

setup_vga_pt: vga bios checksum is adjusted!

pt_msi_setup: msi mapped with pirq 37

pci_intx: intx=1

register_real_device: Real physical device 01:00.0 registered successfuly!

IRQ type = MSI-INTx

pt_bar_reg_read: first read BARs of gfx

pt_iomem_map: e_phys=d2000000 maddr=d2000000 type=0 len=16777216 index=0 
first_map=1

pt_bar_reg_read: first read BARs of gfx

pt_iomem_map: e_phys=c0000000 maddr=c0000000 type=8 len=268435456 
index=1 first_map=1



Please let me know whether I have missed out on any critical steps.



Thank you very much for your kind assistance.

Yours sincerely,

Teo En Ming (Zhang Enming)



[-- Attachment #1.2: Type: text/html, Size: 6067 bytes --]

[-- Attachment #2: Xen VGA Passthrough - Version 1.0.pdf --]
[-- Type: application/pdf, Size: 87964 bytes --]

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

                 reply	other threads:[~2012-03-21  7:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F698728.4080609@gmail.com \
    --to=singapore.mr.teo.en.ming@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=cdelorme@gmail.com \
    --cc=davidtecher@yahoo.fr \
    --cc=pasik@iki.fi \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).