On Fri, Mar 03, 2017 at 05:30:30PM +0100, Stephan Marwedel wrote: > Hi Steve, > > thank you for the information. > > Your approach probably won't work in my case, as the license served by > flexlm software is tied to MAC address and hostname. If I install it in the > TemplateVM the license will be created with MAC address and hostname of that > TemplateVM. If I later start the software from the AppVM like you suggested, > it will provide a different MAC address and hostname which will invalidate > the license. So there seems to be no alternative other than to create a > standalone VM and install the commercial package in that VM. > > Regards, > Stephan > > On 02/28/2017 04:15 PM, Steve Coleman wrote: > >On 02/25/2017 04:07 PM, Stephan Marwedel wrote: > >>Hi, > >>I use a commercial simulation environment running on Debian. I installed > >>the software in the Debian TemplateVM and it is running fine. However, > >>when starting an AppVM based on that template I cannot use the > >>simulation software because of the flexlm license manager failing. This > >>is most likely caused by the AppVM getting both a hostname and MAC > >>address being different from those of the corresponding TemplateVM. > >> > >>What options do I have, if any, to work with such a commercial software > >>in an AppVM, as I don't want to work in the TemplateVM? > >> > > > >What I have done is install the COTS software base in the template VM. I > >generally choose /opt for COTS products to keep them separate. > > > >Then I install a service to start the license manager in the one client > >VM and create a desktop file pointing to that installed application > >location. Install the desktop file in the template > >/usr/share/applications but assign it in the start menu of just that one > >VM. Look at qvm-service for how to assign the license manager service to > >just that one VM instance. > > > >Any VM may see the software on disk, but as long as you don't actually > >run from the software template or other VMs then you should be good with > >the license server seeing only the one install instance. > > > >Things can get a bit trickier if the service/software demands to be able > >to write to the system area of the template provided ro file system. > >Then you may need some fixups performed prior to starting the license > >service. > > > >Other options might be to install in /usr/local in the client VM itself, > t> or even in your home directory if that is possible. The service is > >likely required as before unless you write a script to launch the > >license manager, wait for it, and then launch the application when the > >license manager is ready. > > > >My worst case situation would be a standalone VM, but I haven't found > >anything quite that stubborn just yet. > > > >Steve > >
Stephen, You can use macchanger to change your MAC address to match the flexlm expectation. Similarly, changing the hostname is straightforward, Depending on what the software is, you may be able to choose the installation point: if so, you can install in a TemplateBasedVM in /home or /usr/local, rather than in a Template. I did have one issue where I was able to show the vendor that the license issued with appropriate MAC/hostname/user details didn't work on the qube. They provided me with effectively an open license, so it's definitely worth talking to them if you have issues. You haven't said what the software is - knowing that may help. unman -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20170304150558.GA8838%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
