So one workaround for VirtualBox is that the script on the VM waits for enough time after rebooting JAX into recovery mode, instructing the user to manually plug out the Type-C USB cable for flashing and put the cable back, and make sure the device is again seen on the VM (ex. VMware Workstation Pro 16 finds the re-connected USB device properly and completed the whole flashing flow without an issue. I did not see this issue with VMware Workstation Pro 16. When the VM (Ubuntu) tries to communicate with the USB device, it does not have the latest USB device so fails.Possibly, this is the Virtualbox mechanism to combat unstable USB connection on some other device (some people reports loop of disconnect and reconnect).However, maybe because the Jetson comes back too quickly, the VM (Ubuntu) does NOT detect the USB disconnect, keep listing the old USB device instance. Jetson reboots, and the host (Windows10) detects the USB disconnect.tegraflash.py after all the other checking, make Jetson reboot in recovery mode.Here is the issue that I saw with Virtualbox. VMware Workstation Pro 16 on Windows 10 → Flash succeeds.Virtualbox (6.x and 7.0) on Windows 10 → Flash fails.I did not test with VMware Fusion on Mac M1/M2. I tested with both Virtualbox (6.x and 7.0) and VMware Workstation Pro on Windows 10 host. For example, is there some state that gets messed up on the Jetson device when it gets passed from the host to the VM? Is there some additional latency that breaks some time-sensitive operation? It would be good to know more specifics about which programs have issues and what part of the process breaks down. I am surprised about this because it cannot be universally true across all virtualization programs, host operating systems, and hypervisors. VMs are not supported is because they don’t handle USB correctly for the case of a USB device which repeatedly disconnects and reconnects (which is what happens during flash) So rather than discouraging it, it would be beneficial to try to identify and resolve some of the root causes of problems that arise. They’re incredibly convenient, and one doesn’t need to keep a special laptop around with the blessed version of Ubuntu just in case there’s a need to reflash. Obviously, a lot of people want to use virtual machines. There are some other stories linked from this thread. I can share anecdotally that I have succeeded a few times from an Ubuntu VM on an Intel-based Mac, but I’ve never gotten it to work on an Apple Silicon Mac (fails immediately), both using VMware Fusion. The advice is often given here to not flash a device from a virtual machine.
0 Comments
Leave a Reply. |