VirtualBox

Opened 14 years ago

Closed 8 years ago

#7082 closed defect (obsolete)

Fatal error when executing Virtual Appliance

Reported by: half12 Owned by:
Component: OVF Version: VirtualBox 3.2.6
Keywords: InfoBlox VM5 VM25 Cc:
Guest type: Linux Host type: Solaris

Description (last modified by aeichner)

I have successfully imported the InfoBlox VM5 and VM25 virtual appliances, when I run these virtual appliances however they boot proceed for a while and then report a fatal error.

I have attached a number of Vbox.log files, when I tried changing the hardware virtualisation settings which can effect the running of VMs

Attachments (2)

virtualappliance.png (273.2 KB ) - added by half12 14 years ago.
Screen grab of running infoblox virtual appliance error
vbox.logs.tar (237.0 KB ) - added by half12 14 years ago.
VBox log instances after changing VB virtualisation settings

Download all attachments as: .zip

Change History (6)

by half12, 14 years ago

Attachment: virtualappliance.png added

Screen grab of running infoblox virtual appliance error

by half12, 14 years ago

Attachment: vbox.logs.tar added

VBox log instances after changing VB virtualisation settings

comment:1 by michaln, 14 years ago

I have no experience with Infoblox, but AFAICS the VM has VMware Tools and vmxnet drivers installed. These drivers do *not* work with plain PCnet adapters which VirtualBox emulates, therefore the VM will have no connectivity. That's not something we can fix, you have to modify the appliance.

You would also have to ask Infoblox (not us) what the error messages really mean.

comment:2 by half12, 14 years ago

Thanks for the information, all I need to do is figure out how to remove the VMware tools and add the VirtualBox tools instead :) Given that you can import a Virtual Appliance is there any point is asking for vmxnet emulation within VirtualBox feature request? This would be away of increasing the number of Virtual Appliances that VirtualBox would support.

comment:3 by michaln, 14 years ago

Strictly speaking you don't need to add the VirtualBox Guest Additions, and you don't even need to completely remove the VMware Tools. You only need to remove the VMware vmxnet NIC drivers.

The issue here is that VMware Tools installed the vmxnet drivers for VMware's paravirtualized NIC. There are two problems with that. First, to the guest OS the vmxnet PCI device looks just like a regular PCnet adapter, so the OS will not reconfigure the NIC drivers when moving from VMware to VirtualBox (or to a real system with a PCnet adapter). Second, VMware's vmxnet driver can only control the vmxnet paravirtualized NIC, not a regular PCnet adapter. The upshot is that the guest OS thinks the correct driver is installed, but that driver doesn't actually work.

comment:4 by aeichner, 8 years ago

Description: modified (diff)
Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use