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
com.apple.vmnet is missing #37
Comments
it doesn't exist at all? what version of OSX are you on? |
totally not there. Yosemite upgraded recently from Mavericks |
can you run the command |
no results, sadly. |
very interesting. i'll have to look into this deeper. @ailispaw ever seen this happen? |
Just had the same issue. no results for the find as well. |
@nlf I've never seen that before. |
ok, great, thanks for letting me know. i bet we can work out a solution to this in the script. |
@evanmcc You're welcome. I'm glad that worked for you. |
running the b2d version fixed this issue for me. once started, the running instance hung after 3 commands so I had to kill it via kill -9 |
Have the exact same problem but boot2docker-xhyve doesn't work for me because clang (tried different versions) persistently crashes while compiling uuid2mac. |
@therealprof can you pull from master and try again with the latest version of the script and tell me if that works for you? |
Works fine, thanks. |
did you get the warning about restarting the vm to setup nfs exports? |
Maybe the reply was too early... How long is it supposed to be starting up?
|
hmm, it should've started fairly quickly. can you check the output of |
Still starting up but xhyve is not in the process list. |
go ahead and hit control-c to stop the startup and try again, if it's not in the list something failed along the way. |
Tried to start it manually using the information from dhyve status and get the error:
Seems like two things are foul: The vmnet stuff is not correct and dhyve does not detect that xhyve exited early due to problems. |
the permission denied sounds like you didn't use we do need to figure out how to detect a crash in xhyve though |
I did. ;)
|
try it like this with the quotes around the kernel command line
|
Same problem. But since the commandline was assembled by dhyve anyway I would expect it to work as is when called from dhyve, no? ;) |
very strange. ok i'll continue debugging on my end, thanks for the info! |
Hi @therealprof ,
Did you see any error messages on compiling uuid2mac? And I would like to know the version of your Yosemite 10.10.x and vmnet.framework.
|
No, it just segfaults, same message with the standard Xcode clang: tar zxvf boot2docker-data.tar.gz
Yosemite is 10.10.5 (14F27) BuildVersion : 23 |
@therealprof Thank you so much for the prompt reply. How about xhyve itself? Did you compile xhyve without any problems? |
I'm using the bottled homebrew xhyve version. |
dhyve is not working either... It all boils down to:
|
It seems something wrong with libraries or framworks in your system, which xhyve uses. |
Or do you have any zombie processes of xhyve? If so, please kill all of them. |
brew install xhyve --HEAD is compiling directly from the git sources. As mentioned I've tried that but still no change. The least thing that boot2docker-xhyve should do IMHO is to check whether /Library/Preferences/SystemConfiguration/com.apple.vmnet exists and bail out with a meaningful error message before causing lots of random error messages. ;) No, there're no xhyve processes running. |
I see. Yes, boot2docker-xhyve should do it. Hmm. It seems I can not help you for now. I will investigate it. |
It looks similar to this. Sorry for bothering you with boot2docker-xhyve things here. |
I'm seeing a similar issue, with a failure of I also see in Console.app when this happens the messages
|
At least on my end, the issue I and @therealprof are having seems to have been caused by NAT/Network Sharing having been disabled on my mac.
Also NAT has to be enabled for NetworkSharing to run:
EDIT: After this I can run xhyve with working network, ping back and forth from the host and guest, but still am not seeing |
Hm, does not work for me:
And NAT was already enabled. xhyve is still complaining. |
Wow this is a long thread. I think I have the same issue
however it's being masked by #653b8e8c3 so I just see Is this file meant to be created by the Yosemite installer? |
The current theory is that file is created when the network sharing has been used the first time. Note though, that the filename is |
Oh I have that file. |
good eye, added in the .plist extension |
the other part of that commit is needed too, to avoid an error when the file exists. I swear I created a PR for that commit, but I can't find it now. |
i'm not sure i follow, i left the commit intact and only added the .plist extension to the test. what else am i missing? |
I had to change the test on L313 to avoid an error when the file exists (since the test expects an integer) , see the commit message and body of 9acf6f8. |
just pushed an update, should take care of that |
I am facing a similar problem
NOTE: If I run xhyve without $UUID OS boots up just fine, but I wish a same ip for every boot. |
Actually all of my problem just vanished this morning. Yesterday night I was looking through various log files again to find the reason for sporadic erratic behaviour of some applications (like the clipboard not working in the latest Chromium version) and in due course I discovered that there were some old files in /var/run and /var/db which were not supposed there and couldn't be removed. So I booted into Recovery and did a little spring cleaning, including disabling rootless mode and removing those bogus files and plenty of others which haven't been touched since 2011; sure enough after a reboot dhyve, xhyve, Veertu and the Docker for Mac Beta didn't have any problems wrt to networking anymore. Not exactly sure what exactly was the culprit here but something most certainly was. NB: This system has been updated all the way from Leopard so if you have a senior system, you might want to check for any leftovers... |
Found it !! In my case culprit was UUID (I have no idea why)
By changing the UUID I get same IP across reboots. |
@therealprof I'm having all of the same issues that you're having. What exactly did you remove in |
I posted a Stack Overflow question since it's a better forum to answer these sorts of things. |
@nhooey I'm sorry but I have really no idea what exactly did the trick. It was simply some severe pruning and suddenly things worked again. |
the file
/Library/Preferences/SystemConfiguration/com.apple.vmnet
doesn't exist.This leads to errors of the flavor:
The text was updated successfully, but these errors were encountered: