I have to change the boot start location from the SDA in my computer’s ssd to the SDB of the external ssd with higher memory. and no if I copy the virtual box files from one ssd to another boot start moves.
You mean you are wanting to move virtual box files to a larger drive?
Or want to reconfigure the host boot files (i.e. the main OS boot set up), two very different things, you need to be clearer about your intent!
the virtual box files are already in the external ssd and it’s already set as default disk but the boot start of kali is in the ssd of my computer
If you want to install Kali directly on an external drive, you wont be using a virtual box image, but an installer ISO image, you’ll boot from that image and install Kali AND the bootloader (Grub) to the external disk, you would then have a bootable kali installed to an external disk, which is I think what your trying to achieve?
No listen, i want to use an external disk for my virtual machine, i have already tranfered the machine files inside of this storage however the issue is that the virtual machine doesn’t boot using that disk
boot in EUFI USB mode, turn off secure boot and enter bios eufi settings and select boot frmo eufi usb
sorry not frmo, from…
The only way you could change the boot sector if you want everything on sdb drive is to boot Kali, create a new partition for boot loader on sdb drive with GParted and reinstall grub there instead.
If any of this sounds confusing to you, I’d suggest reinstalling Kali and setting this up that way from the beginning, its only a VM
know a video that shows how to do
If you need a video, which may or may not exist, try searching for one, I suspect you won’t find anything.
In your case, I would suggest starting again with a live boot ISO, deleting any and all partitions you have on your target drive you want Kali installed on using GParted, formatting it to ext4, and then reinstalling Kali again, making sure you also install the bootloader to that same drive. That is IF you want a bare metal install on the external drive that will be bootable
If however, which is what I am suspecting you actually mean, you have simply ‘moved’ a VM file to a different drive, then instead of trying to boot it which will fail because it is no longer where the VM manager expects it to be, you don’t ‘move the boot’, you ‘import’ the VM image into the VM manager, pointing it to your new location when it asks where to import from…
And I am ‘listening’, but you are not being very clear, moving a VM doesn’t need a ‘boot sector’, that is all taken care of by the VM hypervisor, whilst a ‘bare metal’ install would require a bootloader, and is a different set up.
Bare metal or VM ?
I had set through the application vm the position on the external one and now I recognize that it is from there as you see in the pictures. It’s just that I have to move the boot start. only that I have moved both the “.vdi” and the “1.vdi”
Your host OS is using the virtual machine files, so the ‘host’ has to be running for the VM software to be able to boot the VM
You cannot run a VM directly on hardware from a machine boot, everything inside the VM is emulated, you can’t simply move a VM to an external drive and make it bootable without launching the Host OS.
IF you want Kali on an external drive that is bootable directly on hardware, then you need to boot Kali from a Live or installer ISO directly from booting the machine (this behaviour is configured in the UEFI or BIOS), and then install Kali and all its files, including the boot sector, on that new drive.
As this stands, I don’t see what the problem is, the VM software is working exactly as it was intended to.
As I said in the beginning, be clear of what your intended outcome is, rather than asking how to do something you think is correct, but may not be.
So your VM has borked the Grub loader, now that would have been where to start!
some command don’t go there you saw it, it’s not that i have to use the live iso