VirtualBox

Ticket #1925 (closed defect: fixed)

Opened 6 years ago

Last modified 5 years ago

Ubuntu 8.04 guest segfault on Shutdown

Reported by: jblackhall Owned by:
Priority: minor Component: other
Version: VirtualBox 1.6.4 Keywords:
Cc: Guest type: Linux
Host type: other

Description

I currently am running Ubuntu 8.04 as both a host and guest on VB 1.6.4 PUEL. Overall things are running very well. If I boot up my Ubuntu 8.04 guest, the gdm login screen loads. If I choose Options -> Shutdown from there, I get a segfault near the end of the shutdown process. But rather if I decide to continue, log in, and then shut down normally, the shutdown process works fine. Furthermore, if I log in, then log back out to GDM, and then choose Options -> Shutdown, the shutdown process works fine. I seem to only get this segfault when I perform a shut down without having first logged in.

This is my first but report for VBox, so I have no idea what I need to submit as far as log files go. I'd be happy to help by submitting any info you might need though. Just let me know what you'd like.

Attachments

testing-2008-08-08-20-14-42.log Download (37.0 KB) - added by jblackhall 6 years ago.
testing-2008-08-08-20-16-09-powerdown.log Download (45.3 KB) - added by jblackhall 6 years ago.
Same as other attachment except after I completed a manual power down
testing-2008-08-10-23-45-09.log Download (45.4 KB) - added by jblackhall 6 years ago.
with VT-x enabled
testing-2008-08-11-11-23-40.log Download (44.1 KB) - added by jblackhall 6 years ago.
without VT-x, same thing happens

Change History

comment:1 Changed 6 years ago by frank

Thanks for this detailed report. Just to make sure: The SEGFAULT occurs in the guest, right? Please could you attach your VBox.log file of such a session when the SEGFAULT occurred? It can be found in the main selector menu / Machine / Show Log. Make sure that you actually attach the correct log file as a new log file is created for every new session and the old ones are renamed to VBox.log.0 ...

Changed 6 years ago by jblackhall

Changed 6 years ago by jblackhall

Same as other attachment except after I completed a manual power down

comment:2 Changed 6 years ago by jblackhall

There you go. Hopefully that's what you were looking for. The segfault causes the shutdown to freeze, so I did a "refresh" in the log right after that occurred and saved it. I also did one after a manual power down. And yes the segfault's in the guest. If the logs are not right or if you need something else, let me know.

comment:3 Changed 6 years ago by frank

Thanks for these logs. Please could you try what happens if you start the VM with VT-x enabled for this VM (VM settings)?

comment:4 Changed 6 years ago by jblackhall

Sure, I'm actually pretty sure that I had it on before. Since I'm not 100% sure, I went ahead an checked everything and I'm attaching another log. VT-x is enabled in my BIOS, in File -> Preferences, and in Machine -> Settings -> Advanced. Is it showing up as not enabled?

Changed 6 years ago by jblackhall

with VT-x enabled

comment:5 Changed 6 years ago by frank

My fault, actually all logs show that VT-x is enabled. So please could you check if the behavior is different if you disable VT-x for that session?

Changed 6 years ago by jblackhall

without VT-x, same thing happens

comment:6 Changed 6 years ago by jblackhall

Whoops, I forgot to let you know I'd attached that log without VT-x enabled yesterday

comment:7 Changed 6 years ago by frank

  • Guest type changed from other to Linux

Thanks for the log. No obvious problem visible. I start to think that this is a problem of the guest image. Can you make sure that your guest Ubuntu is up-to-date? Can you perform a disk check of your guest image (tune2fs -C10000 /dev/sda1 or something like that + reboot)?

comment:8 Changed 6 years ago by jblackhall

I ended up having to re-install my guest Ubuntu. So I deleted the VM and the virtual disk. The error is still occurring after a fresh install on a fresh virtual disk. I tried sudo tune2fs -C10000 /dev/sda1, but it didn't appear to "check" anything (seemed more like it just made a simple change. I was supposed to run that command in the Guest OS, correct?

Also, I guess I should probably mention that I have the new KDE 4.1 Kubuntu installed alongside the regular GNOME desktop. Could that be causing any sort of issue? I haven't tried this yet without Kubuntu also installed.

comment:9 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Actually still no idea. Does this problem still occur with VirtualBox 2.2.4 or VirtualBox 3.0.0? If so, please reopen.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use