Skip to content

virtual box "5.0.4" bridged networking connection issue between guest and host (windows 10)

Since we spent days (let me write it again, daaayyyyyyssss) to solve this problem. To prevent you from doing the same, I write this entry.
Our problem was, that a guest box was running fine on a virtual box host. The "only" issue was, that everyone could ping (and even do more) with the host and the guest os, except the host talking with the guest and vice versa.
It looks like this is a microsoft windows 10 issue only. Everything is workin on my *nix systems - meaning, if you are using real software, no problem is there.
But seriously folks (I know you are not reading this entry because you want to have some funny battle from good, free as in freedom software, against clunky ugly and bad close source whatever), the solving of this issue is braindead simple.

It a also contains a workaround: 
- Open the network adapters in Windows 10
- Open properties of the adapter used in your guest OS
- Disable IPv6 -> OK
- Open properties again
- Enable IPv6 -> OK
ticket number 14457
ticket number 14428

Good luck and stay with the force.

Translate to de es fr it pt ja

Pro OpenSolaris

Another month, another book, but still an apress one ;-).

This time, my eyes were focused on the operation system side. It is sad but after reading this book, i can still feel and see the echo of the wounded heart that oracle made by stopping the open solaris development in 2010.
This os reads and feals really well structured and "like a fresh breeze".

But back to the book. If have already index the book with my sticky markers and from now on i have quick access to the following content.

  • CLI
  • SMF
  • ZFS
  • Zones
  • AMP
  • SVN
  • DTrace
  • Links

The book contains 240 pages, so can not bring you in that deep. But it at least it tries, or tries to show you the great world of this operation system.
While playing around in a VM, it still feals that fresh and easy way. The os is well structured and by scratching at the top, all works well. And of course, just for DTrace, SMF and ZFS ... you should give open solaris a try.

The book itselfs is short and well written and shows you the represents you the main benefits of this os.
Because of the fact that open solaris is currently not in well progress, the price is more than cheap. And if not using open solaris, it is good to read about the concepts and the way the os is structured.

Translate to de es fr it pt ja

Virtualbox could not start - error message says "run /etc/init.d/vboxdrv setup"

If you shell outputs something like the following don't get frustrated, the solution is just one apt-get install away! The error

WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release. Stopping VirtualBox kernel modules:. Uninstalling old VirtualBox DKMS kernel modules:. Trying to register the VirtualBox kernel modules using DKMS:Error! echo Your kernel headers for kernel 3.0.0-1-686-pae cannot be found at /lib/modules/3.0.0-1-686-pae/build or /lib/modules/3.0.0-1-686-pae/source. Failed, trying without DKMS ... failed! Recompiling VirtualBox kernel modules: Look at /var/log/vbox-install.log to find out what went wrong ... failed!

The solution

apt-get install linux-headers-3.0.0-1-686-pae /etc/init.d/vboxdrv setup

You see, your system just needs the current kernel header file and thats it.

Thanks zzeroo for the the hint

Translate to de es fr it pt ja