Custom Query (16363 matches)
Results (772 - 774 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16039 | fixed | terminated unexpectedly during startup with exit code -1073741819 (0xc0000005) | ||
| Description |
Failed to open a session for the virtual machine WinXP 32-bit. The virtual machine 'WinXP 32-bit' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\.......\VirtualBox VMs \WinXP 32-bit\Logs\VBoxHardening.log'. Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0} 1) Host OS and version 2) VBoxStartup.log (zipped) [from VBox 5.0.6 this file is now called "VBoxHardening.log"] 3) Mention any host anti-virus, firewalls, protection software, and debugging programs etc which might be relevant. 1 - Host OS and version = Windows 7 Professional SP1 Microsoft Windows [Version 6.1.7601] |
|||
| #8659 | fixed | tcpdump not seeing vboxnet0 | ||
| Description |
It might be related to bug #8076. I have NAT and vboxnet0 (host only) setup between MacOSX 10.6.7 (host) and XP SP3 (Guest with tools installed) on Host:
1.fw0 2.en0 3.en1 4.lo0 ifconfig shows vboxnet0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
|
|||
| #8076 | fixed | tcpdump not logging packets to guests => Fixed in SVN | ||
| Description |
I was running guests with host only networking on VirtualBox 4.0 on top of a 64bit Ubuntu 10.04 machine installed from the virtualbox repository. I attempted to capture traffic on on the vboxnet0 interface using
This problem does not occur in the |
|||

