Custom Query (16363 matches)
Results (1399 - 1401 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15579 | fixed | Bug in VBoxLinuxAdditions.sh 5.0.24_108355 | ||
| Description |
Tracked down failures to install guest additions on CentOS 7. Symptom was constant syslogs: dracut: Can't write to /boot/initramfs-: Directory /boot/initramfs- does not exist or is not accessible. Upon rebooting, the system would be unbootable and required a rescue disk. problem is on line 1042 of VBoxLinuxAdditions.sh: for i in /lib/modules/*; do
update_module_dependencies "${i#/lib/modules}"
done
running the following code illustrates the problem: # for i in /lib/modules/*; do
echo update_module_dependencies "${i#/lib/modules}"
done
update_module_dependencies /3.10.0-327.22.2.el7.x86_64
the correct code puts a trailing '/' after 'modules': for i in /lib/modules/*; do
update_module_dependencies "${i#/lib/modules/}"
done
To workaround this bug, do the following: (mount GuestAdditions CD Image, cd to top level of CDROM). # sh ./VBoxLinuxAdditions.sh (errors - define the following shell function taken from the script) # update_module_dependencies()
{
depmod "${1}"
test -d "/lib/modules/${1}/initrd" &&
touch "/lib/modules/${1}/initrd/vboxvideo"
test -n "${QUICKSETUP}" && return
if type dracut >/dev/null 2>&1; then
dracut -f "/boot/initramfs-${1}.img"
elif type update-initramfs >/dev/null 2>&1; then
update-initramfs -u -k "${1}"
fi
}
# for i in /lib/modules/*; do
update_module_dependencies "${i#/lib/modules/}"
done
(the following files seem to be leftover and prevent my system from booting, delete them). # rm -rf /var/lib/VBoxGuestAdditions |
|||
| #7792 | obsolete | Bug in host side network driver - vboxnetflt | ||
| Description |
This bug has existed for quite a long time and is a subtle thing that may have been easily missed by many, but here goes: If on the host you have a network interface - say, eth0 in this example - and you configure an IP address on this interface on the host. If you then start a guest that is bridged to this adapter, packets going from the guest to the host's IP behave as expected, but reply packets from the host to the guest are sent out the physical medium instead of just being bridged internally. The result is the following: Packets flowing from the host to the guest, hit the physical media, which typically is a network switch. If the guest is not talking to any host on the network other that the host it's running on, the switch will flood the packets to all ports in the lan since the switch doesn't know where the source is (inside the host in this case). I have been able to verify this in 3.2.12 and the test is pretty simple, as follows: Set up 2 pc's with a network crossover cable between them. The first PC will be the 'host', and running virtualbox. The second will simply run TCPDUMP to inspect traffic sent over the ethernet cable. Give the host's ethernet in this test and IP address, say 10.1.1.1. Setup a guest instance on the host and give it an ethernet that is bridged to this adaptor. Log into the guest and configure an ip on it's interface, such as 10.1.1.2 From the guest, start a ping - ping 10.1.1.1 Over on the second PC running tcpdump, you will observe the initial arp request (correct operation), and then you will see ICMP echo replys sourced from the host directed at the guest (incorrect operation). These packets are flooded to the network when in reality, the should not be since the destination mac address is a local guest. I have tried putting the hosts's ethernet into a bridge interface, thinking that would stop the frames from leaving the host, but I was suprised to learn that they are still sent out of the physical ethernet despite the bridge knowing the mac of the guest. Thank you for virtualbox. |
|||
| #18672 | invalid | Bug in the Shared Transfer Aréa. | ||
| Description |
I put it as Bi-Directional but it does not work. this problem has been happening for some time. The Host Operating System using it is Windows 10 64 Bit. the Guest Virtual System is also Windows 10 64 Bit. The Virtual Box used is the Latest Version 6.0.8 r130520 |
|||

