On Sat, 26 Jan 2019 12:12:07 +0530, Bharath Vedartham said: > On Fri, Jan 25, 2019 at 11:24:33AM -0500, valdis.kletnieks@xxxxxx wrote: > > On Fri, 25 Jan 2019 17:11:25 +0530, Bharath Vedartham said: > > > VM has low RAM. Need to adjust :) > > > > Upgrade the hypervisor system so the VM can be properly configured :) > > > I think I ll rather build a native version. The reason I chose a VM was > cause I was told that if I break the kernel it would be much safer. But > I think GRUB will save my life if I screw things up. Thanks for your > time! Well, your /boot should be big enough at install time, and remember to keep multiple versions around (mine is big enough to keep 3-4 known-good kernels and up to 12-15 more during a git bisect). And remember to take backups of your system. (Seriously - the first time you do an 'rm *' in the wrong directory will make up for the US$80 or so an external USB drive will cost you) > > (As a side note, few people send their diffs from inside their test VM. > > They usually build outside the VM and copy the needed pieces into > > a shared area that the build environment and the VM can both see.) > That is an interesting usecase. I wonder why they need to do that? As I said, I know of very few (approximately zero) who send the diffs from inside their test VM. The vast majority do the devel work outside and copy it. About the only use case of sending from inside the VM I can think of is the hypervisor being Windows HyperV. Though why somebody would be doing Linux kernel devel in a Windows shop is beyond me. :) _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
