Custom Query (16363 matches)
Results (1141 - 1143 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10963 | obsolete | [Bridged networking] Guest machine loses connectivity after a while | ||
| Description |
Everything works just fine after boot : the guest has internet access, and anyone on the host's subnet can ping the guest. Here's the list of IP addresses :
Initially, anyone here can ping anyone. Of course it's not limited to ICMP traffic, any IP packet can be exchanged just fine between any of those hosts. And the router doing its job, with anyone on the internet too. Now here's the issue: after waiting a random amount of time (between an hour and a day), the guest partially loses network connectivity. It can actually still send IP traffic to the host, but everything else will fail. Namely, pinging anyone else on the host's subnet will fail, pinging the router will fail, and obviously any internet traffic will fail. So, in terms of IP addresses, 192.168.0.2 can exchange IP traffic with, and only with 192.168.0.3. Traffic between hosts other than the guest still works just fine. Here are some interesting facts :
|
|||
| #5421 | fixed | Bluescreen on Windows 7 64Bit when resuming from standby -> fixed in SVN | ||
| Description |
Hot is: Windows 7 Ultimate 64bit VirtualBox Version: 3.0.10 Windows XP Home as Guest going into Standby, then resuming the host gives a Bluescreen: KMODE_EXCEPTION_NOT_HANDLED (1e) Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffffa80086b832a, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: ffffffffffffffff, Parameter 1 of the exception FAULTING_IP: +0 fffffa80`086b832a f30fc73424 vmxon qword ptr [rsp] EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: ffffffffffffffff DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: VirtualBox.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002d0ea17 to fffff80002ccef00 |
|||
| #10753 | duplicate | Taking snapshot of running system produces assertion error | ||
| Description |
I am running VirtualBox 4.1.18 on a Linux host, with a Linux guest. If I try to take a snapshot from the command line when the VM is running, I get the following assertion errors: Message from syslogd@localhost at Jul 12 10:58:05 ... kernel:[6742275.026319] Message from syslogd@localhost at Jul 12 10:58:05 ... kernel:[6742275.026320] !!Assertion Failed!! Message from syslogd@localhost at Jul 12 10:58:05 ... kernel:[6742275.026321] Expression: <NULL> Message from syslogd@localhost at Jul 12 10:58:05 ... kernel:[6742275.026322] Location : /home/vbox/vbox-4.1.18/src/VBox/VMM/VMMAll/PGMAllBth.h(1458) void pgmR0BthAMD64AMD64SyncPageWorkerTrackDeref(VMCPU*, PGMPOOLPAGE*, RTHCPHYS, uint16_t, RTGCPHYS) Message from syslogd@localhost at Jul 12 10:58:05 ... kernel:[6742275.026489] HCPhys=0000000127ae6000 wasn't found! If the VM is not running, I can take the snapshot without a problem. I am running from VBoxHeadless. |
|||

