Re: pciback.hide problems with Xen3.3 on 5.1/amd64

[dukzcry <lomka%gero.in@localhost>]

dukzcry <lomka <at> gero.in> writes:

> I'm using xentools41 and patched it for pciback support. 
> All is you need is following diff: 
> https://raw.github.com/druga/crap/master/netbsd/xen/xentools41/patch-Makefile

My apologies for double-mailing and incomplete answer. I'll try again :-)


Jean-Yves Migeon <jeanyves.migeon <at> free.fr> writes:

> Woopsie, correct, currently, it will not only work with Xen 3.0.
> Downgrading should be fine, just pkg_delete xentools33 and xenkernel33,
> make install both xentools3 and xenkernel3.

I'm using xentools41 and patched it for pciback support.
All is you need is following diff:
https://raw.github.com/druga/crap/master/netbsd/xen/xentools41/patch-Makefile .
And note that:

A. Priebe <netapr <at> gmx.net> writes:
> holmes# xm create -c vm1.cfg
> Using config file "/usr/pkg/etc/xen/vm1.cfg".
> Error: pci: failed to locate device and parse it's resources - unsupported
operand type(s) for +:
> 'NoneType' and 'str'

Python-powered xm frontend will fail at pciback parameter parsing, so you're 
forced to use xl C-based frontend for domain creating/destroying when you 
have active 'pciback' option in the config of your domain. I don't see any 
issue here, since xm is already considered obsolete.

And it 'll not work for PV-domain, afair. I've tested only on HVM-domain 
using system with both VT-x and VT-d features working.