On Fri, 2008-05-23 at 11:18 -0400, Brian J. Murrell wrote:
> Ahh. But as I've said, I'm not even trying to start a VM yet, so I
> don't think this is yet relevant is it? This hang is simply from trying
> to start the main "VirtualBox" process.
I've got VirtualBox OSE running smoothly on i386 an
On Fri, 2008-05-23 at 17:27 +0200, Frank Mehnert wrote:
>
> Oh! I missed that. Could you do a full stracd with
>
> strace -f -o ~/log -s128 VirtualBox
Not necessary now. :-)
> Make sure that no VBoxSVC processes running before you start.
That was the key. Once I killed that, everything sta
On Friday 23 May 2008, Brian J. Murrell wrote:
> Ahh. But as I've said, I'm not even trying to start a VM yet, so I
> don't think this is yet relevant is it? This hang is simply from trying
> to start the main "VirtualBox" process.
Oh! I missed that. Could you do a full stracd with
strace -f
On Friday 23 May 2008, Brian J. Murrell wrote:
> On Fri, 2008-05-23 at 16:53 +0200, Frank Mehnert wrote:
> > Any hardware acceleration active?
>
> Such as? Do you mean overclocking, etc.? None of that.
I mean VT-x or AMD-V for that particular VM (see VM settings).
> > KVM active
> > on the host
On Fri, 2008-05-23 at 17:14 +0200, Frank Mehnert wrote:
> On Friday 23 May 2008, Brian J. Murrell wrote:
> > On Fri, 2008-05-23 at 16:53 +0200, Frank Mehnert wrote:
> > > Any hardware acceleration active?
> >
> > Such as? Do you mean overclocking, etc.? None of that.
>
> I mean VT-x or AMD-V for
On Fri, 2008-05-23 at 16:53 +0200, Frank Mehnert wrote:
>
> Any hardware acceleration active?
Such as? Do you mean overclocking, etc.? None of that.
> KVM active
> on the host?
I don't believe so.
> Unload the kernel module.
lsmod | grep kvm returns nothing. Here's my module stack:
Module
On Friday 23 May 2008, Brian J. Murrell wrote:
> On Fri, 2008-05-23 at 16:10 +0200, Frank Mehnert wrote:
> > please could you open a bug report and attach the VBox.log file?
>
> Given that this hang is simply trying to start the main VirtulBox
> process (i.e. not a VM), which VBox.log file is relev
On Fri, 2008-05-23 at 16:10 +0200, Frank Mehnert wrote:
> Brian,
Hi Frank,
> please could you open a bug report and attach the VBox.log file?
Given that this hang is simply trying to start the main VirtulBox
process (i.e. not a VM), which VBox.log file is relevant?
> Does this occur every time?
Brian,
On Friday 23 May 2008, Brian J. Murrell wrote:
> VirtualBox (1.5.6-28266_Ubuntu_gutsy) seems to be hanging on startup on
> my Hardy machine. The last few lines of strace say:
>
> [...]
please could you open a bug report and attach the VBox.log file?
Does this occur every time? And what gu
VirtualBox (1.5.6-28266_Ubuntu_gutsy) seems to be hanging on startup on
my Hardy machine. The last few lines of strace say:
[pid 30625] futex(0x833d430, 0x81 /* FUTEX_??? */, 1) = 0
[pid 30625] poll([{fd=7, events=POLLIN|POLLOUT, revents=POLLOUT}, {fd=8,
events=POLLIN}], 2, -1) = 1
[pid 30625] s
10 matches
Mail list logo