Custom Query (16363 matches)
Results (904 - 906 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #926 | fixed | Seamless mode support for Multimonitor -> fixed in SVN | ||
| Description |
Hi, seemless mode is one of the biggest improvements I found over VMware workstation, but unfortuantely it only works with one monitor - but today more and more people use mutli-monitor systems (I personally use a 3 Monitor setup - with xinerama) and it would be nice if I can place application windows in seemless mode to all of them but yet the seemless mode only works in the monitor the seemless mode is started. I have no joice to drag the application to one of the other two monitors. Thx Ralf |
|||
| #927 | fixed | Fails to bring host networking down on startup error | ||
| Description |
I had been using a "host pipe" serial port, which I create using an external command (socat) before booting the VM. Unfortunately, the command exits and the socket file is deleted when I shut down a VM. If the socket file is missing when the VM is booted, this results in the following error: Serial device 0 cannot attach to char driver
.
VBox status code: -102 (VERR_FILE_NOT_FOUND).
Result Code: 0x80004005
Component: Console
Interface: IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}
And the VM fails to start. I disabled the serial port and then tried to start the VM again, but then got the following rather cryptic error: Unknown error creating VM (VERR_HOSTIF_INIT_FAILED).
VBox status code: -3100 (VERR_HOSTIF_INIT_FAILED).
Result Code: 0x80004005
Component: Console
Interface: IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}
Only after a lot of frustration did I discover that this was caused by the fact that my "host interface" network adapter had not been brought down after the first attempt to start the VM. Manually running the script I use to bring the vbox0 interface down solved the problem, but that was only after I had already deleted the VM and its snapshots and created a new one :-( Please:
The first error message could also be improved by explicitly mentioning which file could not be found. |
|||
| #928 | obsolete | Mounting share directory on Linux host result in Protocol error if default share name is used | ||
| Description |
Host is Ubuntu 7.10. Guest is Linux Mint 4.0 I created a new shared directory using the GUI in a machine's setting. The GUI will prompt me to select a host directory for the shared directory. When I select the share directory, a share name is automatically generated. So if I select the directory "/home/paulsiu/vshare", the share name "vshare" is created. If I attempt to mount the vshare using the following command in the Linux Guest I get the following error: sudo mount -t vboxsf vshare /home/paulsiu/share /sbin/mount.vboxsf: mounting failed with the error: Protocol error The syslog will have the error: Oct 8 18:27:09 wxbuilder kernel: vboxvfs: sf_glob_alloc: vboxCallMapFolder failed rc=-102 Oct 8 18:27:09 wxbuilder kernel: sf_read_super_aux err=-71 Now suppose I go back into the GUI and change the "vshare" to "vshare2". The following mount command will work: sudo mount -t vboxsf vshare2 /home/paulsiu/share For some reason, whatever Virtualbox select as the default share name will always fail to mount. If you pick something else, it will work. |
|||

