was there any network hiccup? Suddently my VPS disconnected from everywhere same here and arpnetworks.com was inaccessible at points yeah I take it something odd happened here between 6:55 and 7:15 ? my boxes couldn't ping themselves nagios alerts that they also couldn't send. :( and yet, they remained up and running I hate that when that happens. :) seems like network hiccup well - the virtual world broke not sure if it was nets or something else i maintained irc to efnet but not to freenode maybe you just didn't PING out I hat when that happens hate* My VMs on different hosts retained connectivity to each other. But inbound IP failed. Maybe just a routing blip. well, not being able to ping myself is odd although I'm pinging my public IP, not 127.0.0.1 Well, a hiccup every few months I can live with Compare to how amazon will just let your EC2 instances reboot w/o telling you jack maybe they don't have live migration so they have to reboot to push you to a new box opennebula supports live migration for VMs that do it *and* has an EC2-compatible API can't wait for retail services based on opennebula Nice. Too bad they have an awful name. ... and website. the tools are funny ... "oneTHIS" and "oneTHAT" one = Open NEbula Ha. oneimage blah blah onevm blah blah onehost blah blah wonder if i got locked out because it was time to give arp my new credit card info after bank deactivated old one, or if it's something unrelated sure was an effective way of getting me to go see that i had a 2 day old email asking for my new billing info i'm guessing it's coincidence. well-timed coincidence <3 arp networks. and the 10 billion ipv6 addresses they allocated me. hah I'm about to see if my resizing instructions work :) gpart recover ad0; gpart resize -i 3 ad0 Hmm. I'm not getting good VNC on my server and it's not hard-stopping :( I wonder if the disk resize takes time up_the_irons - you around? ahh - reconnected, and I seem to be still stuck in the state after the cdrom boot. ugh this isn't how it worked in vmware. :( I just wish I knew what error messages the KVM was spitting out ahh finally - cdrom booted! crap - my keyboard isn't seen :( yeay - fixit shell launched crap... the freebsd 8.2 gpart doesn't have the right resize command :( so now I'm paying for disk I can't use I must've been using a more modern gpart randalschwartz: freebsd needs to invent bsd.rd er I mean borrow it from openbsd randalschwartz: surely you can redirect a cdrom boot to serial for better interactivity ;-)