Fixes #1061 with VM name selection #1161
Conversation
FrenchBen
force-pushed
the
1061-VM-name
branch
2 times, most recently
from
97f6c1c
to
8188248
Compare
|
Tried to QA with Windows but currently getting some errors from virtualbox. Will wait for new toolbox to be pushed out |
|
Taking a look! |
|
FYI, it looks like the branch needs to be updated prior to final push |
Signed-off-by: French Ben <me+git@frenchben.com>
FrenchBen
force-pushed
the
1061-VM-name
branch
from
8188248
to
5f76089
Compare
FrenchBen
changed the title
|
@FrenchBen Did this PR quietly die? |
|
@pmario it did due to machine management. The VM selection was fine, but for the most part, there was no mounting of folders and misc actions were broken. |
|
Yea. I found out already, that the whole system is heavily connected to vbox. From a programmers point of view. Way to heavy. ... IMO kitematic needs a plugin mechanism, where vbox handling is a plugin too. This would give us (the community with different requirements) the possibility to remove the vbox battery and replace it. At the moment I'm investigating to create shared folders with hyper-v and using container tech and not vbox tech. |
|
I agree with that approach, unfortunately the current heavy vbox integration makes it difficult. |
Signed-off-by: French Ben me+git@frenchben.com