21:58 < grimeton> lifechamp: that's one of those mysterious errors ... i guess it's gone after you shut all the vms down and rebooted the host 21:58 < lifechamp> hmm.. i'll give it a try 22:00 < grimeton> sometimes i get segfaults in my guests - ending the vm, starting it again and i still get the same segfaults 22:00 < grimeton> ending it, starting another vm and then the "broken" one and all starts to work again 22:00 < grimeton> no matter why 22:01 < lifechamp> oops, i only saved the states of the vms, and didn't power them down.. might not fix then huh? 22:02 < lifechamp> (before my windows host reboot just now) 22:02 < lifechamp> well, we'll see 22:02 < grimeton> lifechamp: if it is what i think it is, it's a messed up memory problem on the host, so rebooting the host should fix it 22:02 < lifechamp> grimeton: doesn't the fact that only past a certain snapshot of the bad vm does any of this happen? 22:03 < grimeton> lifechamp: that would mean that the php install changed something on the system's settings ... 22:03 < grimeton> that's weird 22:03 < grimeton> i don't say it's not possible, but in my experience ... 22:03 < lifechamp> OTOH, its weird that, iirc, it was black screen when powered in one order, and network adaptor if the other.. but i'd have to repeat that a few times to say that with more certainty 22:04 < lifechamp> grimeton: they had sudo rights to a few things.. like, hmm.. sudoedit httpd.conf, restart, mysql restart, and rights to run a certain FMS install script as root 22:04 < grimeton> fms? 22:04 < lifechamp> FlashMediaServer 22:05 < lifechamp> and.. sudo cron -u -e 22:05 < grimeton> yeah but all that shouldn't change the kernel's behaviour 22:05 < lifechamp> nope 22:05 < grimeton> and especially not vboxs' behaviour as it is on the host system and hasn't been touched at all 22:05 < grimeton> and only saving the state is something the kernel is not even part of 22:05 < grimeton> the execution is stopped, the memory is dumped to disk, that's it 22:06 < lifechamp> aha! bad one *start*ed just frine 22:06 < grimeton> you run the guest utilities inside those vms? 22:06 < lifechamp> i don't think i've run those utilities here, no. i actually don't see the option to do so.. haven't used vbox much yet 22:07 < lifechamp> oh, devices->install guest additions? 22:07 < grimeton> they usually come as part of the guest's packaging system 22:07 < grimeton> yeah or by the guestaddition.iso 22:07 < grimeton> check if there are packages in the package manager of the guest 22:07 < grimeton> it's the "cleaner" way imho 22:07 < lifechamp> ...and.. their script isn't broken anymore either 22:08 < grimeton> script? not broken anymore? 22:08 < lifechamp> ya, there were bugs in their script before when the 'bad' vm was 'bad 22:08 < grimeton> yeah memory issues 22:08 < lifechamp> i mean, the site didn't behave properly (even after reboot). now it does 22:09 < grimeton> hm yeah 22:09 < grimeton> memory problems 22:09 < grimeton> the problem i have is that i am not able to reproduce it 22:09 < lifechamp> "package manager"? do i need to go dig around in the vbox dir on windows for that? 22:09 < grimeton> i see it 22:09 < grimeton> every now and then but i can't reproduce it to file a bug report 22:09 < grimeton> lifechamp: the package manager is like rpm (yum), dpkg (apt-get) or the pkg* tools on bsd 22:12 < grimeton> lifechamp: does the std work now? 22:12 < lifechamp> std? 22:12 < grimeton> save to disk 22:13 < lifechamp> err.. you mean "store machine state" then "start" machine? yes, works fine, no prob 22:13 < grimeton> great 22:14 < grimeton> i guess i'll file a bug report then without the possibility to reproduce it 22:16 < lifechamp> hrm.. having good virtualization software is more important than i thought 22:16 < lifechamp> I thought it was just features and speed, and not so much serious bugs : ) 22:16 < grimeton> i'm certain it will be fixed pretty soon 22:16 < grimeton> the problem is to reproduce it 22:17 < lifechamp> ya