VirtualBox problem running in a Solaris 10 zone

Discussions related to using VirtualBox on Solaris hosts.

VirtualBox problem running in a Solaris 10 zone

Postby enrico.m.crisostomo » 11. Aug 2008, 19:07

Hi.

I wanted to run VirtualBox, which is installed in the global zone, from a sparse zone in Solaris 10. The zone inherits the /opt directory, it inherits the /dev/vboxdrv (as specified in VBox documentation). VirtualBox seems to work but as soon as I try to start an existing virtual machine a popup with the following message appears:
Code: Select all   Expand viewCollapse view
VirtualBox kernel driver cannot be opened.
VBox status code: -1911 (VERR_VM_DRIVER_OPEN_ERROR).
Result Code: 0x80004005
Component: Console
Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}

I also discovered that running it from the zone and after this error is produces, it seems to screw something up and VBox doesn't run even in the global zone. A reboot fixes it.

Any hint about this? Isn't it possible to run VBox from a sparse Solaris 10 zone?

Bye and thank you,
Enrico
enrico.m.crisostomo
 
Posts: 4
Joined: 11. Aug 2008, 19:03

Postby atria78 » 12. Aug 2008, 19:45

I have the same problem on a Solaris 10 zone (u4 with latest patches).

I have already given the raw device access for this zone and (and rebooted), using:
add device
set match=/dev/vboxdrv
end

Is it really having problems communicating to that device OR is there a keyboard problem as mentioned below?

errno 6 is:
#define ENXIO 6 /* No such device or address */


00:00:03.355 VirtualBox 1.6.4 r33808 solaris.amd64 (Jul 29 2008 20:50:41) release log
00:00:03.355 Log opened 2008-08-12T17:38:10.444932000Z
00:00:03.357 Failed to open "/dev/vboxdrv", errno=6, rc=VERR_VM_DRIVER_OPEN_ERROR
00:00:03.357 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={d5a1cbda-f5d7-4824-9afe-d640c94c7dcf} aComponent={Console} aText={VirtualBox kernel driver cannot be opened.
00:00:03.357 VBox status code: -1911 (VERR_VM_DRIVER_OPEN_ERROR)} aWarning=false, preserve=false
00:00:03.358 Your keyboard type does not appear to be known to VirtualBox. If
00:00:03.358 you would like to help us improve the product, please submit a bug
00:00:03.358 report, attach this logfile and provide information about what type
00:00:03.358 of keyboard you have and whether you are using a remote X server or
00:00:03.358 something similar.
00:00:03.358
00:00:03.358 The tables for your keyboard are:
00:00:03.358 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1e, 0x30, 0x2e, 0x20, 0x12, 0x21, 0x22, 0x23,
00:00:03.358 0x17, 0x24, 0x25, 0x26, 0x32, 0x31, 0x18, 0x19, 0x10, 0x13, 0x1f, 0x14, 0x16, 0x2f, 0x11, 0x2d,
00:00:03.359 0x15, 0x2c, 0x2, 0x3, 0x4, 0x5, 0x6, 0x7, 0x8, 0x9, 0xa, 0xb, 0x1c, 0x1, 0xe, 0xf,
00:00:03.359 0x39, 0xc, 0xd, 0x1a, 0x1b, 0x2b, 0x0, 0x27, 0x28, 0x29, 0x33, 0x34, 0x35, 0x3a, 0x3b, 0x3c,
00:00:03.359 0x3d, 0x3e, 0x3f, 0x40, 0x41, 0x42, 0x43, 0x44, 0x57, 0x58, 0x0, 0x0, 0x0, 0x152, 0x147, 0x149,
00:00:03.359 0x153, 0x14f, 0x151, 0x14d, 0x14b, 0x150, 0x148, 0x145, 0x135, 0x37, 0x4a, 0x4e, 0x11c, 0x4f, 0x50, 0x51,
00:00:03.359 0x4b, 0x4c, 0x4d, 0x47, 0x48, 0x49, 0x52, 0x53, 0x0, 0x15d, 0x12e, 0x0, 0x0, 0x0, 0x0, 0x0,
00:00:03.359 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x175, 0x0, 0x0, 0x57, 0x58, 0x0, 0x0,
00:00:03.360 0x0, 0x0, 0x0, 0x130, 0x0, 0x120, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
00:00:03.360 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
00:00:03.360 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
00:00:03.360 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
00:00:03.360 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
00:00:03.361 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
00:00:03.361 0x0, 0x0, 0x0, 0x0, 0x1d, 0x2a, 0x38, 0x38, 0x0, 0x36, 0x138, 0x138, 0x0, 0x0, 0x0, 0x0,
00:00:03.361 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0
00:00:03.361 and
00:00:03.361 NULL, 0xe4, 0xe5, 0x3d, 0x2f, 0x2d, 0x2c, 0x56, 0x55,
00:00:03.361 0x54, 0x53, 0x3e, 0x3f, 0x40, 0x41, 0x42, 0x43, 0x44, 0x45
00:00:03.365 Power up failed (vrc=VERR_VM_DRIVER_OPEN_ERROR, hrc=NS_ERROR_FAILURE (0X80004005))
atria78
 
Posts: 3
Joined: 12. Aug 2008, 19:39


Return to VirtualBox on Solaris Hosts

Who is online

Users browsing this forum: No registered users and 2 guests