Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am wanting to install OpenShift Origin on my PC running Windows 7.
I am completely new to Linux environments and terminology but wanted to 'look around' the OpenShift product with the hope that I can become familiar with its offerings and features.
So I have started here:
https://www.openshift.com/products/origin
Where the instructions are:
"The easiest way to run OpenShift Origin locally is to download an image suitable for running on a VM. The image will work on KVM , VirtualBox or VMWare . You can also spin up a VirtualBox instance using Vagrant or build your own machine using Puppet".
I have downloaded openshift-origin.latest.tgz and I am assuming the next step is to download and install a 'VM' (something I also have never used)?
I have heard the name VMWare before but when I visit the site there seem to be 15+ different products and I'm not sure which one is required for the above task.
So, is it possible for someone to provide a <ul> of steps required to install and run OpenShift Origin on Windows 7?
A google search for how to install openshift origin on windows 7? does not seem to return any immediately obvious results (the first result links to an article that starts with [obsolete]).
There is a video called 'open shift origin setup' here:
http://youtu.be/rzW3N_C5sIE
But it starts with a file called 'openshift_origin.iso' and not the 'openshift-origin.latest.tgz' that I have downloaded and then it gets into some terminal coding that is completely foreign to me.
Any pointers appreciated.
Edit:
In addition to accepted answer below, as virtual machines may be a bit ominous to newbies here are some screenshots which show the installation of VirtualBox, it was really pretty easy.
For Windows 7, I downloaded VirtualBox 4.2.16 for Windows hosts x86/amd64 from:
https://www.virtualbox.org/wiki/Downloads
and then ran the installer:
Then you will see a few of these type of screens, just click 'Install'.
Unfortunately then when running OpenShift, as per instructions in accepted answer, I got this message:
And I haven't been able to find a workaround to this yet.
But this error shouldn't occur for those who have hardware acceleration enabled.
VirtualBox
VirtualBox is freely available.
Open VirtualBox from the Start Menu - this opens the VirtualBox Manager.
Open the menu File > Import Appliance or press CTRL+I.
Click Open Appliance...
Browse to the folder you downloaded OpenShift Origin to.
Select the .ovf file.
Press Next.
Press Import.
It'll import the file for a while (roughly 2 minutes on my computer) and show up as a Virtual Machine afterwards. You can just click Start and it'll boot up.
VMWare
VMWare Player is free for personal non-commercial use while most other VMWare products are not.
I haven't personally tried this route, but it seems easy enough to just open the .vmx file directly.
Your choices of software to run the ISO (VM image with Fedora) on Windows is VirtualBox or VMWware Workstation. Here's an interesting article that compares the 2:
http://www.infoworld.com/d/virtualization/review-vmware-workstation-9-vs-virtualbox-42-203277
2 unrelated things here...
First, if you do not have a hardware virtualization enabled 64 bit processor (listed as VT-X on Intel chips, and AMD-V on AMD processors), then you cannot host an OpenShift Origin VM, which itself spawns VMs, and thus not only needs the virtualization enabled processor, but needs its VirtualBox VM enabled for virtualization (a checkbox under System/Acceleration in the settings for the VM).
Second, OpenShift Origin relies on multicast DNS, which is not supported on Windows 7, so it won't work.
If you can install Fedora 20 Alpha (I expect Fedora 19 will work, but I haven;t tried it) onto metal, then install VirtualBox and the nss-mdns RPM, that should work.
Been there, done that, got the headache.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 hours ago.
Improve this question
My company is a Lenovo shop and we stood up a WDS server some time ago that boots computers into MDT to deploy images. We've done all sorts of models, from T480s to T490s, T14s, P51, P52, P53, without a single issue. I never did much with drivers in the boot image because it always just seemed to work. Until, that is, we got some new T14 generation 2 and P15 generation 2 models. No matter what I do, they will not successfully boot into MDT.
What happens is we PXE boot these new model machines, they contact the PDX server, load the boot image, I see the background image we set in MDT, and then we immediately get this image, or sometimes, it displays the prompt to start the deployment wizard, and THEN after clicking the start button it displays this error.
On the P15 gen2:
A connection to the deployment share (path) could not be made. The following networking device did not have a driver installed: PCI\VEN_8086&DEV_15F3&SUBSYS_22D817AA&REV_03.
On the T14 gen2:
A connection to the deployment share (path) could not be made. The following networking device did not have a driver installed: PCI\VEN_8086&DEV_15F3&SUBSYS_22D817AA&REV_20.
Once and only once, a T14gen2 went all the way through the deployment task sequence, booted into Windows 10, and THEN displayed the error.
Some googling led me to this page, where I found that the T14gen2 and P15gen2 have specific WinPE 10 driver packs: https://support.lenovo.com/us/en/solutions/ht074984-microsoft-system-center-configuration-manager-sccm-and-microsoft-deployment-toolkit-mdt-package-index
Ok, great. Problem solved. So I downloaded and extracted each package, created a folder in my Out-of-Box driver packs, imported the drivers into there, made a selection profile for that folder, and configured WinPE to grab drivers from there in the Deployment Share properties, then imported that boot image into WinPE.
Then I PXE booted each model and got the same behavior. I'm a little stuck, and wondering if anyone here has run into this before or has any clues on where to go.
Also, originally, I just left the WinPE drivers on 'All,' imported all of the P15g2 and T14g2 drivers into Out-of-Box drivers, and just let the boot image grab what it needed. That broke everything. Computers would boot from the image and then display a message saying that Windows couldn't boot because iaStorAfs.sys couldn't be found. I had to rebuild the entire MDT environment to recover from that.
So right now, just the WinPE drivers for the T14g2 and the P15g2 are being injected into the image, as well as the drivers for the USB-C gen2 dock (https://download.lenovo.com/km/media/attachment/USBCG2.zip). Every other Lenovo model still boots into MDT no problem, and the two models I loaded drivers for don't.
Any insight appreciated! This has been driving me nuts for a while.
I got the same error with Lenovo Thinkpad T14 Gen2(Type 20W0).
PCI\VEN_8086&DEV_15FC&SUBSYS_22C917AA&REV_20
How to reslove this issue, go to Lenovo website https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t14-gen-2-type-20w0-20w1/downloads
and enter your serial number to download the network driver,my Thinkpad NIC was Intel i211-v, so I download it and import to MDT out-of-box WinPE driver,after that I boot my laptop via PXE and no error prompt,about 15 mins complete the Win10 deployment, hope this can resolve your problem.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I'm trying to install WSL2, but getting error above. Virtual Machine platform and Windows subsystem for linux are enabled, also kernel update installed. In BIOS intel virtualization is enabled. How to fix that?
It's worth verifying the machine meets the hardware requirements.
Buried in the WSL troublshooting page under "Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS" the first item is to check Hyper-V System Requirements.
WSL 2 uses a subset of Hyper-V for virtualization, so while you don't need Win 10 Pro, you do still need the hardware to be able to run Hyper-V.
At the time of writing, the docs say Hyper-V requires the following:
64-bit Processor with Second Level Address Translation (SLAT).
CPU support for VM Monitor Mode Extension (VT-x on Intel CPU's).
Minimum of 4 GB memory. As virtual machines share memory with the Hyper-V host, you will need to provide enough memory to handle the expected virtual workload.
A quick way to check requirements: run msinfo32.exe and under System Summary at the very bottom it notes the Hyper-V requirements:
...in my case, I'm out of luck as my processor lacks SLAT.
The issue might be that virtualisation is disabled in you compute. To enable, follow these steps:
Open a PowerShell console as Administrator.
Run the following command:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
Ref: Microsoft's enable Hyper-V Docs
If still had this error, make sure hyper-V in CPU is enabled. For AMD CPUs, it's called SVM (in BIOS).
If you're inside a Virtual Machine, your VM may not be setup to run nested VMs:
Windows Nested Virtualization
I went through the same situation as you.
SVM(VT) is enable and Hyper-V option is enable but Can't use WSL2.
My problem is rebooting problem. windows 10's reboot is not actual reboot.
WSL2 does not complete installed.
Try reboot with press shift key.
The problem was in BIOS. You need to disable Limit CPUID Max to get it work.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
The Problem
Schwab only supports Windows and Mac for its StreetSmart Edge Cloud (SSEC), not Linux. However SSEC is Citrix based, which has a Linux implementation. Unfortunately, it does not work out of the box. How do I get it working on Linux?
Background
One of the most difficult type of software to find on Linux is investment trading software. For years, I had to maintain a Windows machine for this purpose alone.
One of the most sophisticated platform for this is Schwab SmartStreet Edge Cloud version. The only problem is that Schwab only supports Windows and Mac, not Linux. Of course there are other trading platforms, but few can be installed on Linux and I like StreetSmart best.
But isn't Mac a close cousin of Linux? Why can't we seem to get trading software to work on Linux, especially when it is a cloud version of the trading platform? After all, anything that you can do on a Win or Mac browser, you can do on a Linux browser.
So, my question is how can I install a trading platform with all the sophisticated charting and complex trading parameters, such as stop, limit and bracket orders?
Solution
Now, I am going to answer my own question with a solution.
Here is what worked for me. I have been using StreetSmart Edge for over 6 months on my Linux with this solution. Best of all, it does not rely on Wine or dual booting.
Step 1
Download the latest Citrix Workspace app for Linux Web client (x86_64) for 64 bit architecture or (x86) for 32 bit architecture or (ARM HF) for ARM processor machines. I have only tested on the (x86_64), so cannot speak for the others.
Go to the citrix.com and look for the workspace app download page.
Under Available Downloads, choose the type of package you need. I chose Debian Packages. You may need the RPM Packages. Choose the Web Packages (Web Workspace app only) download for your architecture.
On Debian, you are immediately offered a chance to install with GDebi. Click on OK to install.
On RedHat type distros, there are analogous steps.
Or simply install the downloaded file manually, using your OS normal installation procedure for downloaded packages. Be sure you use a method such as GDebi to install needed dependencies as well.
Everything should appear to install correctly without an error message, however, when you try to launch StreetSmart Edge Cloud, you will get the following error message:
SSL error
Contact your help desk with the following information: You have not chosen to trust "DigiCert Global Root G2", the issuer of the server's security certificate (SSL error 61).
Step 2
Create a soft symbolic link to DigiCert_Global_Root_G2.crt which should be in your mozilla ca-certificates.
In my case - Debian 9 - the command to create the symbolic link was as follows:
sudo ln -s /usr/share/ca-certificates/mozilla/DigiCert_Global_Root_G2.crt /opt/Citrix/ICAClient/keystore/cacerts/DigiCert_Global_Root_G2.pem
You may need to search for the mozilla directory to find the correct path for your setup. Also, you may need to search for the Citrix ... cacerts directory to find the correct path for your setup. Replace the ln -s syntax above with the one corrected for your paths.
Step 3
Reboot. I am not certain this is actually necessary, but it can't hurt.
Hurray! You should now be able to use Schwab StreetSmart Edge on your linux.
Now go out and make lots of money and donate it to charity. ... that includes supporting your favorite open source software!!
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
Our customer has about 800+ computers running Windows XP distributed across the country. Each computer can be accessed using TeamViewer. The goal is to replace XP by a Linux distribution remotely.
Does anybody know if this is possible, and where to start?
Thanks!
PXE is your only realistic hope:
Some on-site assistance is needed to press F12 at Bios before Windows XP boot:
A) On PC-A, setup DHCP server that refer DHCP-client to PXE server that download Linux ISO from a web server (of course all three can be a Windows machine in the same LAN segment onsite)
B) reboot PC-B onsite to reboot machine and press F10-F12 to choose Boot-options
C) then choose network-boot (PXE-Boot)
further reading : https://www.vercot.com/~serva/
guide: https://youtu.be/nnxgFpUr1Og?t=39
Note: Make sure you have enabled proxyDHCP and not DHCP Server
I would try with something like these:
Clonezilla, which works by replicating a previously prepared disk image to one or more computers booted inside a network segment
Cobbler, which works like a provisioning server for Linux based machines
Of those options, I have used Clonezilla with success. As long as the prepared base image doesn't change too frequently, the main time consuming tasks would be related with configuring the Clonezilla server and building that seed image.
I did a basic test of Cobbler and it worked fine in my environment, being this a way that would be more apt to deal with requirement changes.
Please also note that both options require some network configuration, like DHCP server settings that work with the PXE protocol.
Also, for your requirement, someone, a human being, would be needed to execute one or more of these tasks:
Properly enable network booting in the BIOS of each of the 800+ machines, unless it has already be done before
Boot the machines to install the new operating system
The network booting option, based on the PXE specification, should be supported by the motherboard of those machines and have higher booting priority than other devices, like CD drives, hard drives, etc.
Another thing to consider for the couple of options I'm suggesting, is how are those 800+ distributed across the country. The more disperse they are, the more cumbersome this task will be. Quite contrary, if there are few places were those machines are located, the more feasible this task will be; for example, by preparing and testing a server, computer or laptop that you then carry to each of those few places and installing the new operating system.
Regarding the option to boot using the public Internet to reach a remote deployment server, I don't know about how that could be done; in fact, for me that would be something quite interesting to learn about. If something like this is possible, another variable to note is the hardware compatibility of the destination machines, because as far as I know, protocols like PXE do some kind of multicast or broadcast in the local network segment and I presume those 800+ machines don't have recent motherboards with advanced firmware that could support more modern boot protocols.
That's all for now.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I've been using linux at university for quite a while, and it seems much more customisable and better for coding.
So I want to switch to linux from windows 7 at home.
What branch of linux should I use? I'm an emacs user if that gives any insight.
Which desktop enviroment should I use? At uni we use KDE, but it's too graphical, often I just click on stuff instead of using the terminal. I want one where it encourages me to use terminal more.
and the biggest question, how do I install it all? Should I put everything on external hard drive and wipe my computer completley?
I primarily program in Java and python.
I would recommend that you first try using Linux off Live CD/DVD. Linux Mint, Ubuntu, etc.
Just download and burn .iso onto blank media and boot your computer off of it. Just play around, check various desktop environments, see if all your hardware work with the specific Linux distribution. This step is very useful to decide which distribution you actually want to install onto your computer, especially the latter since, while it has been improving, the biggest obstacle you may face in configuring your computer to run on Linux is often hardware incompatibility. Just make sure everything that you need to work actually works.
If you have no issues wiping out Windows, Linux installation is pretty straightforward these days. It even takes less time in general than re-installing Windows. I would browse the web for an installation note for your specific computer model to see if anyone has already successfully done so, so that you can just follow. That saves a lot of time.
I use Debian (Wheezy now) and KDE. It's very easy to install and switch desktop environments after installing Linux though, so that shouldn't be any concern.
I suggest creating a virtual machine using VMWare or Virtual Box. As far as the distribution goes, Linux Mint and Ubuntu are pretty user-friendly for first time installations. And for the desktop environment, I suggest XFCE.
A few Google searches will do you good. I think a virtual environment will be much more easier to manage than partitioning a hard-drive.
Well, the installation step, if you use Windows 7, you may want to make a full backup of your hdd - so if things go wrong you will be safe and able to recover.
I was in somewhat similar situation recently - figuring out which linux distro to use. Previously I had luck with ScientificLinux, but this time it didn't like my laptop hardware for some reason - after wake-up wireless network card was getting stuck and wasnt picking any signal. I didn't want to recompile kernel etc., so I installed Ubuntu, but the Gnome 3 was a show stopper - I had to roll back to Gnome 2, but later I tried and liked a lot XFCE desktop - which I use right now on my workstation and laptop.
Java, Python and emacs probably work well with any linux distribution out of the box, so it is up to you which one to choose after all. Good luck!
Sorry, forgot to mention - all contemporary Linux distributions are able to install a dual boot feature - so you can keep your Windows 7 setup along with Linux (if you have enough of free space), moreover Windows partition will be accessible from Linux which is handy sometimes.