On Mon, Feb 12, 2018 at 12:38:00AM -0800, Mike Larkin wrote: > > > > it's horrible slow, just doing 'tor-resolve $dnsname' takes > > > > sometimes ages. > > > > [...] > [...] > > What did the guest pick for timecounter? (sysctl kern.timecounter.hardware) > > Your hardware is nearly a decade old. I wouldn't be surprised if vmm > picked some ancient timecounter hardware. For the example below, my guest > chose 'tsc' (I have a 2013-era Ivy Bridge CPU). All my hosts/VMs are > -current. And we know if your hardware is shit, we do the best we can but > no promises as to how precise time is going to be. With tsc timecounter, > my VMs that have been up for weeks have drifted maybe a second or two from > the host. > > [...] > > In other words, I don't see anything odd here. The vm appears to actually > be running faster than the host. I'm not concerned about the 2-3 second > difference on the first resolve. I bet if I ran it a hundred times I'd see > things pretty much the same.
Mike, thank you for your time. The VM picked 'tsc' as timecounter. Putting CC Pascal, Tor port maintainer, as I am suspicious that this slowness is related to what tor itself is doing in that time. Pascal, any idea what could cause slowness of tor when using onion service inside VMM? Info below (plus history https://marc.info/?l=openbsd-misc&m=151839235419514&w=2): Feb 12 10:30:25 onion Tor[96278]: connection_connect_sockaddr: Connection to socket established (sock 4). Feb 12 10:32:55 onion Tor[96278]: connection_edge_reached_eof: conn (fd 4) reached eof. Closing. Feb 12 10:32:55 onion Tor[96278]: Your system clock just jumped 151 seconds forward; assuming established circuits no longer work. ^^^ 2 mins gap? Tor tests, if this is general issue or not. - scenario 1 * loop date + tor-resolve $dnsname + sleep 1 * torsocks curl -s -I http://www.openbsd.org ^^ this works ok - scenario 2 make tor to have local onion service with httpd enabled * install -d -o _tor -g _tor -m 700 /var/tor/onion * modify /etc/tor/torrc: Log debug syslog HiddenServiceDir /var/tor/onion/ HiddenServicePort 80 127.0.0.1:80 * enable httpd & tor * loop date + tor-resolve $dnsname + sleep 1 * get your .onion service address cat /var/tor/onion/hostname * access your .onion service from other (tor)browser ... Feb 12 10:30:24.519 [warn] Got SOCKS5 status response '4': host is unreachable Mon Feb 12 10:30:26 CET 2018 129.128.5.194 Mon Feb 12 10:32:58 CET 2018 129.128.5.194 Mon Feb 12 10:33:00 CET 2018 ... ^^ tor-resolve $dnsnanme gets slow downed in a while, 2 mins gap Feb 12 10:30:24 onion Tor[96278]: rend_service_rendezvous_has_opened: Done building circuit 2327426966 to rendezvous with cookie D92E6387 for service xxxxxxxxxxxxxxxx Feb 12 10:30:24 onion Tor[96278]: internal circ (length 4): $0FBE018DADAB416DE17A10C5D4AD3EBF0E243561(open) $BF50E09EED25B82861CF95E1AAA42DCFEF53E5D1(open) $F80FDE27EFCB3F6A7B4E2CC517133DBFFA78BA2D(open) $CCF0E904BAD135F6B2180BD89D19E487F83786A5(open) Feb 12 10:30:24 onion Tor[96278]: connection_handle_listener_read: New SOCKS connection opened from 127.0.0.1. Feb 12 10:30:24 onion Tor[96278]: rep_hist_note_used_port: New port prediction added. Will continue predictive circ building for 1967 more seconds. Feb 12 10:30:24 onion Tor[96278]: connection_edge_process_inbuf: data from edge while in 'waiting for circuit' state. Leaving it on buffer. Feb 12 10:30:24 onion Tor[96278]: exit circ (length 3): $0FBE018DADAB416DE17A10C5D4AD3EBF0E243561(open) $594252BFEE13625AC120F50F3015CB3C1DA55690(open) $1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA(open) Feb 12 10:30:24 onion Tor[96278]: pathbias_count_use_attempt: Used circuit 2 is already in path state use succeeded. Circuit is a General-purpose client currently open. Feb 12 10:30:24 onion Tor[96278]: link_apconn_to_circ: Looks like completed circuit to [scrubbed] does allow optimistic data for connection to [scrubbed] Feb 12 10:30:24 onion Tor[96278]: connection_ap_handshake_send_resolve: Address sent for resolve, ap socket 4, n_circ_id 2260876578 Feb 12 10:30:25 onion Tor[96278]: connection_connect_sockaddr: Connection to socket established (sock 4). Feb 12 10:32:55 onion Tor[96278]: connection_edge_reached_eof: conn (fd 4) reached eof. Closing. Feb 12 10:32:55 onion Tor[96278]: Your system clock just jumped 151 seconds forward; assuming established circuits no longer work. ^^ 2 mins gap So just slow HW issue? Jiri
