Re: Help Needed from Xen Developers: Nasty Yellow Triangle with Exclamation Mark and Error Code 43 in Device Manager in Windows 8 HVM domU

Re: Help Needed from Xen Developers: Nasty Yellow Triangle with Exclamation Mark and Error Code 43 in Device Manager in Windows 8 HVM domU

[Teo En Ming (Zhang Enming)]

On 05/10/2012 16:05, Dariusz Krempa wrote:
> I'm afraid it is not possible to do this in this configuration. Nvidia 
> does not support virtualization for geforce cards and their drivers 
> have problems in windows 7, windows 8, vista, server 2008 etc. We can 
> easy setup virtual machine on windows xp but only with drivers less 
> than 280.xx and I did some trick (with a huge amount of luck) that I 
> setup windows 7, but first drivers for windows 8 are 295.73. I think 
> we will need to wait for different patch for xen to do this.
> If You will study device manager under windows 7 or 8 with view set on 
>  then You can see that windows do not recognize properly this memory 
> range:
> mem 0xf4000000-0xf5ffffff
> and this is the only range which isn't set in xen patch. Of course I 
> will try to work with windows 8 for a while but like I said, I'm 
> afraid this will not work in this moment.

Dear Dariusz Krempa,

Even with Windows XP Home Edition SP3 HVM domU, I also get the nasty 
yellow triangle with exclamation mark and error code 43.

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore

Re: Help Needed from Xen Developers: Nasty Yellow Triangle with Exclamation Mark and Error Code 43 in Device Manager in Windows 8 HVM domU

[Teo En Ming (Zhang Enming)]

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

On 06/10/2012 00:09, Teo En Ming (Zhang Enming) wrote:
> On 05/10/2012 16:05, Dariusz Krempa wrote:
>> I'm afraid it is not possible to do this in this configuration. 
>> Nvidia does not support virtualization for geforce cards and their 
>> drivers have problems in windows 7, windows 8, vista, server 2008 
>> etc. We can easy setup virtual machine on windows xp but only with 
>> drivers less than 280.xx and I did some trick (with a huge amount of 
>> luck) that I setup windows 7, but first drivers for windows 8 are 
>> 295.73. I think we will need to wait for different patch for xen to 
>> do this.
>> If You will study device manager under windows 7 or 8 with view set 
>> on  then You can see that windows do not recognize properly this 
>> memory range:
>> mem 0xf4000000-0xf5ffffff
>> and this is the only range which isn't set in xen patch. Of course I 
>> will try to work with windows 8 for a while but like I said, I'm 
>> afraid this will not work in this moment.
>
> Dear Dariusz Krempa,
>
> Even with Windows XP Home Edition SP3 HVM domU, I also get the nasty 
> yellow triangle with exclamation mark and error code 43.
>

Dear Dariusz Krempa,

Correction: I have just tried it. Even with Windows XP Home Edition SP3 
HVM domU and NVIDIA driver version 275.33, I still get the nasty yellow 
_circle_ with exclamation mark and error code 10.

I am simply wondering. What is wrong?

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore


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

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

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

Re: Help Needed from Xen Developers: Nasty Yellow Triangle with Exclamation Mark and Error Code 43 in Device Manager in Windows 8 HVM domU

[Teo En Ming (Zhang Enming)]

On 05/10/2012 19:48, Dariusz Krempa wrote:
>
> I just installed windows 8 and like before, which I mentioned on 
> mail-list its possible to install nvidia drivers under windows 8 but:
> - drivers has to be 275.33
> - gpu-z shows that only Direct Computing is available, no physX, no 
> OpenCL, no CUDA
> - windows index is much lower than normal, 7.8 under windows 7 
> standalone and hvm and 7.1 under windows 8 hvm
>
> I don't know if this will work with stub, but with pciback I don't 
> need to do special tricks just install drivers 275.33 for win 7/vista

How did it go with your Windows 8 HVM domU?

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore

Re: Help Needed from Xen Developers: Nasty Yellow Triangle with Exclamation Mark and Error Code 43 in Device Manager in Windows 8 HVM domU

[Teo En Ming (Zhang Enming)]

On 06/10/2012 05:46, Dariusz Krempa wrote:
>
> >
> > Dear Dariusz Krempa,
> >
> > Even with Windows XP Home Edition SP3 HVM domU, I also get the nasty 
> yellow triangle with exclamation mark and error code 43.
> >
> > --
> > Yours sincerely,
> >
> > Mr. Teo En Ming (Zhang Enming)
> > Singapore
> >
> >
> Im just wondering. In last patch is 7 files to patch and in tutorial 
> from march You did was just 6. Maybe You missed that additional file. 
> There should work exact the same makings for gtx560 like before for 4xx. 

Dear Dariusz Krempa,

I have just checked. I can confirm that there are only 6 patch files 
from David Techer's personal website. How did you get 7 patch files? May 
I know whose patch files did you use?

wget 
http://www.davidgis.fr/download/xen-4.2_rev24798_gfx-passthrough-patchs.tar.bz2
tar xfvj xen-4.2_rev24798_gfx-passthrough-patchs.tar.bz2

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore

Re: Help Needed from Xen Developers: Nasty Yellow Triangle with Exclamation Mark and Error Code 43 in Device Manager in Windows 8 HVM domU

[Teo En Ming (Zhang Enming)]

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

On 06/10/2012 10:13, Dariusz Krempa wrote:
>
>
> 2012/10/6 Teo En Ming (Zhang Enming) 
> <singapore.mr.teo.en.ming@gmail.com 
> <mailto:singapore.mr.teo.en.ming@gmail.com>>
>
>     On 06/10/2012 05:46, Dariusz Krempa wrote:
>
>
>         >
>         > Dear Dariusz Krempa,
>         >
>         > Even with Windows XP Home Edition SP3 HVM domU, I also get
>         the nasty yellow triangle with exclamation mark and error code 43.
>         >
>         > --
>         > Yours sincerely,
>         >
>         > Mr. Teo En Ming (Zhang Enming)
>         > Singapore
>         >
>         >
>         Im just wondering. In last patch is 7 files to patch and in
>         tutorial from march You did was just 6. Maybe You missed that
>         additional file. There should work exact the same makings for
>         gtx560 like before for 4xx.
>
>
>     Dear Dariusz Krempa,
>
>     I have just checked. I can confirm that there are only 6 patch
>     files from David Techer's personal website. How did you get 7
>     patch files? May I know whose patch files did you use?
>
>     wget
>     http://www.davidgis.fr/download/xen-4.2_rev24798_gfx-passthrough-patchs.tar.bz2
>     tar xfvj xen-4.2_rev24798_gfx-passthrough-patchs.tar.bz2
>
>
>     -- 
>     Yours sincerely,
>
>     Mr. Teo En Ming (Zhang Enming)
>     Singapore
>
> I am using last patches rev25240
>
> wget 
> http://www.davidgis.fr/download/xen-4.2_rev25240_gfx-passthrough-patchs.tar.bz2 
> <http://www.davidgis.fr/download/xen-4.2_rev24798_gfx-passthrough-patchs.tar.bz2>
> tar xfvj xen-4.2_rev25240_gfx-passthrough-patchs.tar.bz2
You mean there are 7 patch files in this patch set? Thanks! I will go 
and try it out.

By the way, this patch set was not published by David Techer himself. 
The link you have given above was not published on his personal website.

I have also observed one strange phenomenon. When it comes to Xen VGA 
Passthrough, no Xen developers appear to be willing to help. I have 
already provided full information, ie. configuration files and 
troubleshooting logs.

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore


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

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

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

Re: Help Needed from Xen Developers: Nasty Yellow Triangle with Exclamation Mark and Error Code 43 in Device Manager in Windows 8 HVM domU

[Teo En Ming (Zhang Enming)]

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

On 06/10/2012 11:36, Teo En Ming (Zhang Enming) wrote:
> On 06/10/2012 10:13, Dariusz Krempa wrote:
>>
>>
>> 2012/10/6 Teo En Ming (Zhang Enming) 
>> <singapore.mr.teo.en.ming@gmail.com 
>> <mailto:singapore.mr.teo.en.ming@gmail.com>>
>>
>>     On 06/10/2012 05:46, Dariusz Krempa wrote:
>>
>>
>>         >
>>         > Dear Dariusz Krempa,
>>         >
>>         > Even with Windows XP Home Edition SP3 HVM domU, I also get
>>         the nasty yellow triangle with exclamation mark and error
>>         code 43.
>>         >
>>         > --
>>         > Yours sincerely,
>>         >
>>         > Mr. Teo En Ming (Zhang Enming)
>>         > Singapore
>>         >
>>         >
>>         Im just wondering. In last patch is 7 files to patch and in
>>         tutorial from march You did was just 6. Maybe You missed that
>>         additional file. There should work exact the same makings for
>>         gtx560 like before for 4xx.
>>
>>
>>     Dear Dariusz Krempa,
>>
>>     I have just checked. I can confirm that there are only 6 patch
>>     files from David Techer's personal website. How did you get 7
>>     patch files? May I know whose patch files did you use?
>>
>>     wget
>>     http://www.davidgis.fr/download/xen-4.2_rev24798_gfx-passthrough-patchs.tar.bz2
>>     tar xfvj xen-4.2_rev24798_gfx-passthrough-patchs.tar.bz2
>>
>>
>>     -- 
>>     Yours sincerely,
>>
>>     Mr. Teo En Ming (Zhang Enming)
>>     Singapore
>>
>> I am using last patches rev25240
>>
>> wget 
>> http://www.davidgis.fr/download/xen-4.2_rev25240_gfx-passthrough-patchs.tar.bz2 
>> <http://www.davidgis.fr/download/xen-4.2_rev24798_gfx-passthrough-patchs.tar.bz2>
>> tar xfvj xen-4.2_rev25240_gfx-passthrough-patchs.tar.bz2
> You mean there are 7 patch files in this patch set? Thanks! I will go 
> and try it out.
>
> By the way, this patch set was not published by David Techer himself. 
> The link you have given above was not published on his personal website.
>
> I have also observed one strange phenomenon. When it comes to Xen VGA 
> Passthrough, no Xen developers appear to be willing to help. I have 
> already provided full information, ie. configuration files and 
> troubleshooting logs.
>
> -- 
> Yours sincerely,
>
> Mr. Teo En Ming (Zhang Enming)
> Singapore

Dear Dariusz Krempa,

I have used patch set 25240 from David Techer's personal website as you 
have recommended and applied it to Xen 4.2.1-pre. Now I am able to get 
*PARTIAL SUCCESS* with Xen 4.2.1-pre but there is still this nasty 
yellow triangle with exclamation mark and error code 43.

Could you carefully look through my manual/tutorial/guide for me and see 
what is missing from my manual. BUT, using the same 
manual/tutorial/guide that I have written, I was able to get 100% 
success with Frank Lyon's Xen VGA Passthrough server. There is no nasty 
yellow triangle with exclamation mark and error code 43 in Frank Lyon's 
case.

Just what is wrong with my setup?!?!?!

By the way, patch set 25240 is for Xen 4.2-unstable changset 25099 and 
above.

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore


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

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

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

Re: Help Needed from Xen Developers: Nasty Yellow Triangle with Exclamation Mark and Error Code 43 in Device Manager in Windows 8 HVM domU

[Teo En Ming (Zhang Enming)]

On 06/10/2012 13:25, Dariusz Krempa wrote:
>
> >
> > You mean there are 7 patch files in this patch set? Thanks! I will 
> go and try it out.
> >
> > By the way, this patch set was not published by David Techer 
> himself. The link you have given above was not published on his 
> personal website.
> >
> > I have also observed one strange phenomenon. When it comes to Xen 
> VGA Passthrough, no Xen developers appear to be willing to help. I 
> have already provided full information, ie. configuration files and 
> troubleshooting logs.
> >
> > --
> > Yours sincerely,
> >
> > Mr. Teo En Ming (Zhang Enming)
> > Singapore
>
> This patch was published on David's website but it was just short 
> note. It still is link on left side with other shortcuts to last news.
> About devs, they just dont bother about gtx vga passthrough cause its 
> not pro card and with quadro and tesla there is no problem. 

No wonder I have no problems with Frank Lyon's NVIDIA Quadro 6000 at 
all. Complete 100% success.

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore

Re: Help Needed from Xen Developers: Nasty Yellow Triangle with Exclamation Mark and Error Code 43 in Device Manager in Windows 8 HVM domU

[Teo En Ming (Zhang Enming)]

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

On 06/10/2012 13:55, Dariusz Krempa wrote:
>
>
>     Could you carefully look through my manual/tutorial/guide for me
>     and see what is missing from my manual. BUT, using the same
>     manual/tutorial/guide that I have written, I was able to get 100%
>     success with Frank Lyon's Xen VGA Passthrough server. There is no
>     nasty yellow triangle with exclamation mark and error code 43 in
>     Frank Lyon's case.
>
>     Just what is wrong with my setup?!?!?!
>
>
> When I started with Xen and linux about 3 weeks ago I found Yours 
> manuals in pdf. My first steps was simple copy paste. Later I realized 
> that for me not whole manual is needed and in this moment im using:
> - to build kernel points 1-5, but without modified /etc/modules
> -- in this moment Im using kernel 3.6-rc7 instead 3.3-rc7
> -- in config I set all *XEN* for y
> - to build xen from sources (I also copy-pasted at start from Xen 
> manual from You and from David's website):
> -- apt-get install texinfo git-core libglib2.0-dev libyajl-dev 
> build-essential vncviewer bridge-utils mercurial
> -- apt-get build-dep xen
> -- patch rev25240
>
> Also Im using pciback instead stub, cause Im having problems with 
> stub. It report me errors (missing files).
> This is all what I need to start hvm. Now like I said before first I 
> install windows without vga passthrough (its because 1 gfx also with 
> problems with usb drivers under windows). When I have windows ready Im 
> passing pci  with vga to hvm and Im installing nvidia drivers 275.33 
> or 275.50 and when it is done Im setting gfx_passthrough=1 in DomU 
> config.

Isn't it gfx_passthru=1 instead of gfx_passthrough=1? I believe your 
syntax is wrong.

What a joke man! I can only get Frank Lyon's NVIDIA Quadro 6000 VGA 
Passthrough completely 100% working but I cannot get 100% success for my 
own display cards. I have been trying a lot of things but still cannot 
get rid of the yellow triangle with exclamation mark and error code 43. 
Frank Lyon's NVIDIA Quadro 6000 costs S$6000++ and I can't afford that.

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore


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

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

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

Re: Help Needed from Xen Developers: Nasty Yellow Triangle with Exclamation Mark and Error Code 43 in Device Manager in Windows 8 HVM domU

[Teo En Ming (Zhang Enming)]

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

On 06/10/2012 15:23, Dariusz Krempa wrote:
>
>     Isn't it gfx_passthru=1 instead of gfx_passthrough=1? I believe
>     your syntax is wrong.
>
>
> You right. That was misspelling.
>
>
>     What a joke man! I can only get Frank Lyon's NVIDIA Quadro 6000
>     VGA Passthrough completely 100% working but I cannot get 100%
>     success for my own display cards. I have been trying a lot of
>     things but still cannot get rid of the yellow triangle with
>     exclamation mark and error code 43. Frank Lyon's NVIDIA Quadro
>     6000 costs S$6000++ and I can't afford that.
>
>  There can be another problem why You cant pass thru vga. The problem 
> can be with Yours motherboard. You never wrote what chipset You have 
> and, I assume, You don't test Q6000 on Yours MB. I have luck, cause 
> even if nvidia's and Intel's workers claims that chipset H67 don't 
> have implemented passthrough and I don't have any option in bios to 
> turn it on/off, then at least partially passthrough is implemented. If 
> You have possibilities to check this on different MB or put Q6000 into 
> Yours box then You will see if there is problem.
>
>
> If You are willing we can try something. You can install teamviewer on 
> windows DomU and send me invitation or number by email then I will 
> inspect DomU and maybe I can help. We will have possibilities to chat 
> in teamviewer and You will control everything.

Dear Dariusz Krempa,

My motherboard is the Intel DQ45CB. It supports VT-d officially. There 
is a BIOS option to enable/disable VT-d. It was enabled.

By the way, what is teamviewer? Maybe we can chat on IRC?

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore


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

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

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

Help Needed from Xen Developers: Nasty Yellow Triangle with Exclamation Mark and Error Code 43 in Device Manager in Windows 8 HVM domU

[Teo En Ming (Zhang Enming)]

[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]

Dear Xen developers,

I have been able to get 100% success in Xen VGA Passthrough with Frank 
Lyon's NVIDIA Quadro 6000 (there is NO nasty yellow triangle with 
exclamation mark and error code 43 in device manager in Windows 8 HVM domU).

But I have not been able to get 100% success (partial success) in Xen 
VGA Passthrough with my own display cards. I have recently upgraded my 
display card from NVIDIA Geforce 8400 GS to NVIDIA Geforce GTX 560 but 
there is always the nasty yellow triangle with exclamation mark and 
error code 43 associated with my display card in device manager in 
Windows 8 HVM domU.

I have attached troubleshooting logs and configuration files. Please 
help me to troubleshoot and get rid of the nasty yellow triangle with 
exclamation mark and error code 43. I am using Xen 4.2-unstable 
changeset 25099 and Linux kernel 3.5.4 / 3.6.0-rc7.

In both Frank Lyon's and my case, I have followed the installation 
instructions from my own Xen VGA Passthrough tutorial at

http://wiki.xen.org/wiki/Xen_VGA_Passthrough_to_Windows_8_with_Xen_4.2-unstable

I was able to get Frank Lyon's Xen VGA Passthrough to work 100% but not 
mine (partial success) with the same Xen VGA Passthrough tutorial.

Thank you very much for your kind assistance.

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore


[-- Attachment #2: qemu-dm-Windows8.log --]
[-- Type: text/x-log, Size: 14358 bytes --]

domid: 1
Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio')
Using file /etc/xen/images/windows8.img in read-write mode
Strip off blktap sub-type prefix to /home/teo-en-ming/Windows8-ReleasePreview-64bit-English.iso (drv 'aio')
Using file /home/teo-en-ming/Windows8-ReleasePreview-64bit-English.iso in read-only 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 = 9e771120-b3f6-4cd1-9d15-d39fab0d6489
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
medium change watch on `hdc' (index: 1): aio:/home/teo-en-ming/Windows8-ReleasePreview-64bit-English.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
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=0x02000000 base_addr=0xdc000000)
pt_register_regions: IO region registered (size=0x08000000 base_addr=0xd000000c)
pt_register_regions: IO region registered (size=0x04000000 base_addr=0xd800000c)
pt_register_regions: IO region registered (size=0x00000080 base_addr=0x0000d001)
pt_register_regions: Expansion ROM registered (size=0x00080000 base_addr=0xde000002)
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
dm-command: hot insert pass-through pci dev 
register_real_device: Assigning real physical device 00:1b.0 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1b.0x0
pt_register_regions: IO region registered (size=0x00004000 base_addr=0xde220004)
pt_msi_setup: msi mapped with pirq 36
pci_intx: intx=1
register_real_device: Real physical device 00:1b.0 registered successfuly!
IRQ type = MSI-INTx
dm-command: hot insert pass-through pci dev 
register_real_device: Assigning real physical device 00:1a.0 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1a.0x0
pt_register_regions: IO region registered (size=0x00000020 base_addr=0x0000e0c1)
pci_intx: intx=1
register_real_device: Real physical device 00:1a.0 registered successfuly!
IRQ type = INTx
dm-command: hot insert pass-through pci dev 
register_real_device: Assigning real physical device 00:1a.1 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1a.0x1
pt_register_regions: IO region registered (size=0x00000020 base_addr=0x0000e0a1)
pci_intx: intx=2
register_real_device: Real physical device 00:1a.1 registered successfuly!
IRQ type = INTx
dm-command: hot insert pass-through pci dev 
register_real_device: Assigning real physical device 00:1a.2 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1a.0x2
pt_register_regions: IO region registered (size=0x00000020 base_addr=0x0000e081)
pci_intx: intx=3
register_real_device: Real physical device 00:1a.2 registered successfuly!
IRQ type = INTx
dm-command: hot insert pass-through pci dev 
register_real_device: Assigning real physical device 00:1a.7 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1a.0x7
pt_register_regions: IO region registered (size=0x00000400 base_addr=0xde226000)
pci_intx: intx=3
register_real_device: Real physical device 00:1a.7 registered successfuly!
IRQ type = INTx
dm-command: hot insert pass-through pci dev 
register_real_device: Assigning real physical device 00:1d.0 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1d.0x0
pt_register_regions: IO region registered (size=0x00000020 base_addr=0x0000e061)
pci_intx: intx=1
register_real_device: Real physical device 00:1d.0 registered successfuly!
IRQ type = INTx
dm-command: hot insert pass-through pci dev 
register_real_device: Assigning real physical device 00:1d.1 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1d.0x1
pt_register_regions: IO region registered (size=0x00000020 base_addr=0x0000e041)
pci_intx: intx=2
register_real_device: Real physical device 00:1d.1 registered successfuly!
IRQ type = INTx
dm-command: hot insert pass-through pci dev 
register_real_device: Assigning real physical device 00:1d.2 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1d.0x2
pt_register_regions: IO region registered (size=0x00000020 base_addr=0x0000e021)
pci_intx: intx=3
register_real_device: Real physical device 00:1d.2 registered successfuly!
IRQ type = INTx
dm-command: hot insert pass-through pci dev 
register_real_device: Assigning real physical device 00:1d.7 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1d.0x7
pt_register_regions: IO region registered (size=0x00000400 base_addr=0xde225000)
pci_intx: intx=1
register_real_device: Real physical device 00:1d.7 registered successfuly!
IRQ type = INTx
pt_bar_reg_read: first read BARs of gfx
pt_iomem_map: e_phys=dc000000 maddr=dc000000 type=0 len=33554432 index=0 first_map=1
pt_bar_reg_read: first read BARs of gfx
pt_iomem_map: e_phys=d0000000 maddr=d0000000 type=8 len=134217728 index=1 first_map=1
pt_bar_reg_read: first read BARs of gfx
pt_bar_reg_read: first read BARs of gfx
pt_iomem_map: e_phys=d8000000 maddr=d8000000 type=8 len=67108864 index=3 first_map=1
pt_bar_reg_read: first read BARs of gfx
pt_bar_reg_read: first read BARs of gfx
pt_ioport_map: e_phys=d000 pio_base=d000 len=128 index=5 first_map=1
pt_iomem_map: e_phys=f1000000 maddr=de220000 type=0 len=16384 index=0 first_map=1
pt_iomem_map: e_phys=f1004000 maddr=de226000 type=0 len=4096 index=0 first_map=1
pt_iomem_map: e_phys=f1005000 maddr=de225000 type=0 len=4096 index=0 first_map=1
pt_ioport_map: e_phys=c120 pio_base=e0c0 len=32 index=4 first_map=1
pt_ioport_map: e_phys=c140 pio_base=e0a0 len=32 index=4 first_map=1
pt_ioport_map: e_phys=c160 pio_base=e080 len=32 index=4 first_map=1
pt_ioport_map: e_phys=c180 pio_base=e060 len=32 index=4 first_map=1
pt_ioport_map: e_phys=c1a0 pio_base=e040 len=32 index=4 first_map=1
pt_ioport_map: e_phys=c1c0 pio_base=e020 len=32 index=4 first_map=1
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.
pt_pci_read_config: [00:04:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:04:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:04:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:04:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:04:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:04:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:04:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:06:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:06:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:06:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:06:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:06:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:06:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:06:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:0a:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:0a:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:0a:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:0a:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:0a:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:0a:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_pci_read_config: [00:0a:0] Error: Failed to read register with invalid access size alignment. [Offset:0eh][Length:4]
pt_iomem_map: e_phys=ffffffff maddr=dc000000 type=0 len=33554432 index=0 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=d0000000 type=8 len=134217728 index=1 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=d8000000 type=8 len=67108864 index=3 first_map=0
pt_ioport_map: e_phys=ffff pio_base=d000 len=128 index=5 first_map=0
pt_iomem_map: e_phys=dc000000 maddr=dc000000 type=0 len=33554432 index=0 first_map=0
pt_iomem_map: e_phys=d0000000 maddr=d0000000 type=8 len=134217728 index=1 first_map=0
pt_iomem_map: e_phys=d8000000 maddr=d8000000 type=8 len=67108864 index=3 first_map=0
pt_ioport_map: e_phys=d000 pio_base=d000 len=128 index=5 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=de220000 type=0 len=16384 index=0 first_map=0
pt_iomem_map: e_phys=f1000000 maddr=de220000 type=0 len=16384 index=0 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e0c0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c120 pio_base=e0c0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e0a0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c140 pio_base=e0a0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e080 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c160 pio_base=e080 len=32 index=4 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=de226000 type=0 len=4096 index=0 first_map=0
pt_iomem_map: e_phys=f1004000 maddr=de226000 type=0 len=4096 index=0 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e060 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c180 pio_base=e060 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e040 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c1a0 pio_base=e040 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e020 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c1c0 pio_base=e020 len=32 index=4 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=de225000 type=0 len=4096 index=0 first_map=0
pt_iomem_map: e_phys=f1005000 maddr=de225000 type=0 len=4096 index=0 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=dc000000 type=0 len=33554432 index=0 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=d0000000 type=8 len=134217728 index=1 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=d8000000 type=8 len=67108864 index=3 first_map=0
pt_ioport_map: e_phys=ffff pio_base=d000 len=128 index=5 first_map=0
pt_iomem_map: e_phys=dc000000 maddr=dc000000 type=0 len=33554432 index=0 first_map=0
pt_iomem_map: e_phys=d0000000 maddr=d0000000 type=8 len=134217728 index=1 first_map=0
pt_iomem_map: e_phys=d8000000 maddr=d8000000 type=8 len=67108864 index=3 first_map=0
pt_ioport_map: e_phys=d000 pio_base=d000 len=128 index=5 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e0c0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c120 pio_base=e0c0 len=32 index=4 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=de220000 type=0 len=16384 index=0 first_map=0
pt_iomem_map: e_phys=f1000000 maddr=de220000 type=0 len=16384 index=0 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e0a0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c140 pio_base=e0a0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e080 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c160 pio_base=e080 len=32 index=4 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=de226000 type=0 len=4096 index=0 first_map=0
pt_iomem_map: e_phys=f1004000 maddr=de226000 type=0 len=4096 index=0 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e060 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c180 pio_base=e060 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e040 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c1a0 pio_base=e040 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e020 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c1c0 pio_base=e020 len=32 index=4 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=de225000 type=0 len=4096 index=0 first_map=0
pt_iomem_map: e_phys=f1005000 maddr=de225000 type=0 len=4096 index=0 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=de220000 type=0 len=16384 index=0 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=de225000 type=0 len=4096 index=0 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e040 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e020 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e0c0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e080 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e060 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=e0a0 len=32 index=4 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=de226000 type=0 len=4096 index=0 first_map=0

[-- Attachment #3: xl create info --]
[-- Type: text/plain, Size: 3182 bytes --]

+ sudo xl -vvv create /etc/xen/windows8
Parsing config file /etc/xen/windows8
libxl: debug: libxl_device.c:183:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=unknown
libxl: debug: libxl_device.c:137:disk_try_backend: Disk vdev=hda, backend phy unsuitable as phys path not a block device
libxl: debug: libxl_device.c:144:disk_try_backend: Disk vdev=hda, backend tap unsuitable because blktap not available
libxl: debug: libxl_device.c:219:libxl__device_disk_set_backend: Disk vdev=hda, using backend qdisk
libxl: debug: libxl_device.c:183:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=unknown
libxl: debug: libxl_device.c:137:disk_try_backend: Disk vdev=hdc, backend phy unsuitable as phys path not a block device
libxl: debug: libxl_device.c:144:disk_try_backend: Disk vdev=hdc, backend tap unsuitable because blktap not available
libxl: debug: libxl_device.c:219:libxl__device_disk_set_backend: Disk vdev=hdc, using backend qdisk
xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0xad72c
xc: detail: elf_parse_binary: memory: 0x100000 -> 0x1ad72c
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->00000000001ad72c
  TOTAL:         0000000000000000->000000007f800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000003fb
  1GB PAGES: 0x0000000000000000
xc: detail: elf_load_binary: phdr 0 at 0x0x7f3d8d0ec000 -> 0x0x7f3d8d1905bb
libxl: debug: libxl_device.c:183:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=qdisk
libxl: debug: libxl_device.c:183:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=qdisk
libxl: error: libxl_pci.c:761:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:01:00.0
libxl: error: libxl_pci.c:761:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:1a.0
libxl: error: libxl_pci.c:761:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:1a.1
libxl: error: libxl_pci.c:761:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:1a.2
libxl: error: libxl_pci.c:756:libxl__device_pci_reset: write to /sys/bus/pci/devices/0000:00:1a.7/reset returned -1: Invalid argument
libxl: error: libxl_pci.c:761:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:1d.0
libxl: error: libxl_pci.c:761:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:1d.1
libxl: error: libxl_pci.c:761:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:1d.2
libxl: error: libxl_pci.c:756:libxl__device_pci_reset: write to /sys/bus/pci/devices/0000:00:1d.7/reset returned -1: Invalid argument
libxl: debug: libxl_pci.c:223:libxl__create_pci_backend: Creating pci backend
Daemon running with PID 2736
xc: debug: hypercall buffer: total allocations:986 total releases:986
xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
xc: debug: hypercall buffer: cache current size:2
xc: debug: hypercall buffer: cache hits:983 misses:2 toobig:1


[-- Attachment #4: xl-Windows8.log --]
[-- Type: text/x-log, Size: 837 bytes --]

Waiting for domain Windows8 (domid 1) to die [pid 2737]
libxl: debug: libxl_event.c:406:watchfd_callback: watch event: epath=@releaseDomain token=3/0 wpath=@releaseDomain w=0x204c188
libxl: debug: libxl.c:786:domain_death_xswatch_callback: [evg=0x204c8b0:1] from domid=1 nentries=1 rc=1
libxl: debug: libxl.c:797:domain_death_xswatch_callback: [evg=0x204c8b0:1]   got=domaininfos[0] got->domain=1
libxl: debug: libxl.c:824:domain_death_xswatch_callback:  exists shutdown_reported=0 dominf.flags=ffff0002
libxl: debug: libxl.c:790:domain_death_xswatch_callback: [evg=0] all reported
libxl: debug: libxl.c:854:domain_death_xswatch_callback: domain death search done
libxl: debug: libxl_event.c:406:watchfd_callback: watch event: epath=/local/domain/1/device/vbd/5632/eject token=2/1 wpath=/local/domain/1/device/vbd/5632/eject w=0x204ee30

[-- Attachment #5: windows8 --]
[-- Type: text/plain, Size: 1775 bytes --]

# XL domain configuration file for Windows 8 Consumer Preview 64-bit English HVM domU
# Please refer to "man xl.cfg" for further explanations.
# See also docs/misc/xl-network-configuration.markdown and
# docs/misc/xl-disk-configuration.txt
# Written by Teo En Ming (Zhang Enming)
# Email: teo.en.ming@gmail.com
# Mobile Phone: +65-8369-2618
# Country: Singapore
# Date: 18 Mar 2012 Sun
name="Windows8"
# Product Key: DNJXJ-7XBW8-2378T-X22TX-BKG7J
builder="hvm"
vcpus=2
memory=2048
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
disk=[ 'format=raw, vdev=hda, access=rw, target=/etc/xen/images/windows8.img', 'format=raw, vdev=hdc, access=ro, devtype=cdrom, target=/home/teo-en-ming/Windows8-ReleasePreview-64bit-English.iso' ]
#vif=[ 'bridge=virbr0,type=ioemu,model=e1000' ]
#boot=[c|d|n]
#Selects the emulated virtual device to boot from. Options are hard disk (c), cd-rom (d) or network/PXE (n).
#Multiple options can be given and will be attempted in the order they are given. e.g. to boot from cd-rom
#but fallback to the hard disk you can give dc. The default is cd.
boot="dc"
acpi=1
xen_platform_pci=1
viridian=1
#stdvga=1
vnc=1
vnclisten="192.168.1.2"
vncdisplay=0
vncunused=1
vncpasswd=""
sdl=0
usb=1
usbdevice="tablet"
# Enable Xen VGA Passthrough
gfx_passthru=1
# VGA Passthrough Gigabyte Geforce GTX 560 1 GB GDDR5.
pci = [ '01:00.0','00:1b.0','00:1a.0','00:1a.1','00:1a.2','00:1a.7','00:1d.0','00:1d.1','00:1d.2','00:1d.7' ]
# PCI Passthrough Intel HD Audio Controller.
#pci = [ '00:1b.0' ]
# PCI Passthrough all the USB Controllers.
# pci = [ '00:1a.0','00:1a.1','00:1a.2','00:1a.7','00:1d.0','00:1d.1','00:1d.2','00:1d.7' ]

apic=1
xen_extended_power_mgmt=1
pae=1
arch='x86_64'
hpet = 1
hap = 1
monitor=1
pci_power_mgmt = 1
acpi_s3 = 1
acpi_s4 = 1

[-- Attachment #6: start-windows --]
[-- Type: text/plain, Size: 4611 bytes --]

#!/bin/sh
set -x
#
# Starts Shorewall Firewall
sudo service shorewall restart
#
# Loads pci-stub kernel module
sudo modprobe pci-stub
#
# Passthrough Gigabyte Geforce GTX 560 1 GB GDDR5
#
echo "Passthrough Gigabyte Geforce GTX 560 1 GB GDDR5"
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id
sudo chmod o+w /sys/bus/pci/devices/0000:01:00.0/driver/unbind
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind
echo "10de 1201" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:01:00.0" > /sys/bus/pci/devices/0000:01:00.0/driver/unbind
echo "0000:01:00.0" > /sys/bus/pci/drivers/pci-stub/bind
#
# Passthrough Intel HD Audio Controller
#
echo "Passthrough Intel HD Audio Controller."
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id
sudo chmod o+w /sys/bus/pci/devices/0000:00:1b.0/driver/unbind
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind
echo "8086 3a6e" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:00:1b.0" > /sys/bus/pci/devices/0000:00:1b.0/driver/unbind
echo "0000:00:1b.0" > /sys/bus/pci/drivers/pci-stub/bind
#
# Sleep for 10 secs
#
sleep 10
#
# Passthrough USB Controller #1
#
echo "Passthrough USB Controller #1."
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id
sudo chmod o+w /sys/bus/pci/devices/0000:00:1a.0/driver/unbind
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind
echo "8086 3a67" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:00:1a.0" > /sys/bus/pci/devices/0000:00:1a.0/driver/unbind
echo "0000:00:1a.0" > /sys/bus/pci/drivers/pci-stub/bind
#
# Passthrough USB Controller #2
#
echo "Passthrough USB Controller #2."
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id
sudo chmod o+w /sys/bus/pci/devices/0000:00:1a.1/driver/unbind
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind
echo "8086 3a68" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:00:1a.1" > /sys/bus/pci/devices/0000:00:1a.1/driver/unbind
echo "0000:00:1a.1" > /sys/bus/pci/drivers/pci-stub/bind
#
# Passthrough USB Controller #3
#
echo "Passthrough USB Controller #3."
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id
sudo chmod o+w /sys/bus/pci/devices/0000:00:1a.2/driver/unbind
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind
echo "8086 3a69" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:00:1a.2" > /sys/bus/pci/devices/0000:00:1a.2/driver/unbind
echo "0000:00:1a.2" > /sys/bus/pci/drivers/pci-stub/bind
#
# Passthrough USB Controller #4
#
echo "Passthrough USB Controller #4."
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id
sudo chmod o+w /sys/bus/pci/devices/0000:00:1a.7/driver/unbind
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind
echo "8086 3a6c" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:00:1a.7" > /sys/bus/pci/devices/0000:00:1a.7/driver/unbind
echo "0000:00:1a.7" > /sys/bus/pci/drivers/pci-stub/bind
#
# Passthrough USB Controller #5
#
echo "Passthrough USB Controller #5."
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id
sudo chmod o+w /sys/bus/pci/devices/0000:00:1d.0/driver/unbind
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind
echo "8086 3a64" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:00:1d.0" > /sys/bus/pci/devices/0000:00:1d.0/driver/unbind
echo "0000:00:1d.0" > /sys/bus/pci/drivers/pci-stub/bind
#
# Passthrough USB Controller #6
#
echo "Passthrough USB Controller #6."
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id
sudo chmod o+w /sys/bus/pci/devices/0000:00:1d.1/driver/unbind
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind
echo "8086 3a65" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:00:1d.1" > /sys/bus/pci/devices/0000:00:1d.1/driver/unbind
echo "0000:00:1d.1" > /sys/bus/pci/drivers/pci-stub/bind
#
# Passthrough USB Controller #7
#
echo "Passthrough USB Controller #7."
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id
sudo chmod o+w /sys/bus/pci/devices/0000:00:1d.2/driver/unbind
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind
echo "8086 3a66" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:00:1d.2" > /sys/bus/pci/devices/0000:00:1d.2/driver/unbind
echo "0000:00:1d.2" > /sys/bus/pci/drivers/pci-stub/bind
#
# Passthrough USB Controller #8
#
echo "Passthrough USB Controller #8."
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id
sudo chmod o+w /sys/bus/pci/devices/0000:00:1d.7/driver/unbind
sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind
echo "8086 3a6a" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:00:1d.7" > /sys/bus/pci/devices/0000:00:1d.7/driver/unbind
echo "0000:00:1d.7" > /sys/bus/pci/drivers/pci-stub/bind

#
# Wait for 10 seconds
#
sleep 10
#
# Start Windows HVM domU with VGA Passthrough
#
#sudo xl create /etc/xen/WindowsXPHomeEditionSP3
sudo xl -vvv create /etc/xen/windows8

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

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