I am new to linux OS. According to the requirement of my project I have to install extensible Hypervisor Framework( XMHF) and then build the required hypapp over it. Grub is supposed to load the XMHF at boot time and then the ubuntu OS has to laod over it, But when i am trying to boot the system according to the steps mentioned to install XMHF the system stops at the Starting up.... state at the time of booting. I dont know where i have done mistake. I have checked it many times but nothing useful. Can anyone please help me with this?? "Installing XMHF" manual can be found at http://xmhf.sourceforge.net/doc/xmhf/doc/installing-xmhf.md.html
My grub entry for XMHF is
title XMHF
rootnoverify (hd0,0) // as i have no primary partition for the hard drive
kernel /boot/init-x86.bin
module /boot/hypervisor.bin.gz
modulenounzip (hd0)+1
I had the exact same problem.
I had to properly configure serial output, either physically or serial-over-lan, to see XMHF's output. In my case, I missed a Intel VT related switch in BIOS.
How to configure serial console can be found here: https://www.cyberciti.biz/faq/linux-serial-console-howto/
go through this http://xmhf.sourceforge.net/doc/xmhf/doc/installing-xmhf.md.html this will be helpful :D
Related
first up I don't even know if this is the right thread to post in, if not I'm sorry.
For my OS-class I need to install Linux Mint in Virtual Box.
I don't have any experience in that sort of thing and don't even know how I barely passed my programming class last year.
So. I installed Virtual Box. Downloaded the Linux Mint 64-bit ISO file?
I started a new machine in Virtual Box called it "Linux Mint", type Linux, Version other Linux (64-bit).
No problem so far. Then I configured all the stuff they ask you. (Yes, I have exactly no clue what I'm doing.)
Now. I started the machine and entered the previously downloaded file linuxmint-20-cinnamon-64bit.
That works, then the Virtual Box screen comes up, quickly after that it changes to the Linux Mint start screen saying "Welcome to Linux Mint 20 Cinnamon 64-bit" and below that options what to do. First of them is "Start Linux Mint".
If I either wait for it to boot automatically or click "Start Linux Mint" it takes a second and then comes up with the error message:
Kernel panic - not syncing: No working init found. Try passing init= option to kernel.
So, I don't know what that means. Can anyone help me with that?
Thanks in advance!
The issue has been resolved!
The ISO wasn’t corrupted, I just had to give the virtual machine more RAM. The suggested 512MB weren’t enough, I upped it to about 1.5GB and then it just worked.
Long story short, I bought a pre-installed linux laptop and would like to be able to run other linux distros, but use the same linux drivers w/ other distro so as to have all my hardware work flawlessly as it does with the custom linux Ubuntu 14.04 LTS.
If I could save or copy all of my hardware drivers someplace to reinstall once I've got a new linux distro installed.
So far I think the answer lays in compiling a linux kernel and modules from my running linux laptop, and try to get flashed in my new linux distro that I'm installing. Not sure if that will work? or is the easiest method.
Any help or ideas would be greatly appreciated.
i just want my linux workstation hardware to work as good as it does w/ Ubuntu 14.04, with any linux distro I choose to try.
Thanks in advance
A bit weired, but, as far as I gnow:
you can do the thing you ask for to customize the same distribution.
"Compiling a linux kernel and modules from my running linux laptop": You said the running one, so You can pick it instead directly from "/boot/vmlinuz-KERNEL_VERSION
"If I could save or copy all of my hardware driver": You can copy the content of "/lib/modules/KERNEL_VERSION" folder in the same emplacement in the target. This folder contains kernel modules, among others, device drivers.
After having these in place, you can make the drivers working with "modprobe", you should have a list for all modules (you might use "lsmod" in the original system) and load them one by one or find a way that manage to load them all at once for you; in CentOS, there is a scrpit "/etc/rc.d/rc.sysinit" that can among other stuffs, do that for you.
I really wonder why you are worried about drivers on Linux distributions, coz, as far as I know, they are really good when it comes to device drivers.
I installed linux debian as a 2nd system and it works fine, however when I choose Windows in loader(lilo) to boot, it stops on a windows logo.
I tried to boot in safe mode, and it stops on classpnp.sys driver.
I'm not sure whether the problem is in classpnp or in some other driver which is failed to load after it.
I also tried to boot with bootlog (ntbtlog), however it is not created (I check C:\Windows).
It seems like smth is wrong with hard drive configuration with several partitions.
I've googled a lot of similiar issues with classpnp.sys, but none of the solutions helped:
-I tried to change bios SATA coniguration from IDE to AHCI,
-restore backup configuration files (SAM, DEFAULT, SECURITY etc).
If anyone knows what else can I do with this, please help.
This belongs on super user, but you need to press F8 and select safe mode. There you can fix your problems
I have compiled the Linux kernel with configuration options for ROOT_NFS. My problem now is the screen prints to fast for me the see the error and I cannot find any documentation on the best approach to solve this problem. I am performing this in VirtualBox.
There is Documentation/serial-console.txt you could look into. Serial console has traditionally been used for debugging linux boot problems, where you then can save all of the screen capture on a different pc. This should be possible for a virtualbox use case as well, although I do not know how difficult it will be to configure serial access.
The dmesg command prints the kernel's circular log buffer. Your messages may be in there.
I'm considering doing some Linux kernel and device driver development under a vmware VM for testing ( Ubuntu 9.04 as a guest under vmware server 2.0 ) while doing the compiles on the Ubuntu 8.04 host.
I don't want to take the performance hit of doing the compiles under the VM.
I know that the kernel obviously doesn't link to anything outside itself so there shouldn't be any problems in that regard, but
are there any special gotcha's I need to watch out for when doing this?
beyond still having a running computer when the kernel crashes are there any other benefits to this setup?
Are there any guides to using this kind of setup?
Edit
I've seen numerous references to remote debugging in VMware via Workstation 6.0 using GDB on the host. Does anyone know if this works with any of the free versions of VMWare such as Server 2.0.
I'm not sure about ubuntu thing. Given that you are not doing a real cross compilation (i.e. x86->arm), I would consider using make-kpkg package. This should produce an installable .deb
archive with kernel for your system. this would work for me on debian, it might for for you
on ubuntu.
more about make-kpkg:
http://www.debianhelp.co.uk/kernel2.6.htm
I'm not aware of any gotchas. But basically it depends what kind of kernel part you
are working with. The more special HW/driver you need, the more likely VM won't work for you.
probably faster boots and my favorite is the possibility to take screenshot (cut'n'paste) of panic message.
try to browse to vmware communities. this thread looks very promising, although it dicusses
topic for MacOS:
http://communities.vmware.com/thread/185781
Compiling, editing, compiling is quite quick anyway, you don't recompile you whole kernel each time you modify the driver.
Before crashing, you can have deadlock, bad usage of resource that leads to unremovable module, memory leak etc ... All kind of things that needs a reboot even if your machine did not crash, so yes, this can be a good idea.
The gotchas can come in the form of the install step and module dependency generation, since you don't want to install your driver in the host, but in the target machine.