Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guest data is unconditionally sent from crete-run to crete-vm-node #27

Open
moralismercatus opened this issue May 8, 2017 · 2 comments
Labels

Comments

@moralismercatus
Copy link
Collaborator

moralismercatus commented May 8, 2017

Background

As only the first time a VM is created is the guest data needed (it was assumed that it would be identical on all parallel VMs and reboots of VMs), a conditional flag was added to VMNode's FSM to only accept guest data for the first time.

Problem

crete-run unconditionally sends the guest data every time it starts, regardless of whether it's the first VM or not. This means that there's a break in the synchronization between crete-run and crete-vm-node when more than 1 VM is running (in theory, actual implementation may differ), or when a VM is restarted (caused by crash or other termination).

Solution

Since the feature was implemented as an optimization (to avoid redundantly transmitting guest data), maybe the simplest solution is to remove the feature. I don't believe it serves a necessary purpose.

@likebreath
Copy link
Collaborator

Hi @moralismercatus, Thanks for reporting the issue.

If the "guest data" you mentioned here is the guest configraution file, it is actually being used for replaying test cases on host.

@moralismercatus
Copy link
Collaborator Author

@likebreath I meant the optimization was an unnecessary feature :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants