Howdy- I'm not sure how many other Linux users are experiencing problems similar to that described in https://www.virtualbox.org/ticket/11610, but I recently noticed one difference between working and non-working versions and I wonder if anyone is aware of recent changes that might explain it.
Long story short, running VirtualBox 4.2.10 or 4.2.12 on Linux hosts with kernel v3.8 or later triggers a kernel oops when booting guest vms. VirtualBox 4.2.8 with kernel 3.7.10 works just fine. One difference I noticed in /var/log/messages between working and non-working versions is that when booting guests on a working version there is a message "device vboxnet0 entered promiscuous mode" but on non-working versions the message is "device eth0 entered promiscuous mode." Notice the difference in device name. There's much more detail and several sample logs in the bug entry, but I'm just curious if anyone is aware of any changes in either VirtualBox 4.2.10 or Linux 3.8 that would explain why VirtualBox trys to enable promiscuous mode for a different network device when booting guests. Thanks in advance! Best, Kent ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
