VirtualBox

Ticket #11481: irlog.txt

File irlog.txt, 3.9 KB (added by Grimeton, 12 years ago)

IRC Log of #vbox

Line 
121: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
221:58 < lifechamp> hmm.. i'll give it a try
322:00 < grimeton> sometimes i get segfaults in my guests - ending the vm, starting it again and i still get the same segfaults
422:00 < grimeton> ending it, starting another vm and then the "broken" one and all starts to work again
522:00 < grimeton> no matter why
622:01 < lifechamp> oops, i only saved the states of the vms, and didn't power them down.. might not fix then huh?
722:02 < lifechamp> (before my windows host reboot just now)
822:02 < lifechamp> well, we'll see
922: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
1022:02 < lifechamp> grimeton: doesn't the fact that only past a certain snapshot of the bad vm does any of this happen?
1122:03 < grimeton> lifechamp: that would mean that the php install changed something on the system's settings ...
1222:03 < grimeton> that's weird
1322:03 < grimeton> i don't say it's not possible, but in my experience ...
1422: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
1522: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
1622:04 < grimeton> fms?
1722:04 < lifechamp> FlashMediaServer
1822:05 < lifechamp> and.. sudo cron -u <user> -e
1922:05 < grimeton> yeah but all that shouldn't change the kernel's behaviour
2022:05 < lifechamp> nope
2122:05 < grimeton> and especially not vboxs' behaviour as it is on the host system and hasn't been touched at all
2222:05 < grimeton> and only saving the state is something the kernel is not even part of
2322:05 < grimeton> the execution is stopped, the memory is dumped to disk, that's it
2422:06 < lifechamp> aha! bad one *start*ed just frine
2522:06 < grimeton> you run the guest utilities inside those vms?
2622: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
2722:07 < lifechamp> oh, devices->install guest additions?
2822:07 < grimeton> they usually come as part of the guest's packaging system
2922:07 < grimeton> yeah or by the guestaddition.iso
3022:07 < grimeton> check if there are packages in the package manager of the guest
3122:07 < grimeton> it's the "cleaner" way imho
3222:07 < lifechamp> ...and.. their script isn't broken anymore either
3322:08 < grimeton> script? not broken anymore?
3422:08 < lifechamp> ya, there were bugs in their script before when the 'bad' vm was 'bad
3522:08 < grimeton> yeah memory issues
3622:08 < lifechamp> i mean, the site didn't behave properly (even after reboot). now it does
3722:09 < grimeton> hm yeah
3822:09 < grimeton> memory problems
3922:09 < grimeton> the problem i have is that i am not able to reproduce it
4022:09 < lifechamp> "package manager"? do i need to go dig around in the vbox dir on windows for that?
4122:09 < grimeton> i see it
4222:09 < grimeton> every now and then but i can't reproduce it to file a bug report
4322:09 < grimeton> lifechamp: the package manager is like rpm (yum), dpkg (apt-get) or the pkg* tools on bsd
4422:12 < grimeton> lifechamp: does the std work now?
4522:12 < lifechamp> std?
4622:12 < grimeton> save to disk
4722:13 < lifechamp> err.. you mean "store machine state" then "start" machine? yes, works fine, no prob
4822:13 < grimeton> great
4922:14 < grimeton> i guess i'll file a bug report then without the possibility to reproduce it
5022:16 < lifechamp> hrm.. having good virtualization software is more important than i thought
5122:16 < lifechamp> I thought it was just features and speed, and not so much serious bugs : )
5222:16 < grimeton> i'm certain it will be fixed pretty soon
5322:16 < grimeton> the problem is to reproduce it
5422:17 < lifechamp> ya
55

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy