Custom Query (16363 matches)
Results (2353 - 2355 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16773 | worksforme | Не удалось открыть сессию для виртуальной машины | ||
| Description |
Не удалось открыть сессию для виртуальной машины Tails. VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED). Код ошибки: E_FAIL (0x80004005) Компонент: ConsoleWrap Интерфейс: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} |
|||
| #10420 | wontfix | Auto install kernel source | ||
| Description |
Problem appear just after install fresh kernel. I have message like this cat /var/log/vboxadd-install.log
Uninstalling modules from DKMS
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxguest/4.1.12/source ->
/usr/src/vboxguest-4.1.12
DKMS: add Completed.
Error! Your kernel headers for kernel 3.0.0-19-generic-pae cannot be found.
Please install the linux-headers-3.0.0-19-generic-pae package,
or use the --kernelsourcedir option to tell DKMS where it's located
Failed to install using DKMS, attempting to install without
/tmp/vbox.0/Makefile.include.header:97: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Останов.
Creating user for the Guest Additions.
Creating udev rule for the Guest Additions kernel module.
Of course after install this package everything became fine. But why you can't just add this action in script and through error only if installation was failed. And error I can find only after cat /var/log/vboxadd-install.log }}}but I think more usefull if that kind of error will be print in console we can avoid type cat command. |
|||
| #12001 | fixed | Netfilter modules don't work on Kernel 3.11-rc1+ => Fixed in SVN | ||
| Description |
When running on Kernel 3.11-rc1 and above the kernel modules build without error and load without error. However when attempting to use them, the VM's cannot start. Also Host-only networks disappear at random and sometimes cannot be created. /etc/init.d/vboxdrv setup output: malcolm@linux-549s { ~/Downloads }$ sudo /etc/init.d/vboxdrv setup Stopping VirtualBox kernel modules done Removing old VirtualBox pci kernel module done Removing old VirtualBox netadp kernel module done Removing old VirtualBox netflt kernel module done Removing old VirtualBox kernel module done Recompiling VirtualBox kernel modules done Starting VirtualBox kernel modules done lsmod output root@linux-549s [es:1] { /home/malcolm/Downloads }# lsmod |grep vb vboxpci 27290 0 vboxnetadp 25670 0 vboxnetflt 27613 0 vboxdrv 336842 3 vboxpci,vboxnetadp,vboxnetflt dmesg entrys: [ 121.223288] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use) [ 536.755146] vboxdrv: Found 4 processor cores. [ 536.755291] vboxdrv: fAsync=0 offMin=0xd4 offMax=0xebf [ 536.755356] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [ 536.755357] vboxdrv: Successfully loaded version 4.2.16 (interface 0x001a0005). [ 536.964657] vboxpci: IOMMU not found (not registered) Error when creating host-only network: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: no such file or directory Error when starting VM with host-only networking (when host-only network interface exists): verr_intnet_flt_if_not_found It also behaves the same way for other netfilter based interface options (like bridge) |
|||

