Custom Query (16363 matches)
Results (58 - 60 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18171 | fixed | wrong RCODE from DNS AAAA query with --natdnshostresolver1 (with suggested fix) => Fixed in SVN | ||
| Description |
The natdnshostresolver returns NOTIMP (rcode 4) on AAAA queries. This causes 5 seconds delays with musl libc, which similar to Go's stupresolver does both A and AAAA queries on hostname lookups. Problem was reported to Alpine Linux and to the musl libc mailing list, where the response was that this is is a bug in VirtualBox. Example tcpdump: 22:34:45.724471 IP 10.0.2.15.52190 > 10.0.2.3.53: 27848+ A? www.google.com. (32) 22:34:45.724542 IP 10.0.2.15.52190 > 10.0.2.3.53: 28141+ AAAA? www.google.com. (32) 22:34:45.812045 IP 10.0.2.3.53 > 10.0.2.15.52190: 27848 1/0/0 A 216.58.194.164 (48) 22:34:45.812068 IP 10.0.2.3.53 > 10.0.2.15.52190: 28141 NotImp 0/0/0 (32) 22:34:48.228641 IP 10.0.2.15.52190 > 10.0.2.3.53: 28141+ AAAA? www.google.com. (32) 22:34:48.228965 IP 10.0.2.3.53 > 10.0.2.15.52190: 28141 NotImp 0/0/0 (32) According RFC 1035:
The fix is to return RCode_NXDomain instead of RCode_NotImp: 402 if ( qtype != Type_A
403 && qtype != Type_CNAME
404 && qtype != Type_PTR
405 && qtype != Type_ANY)
406 {
407 LogErr(("NAT: hostres: unsupported qtype %d\n", qtype));
408 return refuse(pData, m, RCode_NotImp);
409 }
|
|||
| #9193 | obsolete | writing to shared folder errors with 'Protocol error' when 'VBoxControl sharedfolder list' runs | ||
| Description |
On a Windows 7 host, using VirtualBox 4.0.10 (also happened with 4.0.8), I have an Ubuntu Lucid host running (kernel 2.6.32-28-generic), with the corresponding guest additions. Scenario:
I'm using 'dd' to be able to reproduce a more general problem. Copying or moving a big enough file to the shared folder results in the same error message when the 'VBoxControl sharedfolder list' command is run before the copy/move operation is finished. The error was first observed from within a Terminal server session running in the Ubuntu guest, copying a large file to the shared folder. The error is also reproducible with a Gentoo Linux guest (kernel 2.6.35-gentoo-r15, with outdated guest additions (3.2.12)). When this error occurs, there is no change in the VBox.log file of the VM session. |
|||
| #939 | fixed | write to floppy bug => Fixed in 1.5.4 | ||
| Description |
I think this is a bug in VirtualBox. VB is inverting the write-protect flag from the floppy. You will find if you write-protect the disc, your guest will now be able to "write" to it, and will probably even show the written files in the file manager for a while. Of course, it cannot really write to the disc; only to the buffer, and sooner or later your host will try to flush the buffer and the game will be up. At least, that's what happens to me, whether using a Linux guest or a Windows one. this is rather simple to solve CU PS:the above text was copied from the forum and tested by myself... it is a really stupid but most disabling bug ;) |
|||

