Difference between revisions of "MVM known issues"
(Tag: Visual edit) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 3: | Line 3: | ||
{{InfoBoxBottom}} | {{InfoBoxBottom}} | ||
| − | + | [[File:TBD.png|thumb|center|200px]] | |
=== Network connection === | === Network connection === | ||
| Line 9: | Line 9: | ||
The issue seems to be related to the Virtualbox manager, and not to the running VM, as it is not enough to reboot the VM but also the manager need to be closed and reopened to make the network work again. | The issue seems to be related to the Virtualbox manager, and not to the running VM, as it is not enough to reboot the VM but also the manager need to be closed and reopened to make the network work again. | ||
| − | |||
| − | |||
Revision as of 10:18, 13 November 2023
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
Network connection[edit | edit source]
If the host network configuration changes (eg. disconnecting and reconnecting ethernet cable), while the VM is running, often the VM bridged connections stop working.
The issue seems to be related to the Virtualbox manager, and not to the running VM, as it is not enough to reboot the VM but also the manager need to be closed and reopened to make the network work again.
