Custom Query (16363 matches)
Results (2158 - 2160 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10553 | obsolete | Guest is not resized after it has booted | ||
| Description |
I started a VM and maximized it by double clicking the tilte bar during the guest boot process. Once the VM has completly booted, its guest OS is not correctly resized to window size. I have to manually resize it in order to trigger guest resize. Host: Linux 12.10 Guest Linux 12.10 |
|||
| #10554 | obsolete | OperationalError: (1213, 'Deadlock found when trying to get lock; try restarting transaction') | ||
| Description |
This doesn't look like the right place to report this (this is a bug in Trac, not in VirtualBox), but the error message directed me here: """" Oops… Trac detected an internal error: OperationalError: (1213, 'Deadlock found when trying to get lock; try restarting transaction') There was an internal error in Trac. It is recommended that you notify your local Trac administrator with the information needed to reproduce the issue. To that end, you could ((THIS LINKED HERE)) a ticket. The action that triggered the error was: GET: /login TracGuide — The Trac User and Administration Guide """" How to Reproduce
While doing a GET operation on (please provide additional details here) Request parameters: {}
User agent: System InformationSystem information not available Enabled PluginsPlugin information not available Python TracebackTraceback (most recent call last):
File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 513, in _dispatch_request
dispatcher.dispatch(req)
File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 235, in dispatch
resp = chosen_handler.process_request(req)
File "/usr/lib/python2.4/site-packages/trac/web/auth.py", line 117, in process_request
self._redirect_back(req)
File "/usr/lib/python2.4/site-packages/trac/web/auth.py", line 341, in _redirect_back
req.redirect(referer or req.abs_href())
File "/usr/lib/python2.4/site-packages/trac/web/api.py", line 358, in redirect
self.session.save() # has to be done before the redirect is sent
File "/usr/lib/python2.4/site-packages/trac/web/api.py", line 212, in __getattr__
value = self.callbacks[name](self)
File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 298, in _get_session
return Session(self.env, req)
File "/usr/lib/python2.4/site-packages/trac/web/session.py", line 166, in __init__
self.promote_session(sid)
File "/usr/lib/python2.4/site-packages/trac/web/session.py", line 225, in promote_session
@self.env.with_transaction()
File "/usr/lib/python2.4/site-packages/trac/db/api.py", line 77, in transaction_wrapper
fn(ldb)
File "/usr/lib/python2.4/site-packages/trac/web/session.py", line 236, in update_session_id
cursor.execute("""
File "/usr/lib/python2.4/site-packages/trac/db/util.py", line 65, in execute
return self.cursor.execute(sql_escape_percent(sql), args)
File "/usr/lib64/python2.4/site-packages/MySQLdb/cursors.py", line 166, in execute
self.errorhandler(self, exc, value)
File "/usr/lib64/python2.4/site-packages/MySQLdb/connections.py", line 35, in defaulterrorhandler
raise errorclass, errorvalue
OperationalError: (1213, 'Deadlock found when trying to get lock; try restarting transaction')
|
|||
| #10555 | obsolete | NAT DnsHostResolver reverse order of dns results compared to host | ||
| Description |
Because the host often needs to connect to a VPN with a local dns server, I enabled NAT DnsHostResolver (NAT DnsProxy wasn't enough) with the command: VBoxManage.exe modifyvm <vmname> --natdnshostresolver1 on It seemed to work correctly but I observed that DNS results order is reversed in a specific query I'm doing. Please note that the local dns server (192.168.101.20) is configured to answer in a specific order for this query (there's absolutely no round-robin, the result is always fixed). Host is Windows7 64-bit, guest is ubuntu 12.04 64 bit. ping + nslookup in the host (correct, sidenote: dns server 192.168.101.20 is configured to serve to vpn users the public ip first for this specific host, and not the lan ip): C:\Users\ceztko>ping hypervisor.rur.it-robotics.it
Pinging hypervisor.rur.it-robotics.it [95.240.170.248] with 32 bytes of data:
Control-C
^C
C:\Users\ceztko>nslookup
Default Server: lanmaster.it-robotics.it
Address: 192.168.101.20
> hypervisor.rur.it-robotics.it
Server: lanmaster.it-robotics.it
Address: 192.168.101.20
Name: hypervisor.rur.it-robotics.it
Addresses: 95.240.170.248
192.168.101.10
ping + nslookup in the guest (wrong, reversed): ceztko@laptopbb:~$ ping hypervisor.rur.it-robotics.it PING hypervisor.rur.it-robotics.it (192.168.101.10) 56(84) bytes of data. ^C64 bytes from 192.168.101.10: icmp_req=1 ttl=63 time=70.1 ms --- hypervisor.rur.it-robotics.it ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 70.124/70.124/70.124/0.000 ms ceztko@laptopbb:~$ nslookup > hypervisor.rur.it-robotics.it Server: 10.0.2.3 Address: 10.0.2.3#53 Name: hypervisor.rur.it-robotics.it Address: 192.168.101.10 Name: hypervisor.rur.it-robotics.it Address: 95.240.170.248 Because, as stated in the manual, "the resolver mode will interpret the DNS requests and use the host's DNS API to query the information and return it to the guest", I'm expecting the guest to see the same order of the host for this query. |
|||

