Reversing the problem, let's say I'm a vendor who (boo!) licenses software on a per-cpu basis. How would I prevent a Xen user from taking a one CPU license, and replicating it to 8 different DomU, single CPU, instances, all running off of the same dongle, on an 8 core machine? I'd probably bind the dongle to a specific CPU core in some ways, but it would have to be something that Dom0 (as well as the other DomU instances) was "blind" to, so the dongle wouldn't know that another CPU was talking to it, or even knew existed. Oh, and that Xen instance would only be able to run on a specific core.
Any other ideas? On Tue, Jun 23, 2009 at 4:45 PM, Joe Pruett <[email protected]> wrote: > > those dongle usually need pretty low level access to the parallel > > controller to do their magic. i don't know if xen can give that level of > > controller to a guest or not. i've seen some discussion about giving > some > > pci access to guests, so maybe something like this is doable. newer usb > > dongles are probably easier for this setup, but i doubt your app (or > > win2k) would be able to use that. > > a quick google seems to indicate that if you can get a pci based parallel > port that win2k will talk to, you should be able to allow a xen guest to > have control over that pci slot. > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
