Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#44550 - [virtualbox] Segmentation fault attempting to book Arch Linux guest

Attached to Project: Community Packages
Opened by mark r (io7m) - Saturday, 11 April 2015, 16:44 GMT
Last edited by Sébastien Luttringer (seblu) - Thursday, 14 May 2015, 15:22 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Immediate segmentation fault when booting an Arch Linux guest from an Arch Linux host.

Additional info:
* package version(s)
* config and/or log files etc.

Linux viper 3.19.3-3-ARCH #1 SMP PREEMPT Wed Apr 8 14:10:00 CEST 2015 x86_64 GNU/Linux
virtualbox 4.3.26-2
virtualbox-host-modules 4.3.26-5

Entirely vanilla configuration. Whatever the defaults are!

Steps to reproduce:

1. Create new Arch Linux VM. Set memory size to 1024mb and disk to 10gb.
2. Boot from archlinux-2015.04.01-dual.iso
3. Witness immediate segfault when the kernel is uncompressed and begins to boot.

Core dump included here, because it's slightly too large to be attached (~5mb):

http://waste.io7m.com/2015/04/11/core.VirtualBox.1000.fc3870790b60476ba2ae9610627d14f8.7233.1428769974000000.lz4
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Thursday, 14 May 2015, 15:22 GMT
Reason for closing:  Works for me
Comment by mark r (io7m) - Saturday, 11 April 2015, 16:48 GMT
To clarify, that's booting from the iso image in order to install a new system. It's impossible to get more than a few seconds beyond the boot menu.
Comment by Sébastien Luttringer (seblu) - Thursday, 14 May 2015, 15:22 GMT
I'm not able to reproduce. Please contact virtualbox support directly.

Loading...