Ubuntu 9.04 segfaults when connecting over TCP with NAT

[pdinoto]

Hello fine people!

I happily installed Vbox 2.2.2 r46594 on Core2 Quad (Q9400) with Ubuntu 9.40 amd64.
Created a VM with 512mb of RAM (out of 4gb in the host), and installed another Ubuntu 9.04 32bits to use as a streaming server.

Right now, we have a temporary internet connection, so the host is connected to an ADSL line and does PPPoE to access the internet.
The VM is using NAT. In order to access it, I did

Code: Select all

vbox@ccm-vmsrv1:$ VBoxManage getextradata d8928519-97f2-421a-9c15-fa2b3700c4a0 enumerate
VirtualBox Command Line Management Interface Version 2.2.2
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

Key: GUI/SaveMountedAtRuntime, Value: yes
Key: VBoxInternal/Devices/e1000/0/LUN#0/Config/guestssh/HostPort, Value: 2234
Key: VBoxInternal/Devices/e1000/0/LUN#0/Config/guestssh/GuestPort, Value: 22
Key: VBoxInternal/Devices/e1000/0/LUN#0/Config/guestssh/Protocol, Value: TCP
Key: VBoxInternal/Devices/e1000/0/LUN#0/Config/icecast/HostPort, Value: 8000
Key: VBoxInternal/Devices/e1000/0/LUN#0/Config/icecast/GuestPort, Value: 8000
Key: VBoxInternal/Devices/e1000/0/LUN#0/Config/icecast/Protocol, Value: TCP

I can access the SSH server on the guest, and also the icecast2 server by using a browser. But when I actually connect a media player (which uses the very same port and protocol), the guest crashes. BTW, I moved the same icecast config to the host, and it works seamlessly from there.

At segfault, all I see on the console is:

Code: Select all

vbox@ccm-vmsrv1:~$ VBoxHeadless -startvm d8928519-97f2-421a-9c15-fa2b3700c4a0
VirtualBox Headless Interface 2.2.2
(C) 2008-2009 Sun Microsystems, Inc.
All rights reserved.

Listening on port 3389
Segmentation fault

Nothing useable on the logs, no other info I could find.
How can I start a VM with more verbose logging?
How to produce output that support can look into?

Thanks for getting this far

I would love to help debugging this.
Cheers,
///Pablo

[pdinoto]

I wonder if there is no way to get more debug, or my thread got lost.

Cheers,
///Pablo

[Perryg]

I honestly have nothing to add. And since no one else has made any suggestions it must be beyond our ability to help. Have you tried to see what the Ubuntu group has to say about it.

Your next avenue if you believe this to be a VBox issue would be to start a ticket on this at bugtracker. You will need to setup an account there though as it is on a different backend. The link is at the bottom of my post. Remember that you will need to send the VBox log or they probably will not read it.