VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (10 - 12 of 16363)

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Ticket Resolution Summary Owner Reporter
#16 fixed Bug in /etc/init.d/virtualbox prevents recomplication of kernel module with dpkg-reconfigure tfim
Description

The /etc/init.d/virtualbox script checks if a kernel module exists and fails if there is none, regardless of the action requested. This causes problems when using dpkg-reconfigure virtualbox to rebuild the kernel module, because the init script will be called to stop the virtualbox service first - and cause dpkg to abort because it fails, creating a chicken-and-egg problem.

A workaround is to replace line 133:

fail "Kernel module not found"

with

true

#17 fixed Unsupported options prevent vboxsf mounts to work properly when added to fstab tfim
Description

As far as I know, there is no way to disable 'noexec' in the fstab (adding 'exec' to the list of options only seems to override it). This always causes an error message to appear that says

"unknown mount option: noexec"

While mounting works fine from the commandline, it would be good if it was possible to use fstab for mounting.

#18 fixed [feature-request] VirtualBox Networking Model - new idea Technologov
Description
  • Why is the TAP driver is "so needed"?

You say that Linux has something like this already, so you provide it only for Windows.

  1. Actually, all Windows NT-based systems has something like this included.

The MS loopback can be added via Control Panel/Add Hardware/New Hardware/Manual/Network Adaptors/Microsoft. It is treated as just another NIC. Does your TAP driver provide you with features that you *absolutely* must-have? If not, then it's better to use the MS one, because it's signed. (and gives no stupid driver signature warnings during adding of an extra NIC)


Actually, I think we can get much more far *without* any such TAP drivers at all.


  1. I think that the current networking model needs new revision: (if I

understood your networking model correctly) : it can be much more scalable, if it will be done the "Microsoft Virtual PC 2004"-way; (or if you hate MS way, then look at the Open-Source emulator "Dynagen"-way)

that is: I think that we don't have to use any such TAP driver at

all. We can use the host network interface directly - of course we need some way to enumerate them - two ways exists: Windows Registry or WinPCap. (BTW: Open-Source Wireshark, while not an emulator, also uses this technique)

With this approach hubs will be created automatically, without any need to define bridges manually. Windows 2000 host will be supported much better this way (because AFAIK it doesn't have bridging) and Windows XP host won't be limited to one bridge as it is now.

As a bonus, the Linux host networking will become piece-a-cake - instead of manually creating TAP interfaces and then bridging them to real host interfaces (manually again, all via command-line), this new approach will enable to integrate it all nicely within a GUI so click-click-click will solve it all. Basically a Linux user, working with a GUI-only, will be able to achieve host-networking effect under Linux very easily !

The possible downside costs is an extra dependency: libpcap/WinPCap (to make things cross-platform).

Please be patient, because I might be incorrect in some cases; after-all I looked at your software for only one day. Please tell me where I'm right and where I'm not.

-Alexey Eremenko (CCNA, Cisco Certified Network Associate)

(originally sent :vbox-users@…

date Feb 7, 2007 10:49 PM)

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy