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

Once close some instance based vbox, show error and close failed. #1444

Closed
superwolfboy opened this issue Aug 25, 2016 · 15 comments
Closed

Once close some instance based vbox, show error and close failed. #1444

superwolfboy opened this issue Aug 25, 2016 · 15 comments
Labels
Milestone

Comments

@superwolfboy
Copy link

superwolfboy commented Aug 25, 2016

As screenshot, when I close these extermeXos based on vbox , they can not be clolse and show errors:
image

OS: lubuntu 16.04
Vbox:5.1.2
GNS3 and server:1.5.2

@julien-duponchelle julien-duponchelle added this to the 1.5.3 milestone Aug 25, 2016
@julien-duponchelle
Copy link
Contributor

I doubt it will the issue but did you try with VirtualBox 5.1.4?

@superwolfboy
Copy link
Author

tried and the same :(
image

@julien-duponchelle
Copy link
Contributor

It's the only vm that create issue?

This VM have special hardware? It's slow to stop?

@superwolfboy
Copy link
Author

I have alread tested some condition:
1, all the extermexos running on vbox,
2,when extermexos enable acpi shutdown, AND connect with other extermxeos, the problem will happen.
3,when extermexos not enable acpi shutdown , AND connect with others , the problem will NOT happen
4,when extermexos enable acpi shutdown, AND NOT connect any others, the problem will NOT happen.
So at this moment disable the acpi shutdown would solve this proble templary,

and I tested a tinycore running vbox ,it has simlar problem.

@julien-duponchelle
Copy link
Contributor

It should be fixed in last server source code

@Raizo62
Copy link

Raizo62 commented Sep 6, 2016

Hi

I have believe that i have still the bug (with last release 1.5)

On Linux (slow PC : with no accelerated processor, and access to vdi with nfs), i have the same error when i stop a WinXP connected to "ethernet switch" :

Server error from http://user@127.0.0.1:3080: WinXP-1: VirtualBox has returned an error: VBoxManage: error: The machine 'WinXP-1' is already locked for a session (or being unlocked)
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
VBoxManage: error: Context: "LockMachine(a->session, LockType_Write)" at line 507 of file VBoxManageModifyVM.cpp

If I have only WinXP (without ethernet switch), i have no error

With VM without gui (console access), i have no error.

@julien-duponchelle
Copy link
Contributor

With the 1.5.2 or with the source code of 1.5.3?

@Raizo62
Copy link

Raizo62 commented Sep 6, 2016

the source code of 1.5.3

Edit 1 : I have tested on PC with accelerated processor (but always access to vdi with nfs) : i have always the error message.

Edit 2 : I have tested on PC with accelerated processor and without nfs (VM debian without access console) : i have always the bug

@julien-duponchelle
Copy link
Contributor

You are using last Vbox also?

@Raizo62
Copy link

Raizo62 commented Sep 7, 2016

yes

@Raizo62
Copy link

Raizo62 commented Sep 8, 2016

Did you can reproduce the bug ? if not, do you want logs or others files ?

@julien-duponchelle
Copy link
Contributor

julien-duponchelle commented Sep 8, 2016

I think this the problem GNS3/gns3-server@d68bf1c. Could you test with last source code?

@julien-duponchelle
Copy link
Contributor

You just need to test with last server

@Raizo62
Copy link

Raizo62 commented Sep 9, 2016

I have tested, and it works
Thanks :-)

@julien-duponchelle
Copy link
Contributor

Thanks for the feedback

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

3 participants