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] RE: xen-unstable pci passthrough

Anyway, here is my kernel configuration for 2.6.18.8-xen non-pvops dom 0 kernel on Fedora 11 64-bit host operating system. Please check email attachment.

-- 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering) 
Technical Support Engineer 
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza 
Singapore 529541
Republic of Singapore
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx
Alma Maters: Singapore Polytechnic, National University of Singapore


On 09/03/2009 11:33 PM, Mr. Teo En Ming (Zhang Enming) wrote:
OK, although I have successfully configured, compiled and installed linux-2.6.18.8-xen-dom0 kernel, I cannot use it at all.

When I tried to boot up kernel 2.6.18.8-xen which I have just compiled and installed, I get the "kernel panic not syncing attempted to kill init" message.

The real reason is because I am using ext4 filesystems. ext4 is only supported in kernel 2.6.28 onwards. 2.6.18 only supports ext3. And I can't mount ext4 as ext3. I have tried it. It doesn't work. Since I can't mount ext4 as ext3, I can't do testing with 2.6.18.8 xenified non-pvops dom0 xen kernel already.

Unless I can patch 2.6.18.8-xen to support ext4. I shouldn't have used ext4 in the first place.
-- 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering) 
Technical Support Engineer 
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza 
Singapore 529541
Republic of Singapore
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx
Alma Maters: Singapore Polytechnic, National University of Singapore


On 09/03/2009 10:28 PM, Mr. Teo En Ming (Zhang Enming) wrote:
Hi Tim,

I have downloaded linux-2.6.18.8-xen source code. I am compiling it now. If I still cannot get nVidia Geforce 8400 GS PCI-e x16 secondary gfx to be passed through to Win XP HVM dom U with xen 3.5-unstable with intel gfx passthrough patches applied with xenlinux 2.6.18.8, I will give up the attempt on the secondary gfx.

I will then focus on getting the primary gfx (either onboard or pci-e) to be passed through.

-- 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering) 
Technical Support Engineer 
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza 
Singapore 529541
Republic of Singapore
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx
Alma Maters: Singapore Polytechnic, National University of Singapore


On 09/03/2009 10:19 PM, Tim Moore wrote:

Try and get native WinXP to boot and initialise both cards at the same time .. acid test .. you`ll know if you are wasting your time or not !

 

From: Mr. Teo En Ming (Zhang Enming) [mailto:enming.teo@xxxxxxxxxxxxxxx]
Sent: 03 September 2009 15:12
To: Tim Moore
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] RE: xen-unstable pci passthrough

 

Hi Tim,

I am aware that Magee told me that onboard GMA4500 and PCI-e x16 graphics cannot work simultaneously.

But Weidong told me in earlier postings that he could get secondary gfx to work in the labs, so I am still holding out some hope of getting my secondary gfx to be passed through to windows xp hvm domU.

-- 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering) 
Technical Support Engineer 
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza 
Singapore 529541
Republic of Singapore
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx
Alma Maters: Singapore Polytechnic, National University of Singapore



On 09/03/2009 09:40 PM, Tim Moore wrote:

hi Teo,

 

I believe it is due to your motherboard - In a previous post to xen-devel, as user said to YOU that the chipset does not have enough PCI Lanes to use both Internal IGFX and PCIe card at the same time (simultaneously). Primary (IGFX) will need to be disabled in your BIOS for PCIe card to work, can you get them both enabled in native WinXP?

 

If I were you, I would try and pass through the Primary (IGFX) VGA controller to DomU with the specific changes needed to memory addresses in the v1 patches .. see if that works.

 

Dont think you will have much luck with your secondary PCIe card - (I couldnt get PCIe secondary working either, and my secondary does work in native WinXP)

 

Tim

 

From: Teo En Ming (Zhang Enming) [mailto:enming.teo@xxxxxxxxxxxxxxx]
Sent: 03 September 2009 10:50
To: weidong.han@xxxxxxxxx; Tim Moore
Cc: djmagee@xxxxxxxxxxxx; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough

 

Hi Weidong,

 

Do you have any ideas why gfx passthrough couldn’t work in my case?

 

Regards,
 

Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)

Technical Support Engineer

Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541

Republic of Singapore
Mobile: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx


From: Han, Weidong [mailto:weidong.han@xxxxxxxxx]
Sent: Thursday, September 03, 2009 5:43 PM
To: 'Tim Moore'
Cc: 'enming.teo@xxxxxxxxxxxxxxx'; 'djmagee@xxxxxxxxxxxx'; 'xen-devel@xxxxxxxxxxxxxxxxxxx'
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough

 

Tim,

 

See my comments belew.

 

 


From: Tim Moore [mailto:timothy.moore@xxxxxxxxxxx]
Sent: 2009
93 17:03
To: Han, Weidong
Cc: 'enming.teo@xxxxxxxxxxxxxxx'; djmagee@xxxxxxxxxxxx; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough

Hi Weidong,

 

Thank you for all your hard work ;)

 

I have just successfully passed through my Nvidia Geforce GTX260 as a fully functional card to my WinXP DomU !!!!!

 

My findings so far:

1) Tried with my 9500 GT (Secondary card) which DOES load the driver successfully but NO output on the Monitor (VGA is sized correctly but monitor is OFF)

2) GTX260 (Primary card) (Dom0 boot VGA) starting DomU from remote SSH console, VGA Loads and Display works !!!!

 

In both cases I am using the NVidia binary driver in the WinXP DomU.

 

The 9500GT (Secondary card) passthrough still has issues, the driver loads without the Monitor displaying anything (DPMS?) and if I make ANY changes to the DomU Graphics then the DomU locks up hard. 

 

[Weidong]: I didn't try 9500GT. Seems it needs extra hacks. 

 

In both cases the VGA card only works the FIRST time, I.e. FLR is required to reset the card for re-use, display become corrupt on second boot of DomU. Restart Dom0 and the VGA will work again the first time DomU is started. 

 

[Weidong]:  Yes, it's not reset well. I suspect it's still in graphics mode, so cannot display the boot messages in VGA mode. In my experiments, WinXP guest can still boot into graphics mode, although you cannot see booting progress.

 

Is there anyway we can impletement the d3r, sbr or flr functionality that is in XCI? I would like to see if a sbr will enable to Card to be reset. 

[Weidong]: these reset functions are already in xen-unstable, but no one can really reset gfx. In my feeling, it needs vendor specific method to reset it. 

 

I would also like to debug the issue with Secondary passthrough as it seems that this is nearly there too ...

 

Regards,

Tim

 

 

 

From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@xxxxxxxxxxxx; 'Han, Weidong'; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough

 

Dear Magee,

 

Any luck with the Intel vga passthrough patches to xen 3.5-unstable on Intel DQ45CB with extra PCI-e x16 graphics card? Are you using pvops dom 0 kernels 2.6.30-rc3 and 2.6.31-rc6?

 

Regards,
 

Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)

Technical Support Engineer

Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541

Republic of Singapore
Mobile: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx


From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of djmagee@xxxxxxxxxxxx
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough

 

That was the problem, thank you.  Now I’ll work on testing the gfx-passthrough patches.

 

From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@xxxxxxxxxxxx; 'xen-devel@xxxxxxxxxxxxxxxxxxx'
Subject: [Xen-devel] RE: xen-unstable pci passthrough

 

I suspect you are using old hvm config file. The device_model is changes in config file.

 

in old config file:

# New stuff
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'

 

in new config file:

# Device Model to be used
device_model = 'qemu-dm'

 

Pls check it, and use the latest config file to create guest.

 

Regards,

Weidong

 


From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of djmagee@xxxxxxxxxxxx
Sent: 2009
92 6:40
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xen-unstable pci passthrough

I have not been able to passthrough any PCI devices using the latest xen-unstable.  I have a DQ45CB, and have successfully passed devices to guests using 3.4.1.

 

The latest c/s in my copy of xen-unstable is 20145.  I just started playing around with unstable yesterday, so I can’t tell you if earlier revisions worked.  I’ve tried with various dom0 kernels, the current 2.6.18.8-xen branch, a xenified 2.6.29.6, and a pvops 2.6.31-rc6, and in every case I get the same error.  I’ve tried both putting pci= in the config file, and hot-adding the device using xm pci-attach.  In every case, the xm command (either create or pci-attach) fails with the message “Error: Timed out waiting for device model action”.  The guests in every case are HVM guests, some flavors of Windows, as well as the Knoppix 5.3.1 DVD.

 

The relevant xm dmesg output is:
(XEN) PCI add device 00:1b.0

(XEN) [VT-D]iommu.c:1292:d0 domain_context_unmap:PCIe: bdf = 0:1b.0

(XEN) [VT-D]iommu.c:1178:d0 domain_context_mapping:PCIe: bdf = 0:1b.0

(XEN) [VT-D]io.c:284:d0 VT-d irq bind: m_irq = 37 device = 3 intx = 0

(XEN) [VT-D]iommu.c:1292:d0 domain_context_unmap:PCIe: bdf = 0:1b.0

(XEN) [VT-D]iommu.c:1178:d0 domain_context_mapping:PCIe: bdf = 0:1b.0

 

And the messages from qemu-log:

dm-command: hot insert pass-through pci dev

hot add pci slot -2 exceed.

 

Please let me know what else I need to supply to help resolve this problem.  If I need to enable debugging messages, let me know the best way to do this.

 

Doug Magee

djmagee@xxxxxxxxxxxx

 

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date: 09/01/09 20:03:00

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date: 09/01/09 20:03:00

 

 
_______________________________________________
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



Attachment: config-2.6.18.8-enming.teo
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>