virtualbox.org

I've searched the entire internet and nothing comes up that has resolved my issue.

Randomly my XP guest aborts. It does not appear to matter if it is doing anything or nothing. I have all the power saving features turned off. I saw a discussion which suggested the bidirectional clipboard could be at fault, though that was for an older version, which didn't have any effect. There is nothing in the log at the time the guest aborts.

I am running PCLinuxOS 2013, installed Virtualbox 4.3.6 from the RPM, and upgraded to 4.3.8. I have 2gb RAM, 37Gb hard drive space reserved for the guest, Pentium4 @ 2.8Ghz.

Anybody have any ideas?

[Truncated/pasted log deleted by mod. Always post logs as .zip attachments.]

1) Never copy-paste the log file. Compress it and add it as an attachment.
2) The log is not complete, most probably due to the size of your message. Post a complete log. See 1 above.
3) Your guest additions are outdated.

Searching through the Linux logs, I found these messages that appeared at the times when the guest aborted:

klogd: EMT[17026]: segfault at 18 ip b14a552a sp b1c7ee30 error 6 in VBoxREM64.so[b1494000+c2000]
klogd: EMT[5452]: segfault at 18 ip b13a452a sp b1b7ee30 error 6 in VBoxREM64.so[b1393000+c2000]
klogd: EMT[5816]: segfault at 11 ip b144c524 sp b1bfde30 error 6 in VBoxREM64.so[b143b000+c2000]
klogd: EMT[3039]: segfault at 18 ip b12e452a sp b1bdce30 error 6 in VBoxREM64.so[b12d3000+c2000]
klogd: EMT[12961]: segfault at 7269563f ip b13b7524 sp b1bfde30 error 6 in VBoxREM64.so[b13a6000+c2000]
klogd: EMT[31646]: segfault at 11 ip b0128524 sp b1b7ee30 error 6 in VBoxREM64.so[b0117000+c2000]

And just now,
klogd: EMT[32256]: segfault at 0 ip b13a952a sp b1b7ee30 error 6 in VBoxREM64.so[b1398000+c2000]

socratis wrote:1) Never copy-paste the log file. Compress it and add it as an attachment.
2) The log is not complete, most probably due to the size of your message. Post a complete log. See 1 above.
3) Your guest additions are outdated.

re: 1) Any particular compression format?
re: 3) Guest additions?

So I am assuming guest additions must also be upgraded in the guest whenever VirtualBox is upgraded, correct?

Please post the log correctly, as requested above. Your questions can't be answered otherwise.

I've upgraded the guest add-ons, still aborting. The latest log is attached.

bump

You are not running a copy of VirtualBox from VirtualBox.org. As such there is very little anyone here can do. I would seek assistance from the rpm fusion folks as they are the ones that compile the source and make it available. You should really post a log file after an abort and before you start it again by the way. The log you posted shows no abort.

Perryg wrote:You are not running a copy of VirtualBox from VirtualBox.org. As such there is very little anyone here can do. I would seek assistance from the rpm fusion folks as they are the ones that compile the source and make it available.

Alright. I downloaded VirtualBox-4.3.10-92957-Linux_x86.run from this website as I have all previous versions, using this link http://download.virtualbox.org/virtualb ... ux_x86.run, installed along with the updated guest additions. Not to be a smart a$$, but is this a copy from Virtualbox.org that I should be using, or should I get it somewhere else?

The guest is still aborting, with nothing in the virtualbox log indicating an abort. Except,in /var/log/message...
Mar 26 11:15:46 ws135lnx klogd: EMT[5768]: segfault at 60 ip af94c524 sp b137de30 error 6 in VBoxREM64.so[af93b000+c2000]

Perryg wrote:The log you posted shows no abort.

I know that, which is why I am seeking help. Perhaps somebody here might have a clue.

Perryg wrote:You should really post a log file after an abort and before you start it again by the way.

The logs I have posted were copied after an abort and before a restart.

I do appreciate any helpful information.

I see where the confusion came in. You are installing the generic build, and compiling it yourself, thus the install in /opt. This is usually where the OSE version is installed.

This can make it as hard as using a version from someone else but let's see what we can figure out.

1) post the /var/log/vbox-install.log and if available the Xorg.0.log.
2) see if you can tell what might be causing this from the guest. Is the any one thing that you can do that will cause the abort?
3) are you sure that all the depends are installed and is dkms installed?

Since my last post I noticed another upgrade had been posted, which I installed this morning, ver 4.3.10-93012. Still aborting. DKMS is installed and up to date. As for the guest, it was idle, nothing running, all power save features and screen saver turned off.

/var/log/messages has the following entry at the time the guest aborted..
Mar 27 09:41:03 ws135lnx klogd: EMT[3512]: segfault at 18 ip af8a452a sp b137ee30 error 6 in VBoxREM64.so[af893000+c2000]
Why VBoxREM64.so when this is a 32 bit system? This what I suspect is the cause of the problem. Looking back at viewtopic.php?f=2&t=60655&p=283520#p282341, I see that the errors always point to VBoxREM64.so.

I can't find what the reason is for this, but if it does work in a previous version I would post a ticket at bugtracker posting all of this information there.

I was noticing some other issues with the host so I rebooted, the guest has been running for hours since, which is longer than it was before. But up until this latest release I had been rebooting after installation knowing that the kernel was rebuilt during install and therefore required reboot. I don't know if that is mentioned in the installation instructions, but if it does reboot is often best after installing any software any way.

I appreciate the help.