Fedora 12 aborts during boot, Fedora 13 not

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
dmischa
Posts: 58
Joined: 20. May 2010, 12:32
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: RHEL, Fedora, Windows 7

Fedora 12 aborts during boot, Fedora 13 not

Post by dmischa »

booting Fedora 13 with 3.2.8 works without problems, with Fedora 12 it needs 2..3 trials until its running.
is there anybody out there with the same problem?
is this a known Fedora-problem?

Detlef
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Fedora 12 aborts during boot, Fedora 13 not

Post by Perryg »

What do the log files say? The reason should be noted if there is a problem. Compare the ones that do not boot to that of the one that does.
dmischa
Posts: 58
Joined: 20. May 2010, 12:32
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: RHEL, Fedora, Windows 7

Re: Fedora 12 aborts during boot, Fedora 13 not

Post by dmischa »

the diff between the VBox.log's tells me:

00:00:40.263 Audio: set_record_source ars=0 als=0 (not implem | 00:00:42.100 Audio: set_record_source ars=0 als=0 (not implem
00:00:40.263 Audio: set_record_source ars=0 als=0 (not implem | 00:00:42.101 Audio: set_record_source ars=0 als=0 (not implem
00:00:40.275 Audio: set_record_source ars=0 als=0 (not implem | 00:00:42.108 Audio: set_record_source ars=0 als=0 (not implem
.......................................................................................................> 00:01:13.276 NAT: IPv6 not supported
................. aborted ........................................................................> 00:01:13.766 NAT: DHCP offered IP address 10.0.2.15
.......................................................................................................> 00:01:13.768 NAT: DHCP offered IP address 10.0.2.15

may be not a Fedora problem.

Detlef
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Fedora 12 aborts during boot, Fedora 13 not

Post by Perryg »

It's possible the either of these (Network or Audio) could cause a problem. You can determine which one by disabling them and then enable them again one at a time. The one causes it not to boot will need to be examined. Still could be Fedora though depending on the drivers it is looking for.
dmischa
Posts: 58
Joined: 20. May 2010, 12:32
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: RHEL, Fedora, Windows 7

Re: Fedora 12 aborts during boot, Fedora 13 not

Post by dmischa »

tested:
Audio: CoreAudio + Network off ==> booted | NAT ==> booted

Network NAT + Audio off ==> booted | CoreAudioo ==> aborted
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Fedora 12 aborts during boot, Fedora 13 not

Post by Perryg »

Well it appears you have found the problem. The question I have to ask is does Fedora 12 support Core Audio? I don't have a MAC handy to see. The F12 and F13 that I have all use Pulse Audio. I would ask the Fedora Forum if this would be a problem with F12 unless someone else here that has a MAC and F12 as guests comes along to verify.
dmischa
Posts: 58
Joined: 20. May 2010, 12:32
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: RHEL, Fedora, Windows 7

Re: Fedora 12 aborts during boot, Fedora 13 not

Post by dmischa »

David Herron (http://davidherron.com/node/1027) says:

VirtualBox is a family of powerful x86 virtualization products for enterprise as well as home use.
...
6. In Audio settings turn on audio support and select "Core Audio".
...



not a good idea with 3.2.8, but with audio support turned off the problem seems to be gone

in the Ticket #7495 : Virtual machine crash with status "Aborted"
wiekus reported:
Seems this is still and with the Audio... It was reported in the Forums with F12 but this is happening on both F13 and Ubuntu 10.04 as well...
Post Reply