I am trying to run a custom ISO in VMWare workstation.
You can refer my Github project for the source code.
When I run mykernel.iso base OS I am getting the following screen, instead of printf() that I have defined.
Related
Clearly, you can run Code Server on a Linux host, or with WSL on a Windows host. Either will provide a Linux run-time environment for your code. I have 2 projects with 3rd party Windows binary dependencies which will not run on Linux. So, is there a way to get a Windows run-time using Code Server?
I'm trying to run TwinCat 3 XAR in a PC where I need to have hyper-V ON to run Azure IoT Edge (which uses hyper-V). Is there a way to run XAR with hyper-V turned on? Is there any way to isolate the cores from hyper-v or something else?
Edit 22 April 2022
For a complete tutorial on this see my blog post.
There is a way to accomplish this. You can do this by instead of having a local runtime, you can run the code on a runtime in a virtual machine. I got the idea from this reddit post.
To make it work I did the following:
Download and install VMware Player. Its free for non-commercial use. You can also use the paid Pro (Workstation) version. I'm not sure if this also works with Virtual Box.
Install TwinCAT BSD on the virtual machine as described in this excellent YouTube video by Jakob
If you're using VMware Player and need to enable UEFI you need to do the following as noted by YouTube user Eivind Hilde:
Follow the guide in the video, but skip the step where the firmware type is set.
Try to boot the VM. it will fail.
Open the .vmx file in the VM directory with notepad .
Find "firmware = "bios" and replace with "firmware ="efi"" and save. If this line doesn't exist, just add it somewhere.
It will now boot, and you can follow the guide in the video for the rest.
Run your TwinCAT project on the virtual machine, without the need to disable Hyper-V. 🎉
Previous answer
I don't think so. InfoSys mentions:
Hyper-V environment:
The runtime environment cannot be started inside a Hyper-V environment. This refers in particular to virtual Hyper-V machines, which are run in a privileged Hyper-V machine. As soon as a component of the computer uses Hyper-V, only the engineering environment (XAE) can be used on this computer, not the runtime environment (XAR).
But they also mention that:
TwinCAT attempts to detect these Hyper-V environments; however, it is in the nature of virtualization approaches that they do not wish to be detected and TwinCAT therefore cannot carry out any 100% detection.
So maybe there is some way you can prevent TwinCAT from detecting a Hyper-V environment. However, that is something I can't answer.
When I watching the openstack launch a VM:
in the 5:12/7:06, you see there choose a image then launch a VM, it will install the OS.
I want to know the technologies of the auto deployment of OS.
How can OpenStack can auto install the OS into a VM?
EDIT-01
I mean how can OpenStack can deploy OS into a VM.
Such as the Windows can use Windows WDS to deploy the OS, the Linux can use kickstart to deploy the OS.
how about the OpenStack can deploy both the Windows and Linux?
There are lots of images type which you can use with Openstack Platform. Some of them are:
RAW, QCOW2, ISO, VHD, VMDK, DOCKER, PLOOP.
Out of which QCOW2 format is a live OS image which does not require OS installation, as you can use it directly without any installation. Same is for VHD, VMDK image format.
If you have used ISO as a format this will install an OS first & then you can use it just like normal OS installation. But it takes time to install an OS instead use Qcow2 images for faster deployments.
Upload an image to your Openstack Platform then while launching an instance select that uploaded image in Image section.
This service probably has a folder containing various OS images. These OS images were prepared ahead of time to work with OpenStack's VMM and network. The OS image is supplied to the VM, and when the VM launches, it initializes the OS.
I have mistakenly formatted windows xp partition of my hardrive while trying to install lubuntu operating system.
Now I can only have access to my computer through the live USB disk of lubuntu.
I have couple of .iso files of windows xp cd.
But when I tried to create bootable USB drive from it, it doesn't work.
It either shows "bootmgr is missing" message or it show a blinking cursor and nothing happens while booting.
The iso's that I have, contain all the necessary installation files required.
Is there a way to make USB drive boot from it?
I tried softwares like rufus but that too doesn't work with iso that I have.
try to google a software called ultraiso, it can create an installation usb using an installation Windows cd or iso, no matter the Windows is xp or 7 or 8 or Windows Server.
If you can't find it in google, try to find it using another search engine such as www.baidu.com
then using the usb, you can install Windows again in your hard drive
I've compiled a cu program on my laptop, using NVIDIA CUDA 5 toolkit. A very basic interface, using only terminal output. Then I went on to test how it runs on my desktop PC (both have Ubuntu 12.04 LTS installed).
On the desktop PC I get this error message:
error while loading shared libraries: libcudart.so.5.0: cannot open shared object file: No such file or directory
Ok, I get it, some libs are not installed. But do I really need to install CUDA toolkit on every PC where I'd want my compiled code to run?
To deploy a CUDA runtime API application on linux you only need to do two things:
Make sure that the machine in question has a CUDA compatible card and a minimum driver version which matches the CUDA Toolkit you used to build the application (you can find information regarding both of these in the release notes of the toolkit)
Distribute the runtime library (so cudart.so) that you built the application against with the executable. If you used any other libraries from the toolkit (like CUBLAS, CUFFT, CUSPARSE, etc) you need to inlcude those too. The CUDA runtime library is versioned and you have to have the libraries which match the toolkit you are building with. You may need to use the LD_LIBRARY_PATH environment variable to ensure that the correct versions of the libraries are found by the link loader. Often a simple shell script which acts the canonical application, settings LD_LIBRARY_PATH variable and running the built executable is the best way to do this.
If you get those two things right, it should just work.