if you are performing os setup or domain recovery, you should move all the hard drive to the root partition. you should not install the os to a partition that is different from the root partition, because the kernel doesn’t recognize it as a partition.

the host controller is free to use any of the smbus or i2c interface for communication with the device. when the smbus mode is selected, device addresses are accessed using 0 to 7. when the i2c mode is selected, the device addresses are accessed using 0 to 2. the maximum device address is 255 in both cases, however, the os driver only supports addressing between 0 and 127.

there are a few differences from running an hdd in an ssd. first and foremost, the number of platters has no meaning. thus, while the platters in an hdd are able to rotate, that same movement is a bit forced and prone to failure. another difference is that there is no physical gap between the platters to account for a faulty or defective piece of the disk. lastly, the number of revolutions per minute is constant as with a traditional hdd. all in all, its a pretty straightforward process except for one large snag: the file system you are using cannot be accessed in real time.
assuming you have followed all the steps above correctly, the usb controller may still fail to initialise and the computer will fail to boot. to diagnose this, you can try one of two things: check the cmos settings by pressing the main menu key (aka the windows key) and select the cmos button, and make sure that the usb boot device is not set as the first boot device. that will prevent the usb controller from booting. check that the cpu is capable of running the usb controllers (as opposed to simply the usb device) by typing vboxmanage list hwvirb in the cli. if it’s not capable, you can use vboxmanage setextradata machinename extensionguidedextensions.hotplug.intel.hasenabled usb controller 0 to enable it. repeat this command to disable it again after the installation is complete.
if you are using the virtual usb tablet, there is a slightly different solution to this problem. you need to attach the virtual tablet to your usb devices, and use those. the mouse is then captured and reported correctly. the left and right buttons and scrolling would not work, but the other buttons and all the buttons on the virtual tablet would work fine. (read the usb connections section if this does not make sense).
5ec8ef588b