bat file, pick out the relevant commands, adjust them for linux, and run them. bat is intended for users running Solidworks inside a VirtualBox VM, with Windows as the host OS as well, however if you're like me trying to run Linux as the host OS, you can still open up the.
Windows server 2012 crack activation license#
bat file even if you have a legitimate license (as I would hope you do). The solution I eventually found was to use the hidevm.bat script included in the Solidsquad crack, for tricking Solidworks into thinking it isn't running in a VM. I was seeing the same error discussed above. Xubuntu 16.04 host OS, VirtualBox, Windows 10, and Solidworks 2015.
Windows server 2012 crack activation install#
I just wanted to share my experience here as well, in case others are in a similar situation (trying to install solidworks on a virtualbox VM) # Please notice there is no CPU definition on the top.ĭS Justice mentioned that Qemu (I used virtio in this example) disk mode may be relevant as well. # Please notice there is xmlns definition in tag. Relevant parts of qemu command line parameters: -cpu host,kvm=off -smbios type=0,vendor=LENOVO,version=FBKTB4AUS,date=,release=1.180 -smbios type=1,manufacturer=LENOVO,product=30AH001GPB,version=ThinkStation P300,serial=S4M88119,uuid=cecf333d-6603-e511-97d5-6c0b843f98ba,sku=LENOVO_MT_30AH,family=P300 As Michael Hampton correctly pointed there's -cpu,kvm=off option.I am going to rule out the above mentioned things in next few hours, but I'd like to know if You have any other ideas. MAC address(es) of VM's Ethernet adapter,.What else can they check if I am running my VM in Qemu-KVM besides checking: For some weird reasons (Hyper-V and VMware are supposed to be well tested :) they (developers) of Solidworks 2015 PDM don't want their products to be activated (last 2014 version worked just fine) on Qemu-KVM.Īs you can see it's KVM-based VM with Windows 2012 and Solidworks PDM installation. My client and I want to activate Solidworks Products on KVM virtual machine. Before our eyes a whole new dependency level is being created - affixment to the hypervisor.Īs far as I know searching in a way to find a workaround of this problem is not violation of the Solidworks license and local law in my country. The whole idea of virtualization is to be hardware independent. The question is not around Solidworks actually, so please continue to read.
0 kommentar(er)
