VirtualBox

Ticket #7082 (new defect)

Opened 4 years ago

Last modified 4 years ago

Fatal error when executing Virtual Appliance

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

Description

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

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

Change History

Changed 4 years ago by half12

Screen grab of running infoblox virtual appliance error

Changed 4 years ago by half12

VBox log instances after changing VB virtualisation settings

comment:1 Changed 4 years ago by michaln

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 Changed 4 years ago by half12

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 Changed 4 years ago by michaln

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.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use