Detailed analysis of the Linux kernel compilation process in the VMware environment

Finally, you can use the newly compiled kernel debug driver in vmware, although it is often used in vmware, but it has never been compiled in the kernel, so no I know that there are so many ways. The process of compiling the kernel is not mentioned. In addition to the general compilation process, each distribution may have its own unique compilation commands, such as the debian I use. Below are just the steps I have tried during the compilation process. 1. From 2.6.18 sourcecode from kernel.org, compile and install and use the new kernel to start, see the following annoying error: VFS: Cannot open root device "sda" or unknow-block(0,0 ) app app a a a a a a a a a a a a a a a a I copied this system to another hard disk and encountered this error when booting with a new hard disk. That is because the hard disk is not connected to the IDE interface corresponding to the original hard disk, but this is definitely not to let it follow me. The reason for this, of course, has been as thick as the bras. I don’t think it will fall here, so I don’t think much about it. I just use the most common method to restart Dafa. I hope it will be It was a moment of negligence. But after a few tens of seconds, it suddenly appeared in front of my eyes, without it, I had to google it. 2, from the results of google, the same channel (together with the road) is quite a lot of people, a variety of processes revealed a roughly solution. Mainly the kernel configuration options, and mainly focused on Device Drivers——>SCSI device support——>SCSI low-level drivers——>BusLogic SCSI support mainly because vmware needs it when using scsi And the file system, I use ext3, because I saw someone saying that they didn't compile them directly into the kernel, so the startup is still unsuccessful. Give yourself a lazy reason, and don't try too much, just build them-in. Then, execute make-kpkg –revision=1.0 kernel-image to compile, and use dpkg to install and restart. It is frustrating that the cute mistakes in the previous lines have appeared again. 3, then go back and check the kernel configuration options, I think the relevant has been selected, it is reasonable to say that the root file system should not be found again, or try initrd? Although the above modules have been compiled into the kernel, is it still necessary to create initrd? Right and try it, so recompile the kernel make-kpkg – revision=1.0 kernel-image –initrd Then install and restart, actually opened the sticky panic, but there is still some cloud in the fog, huh, linux These things seem to be like this, take the time to study initrd.