VirtualBox 5.0.4 crashes Solaris 11.3 beta

Discussions related to using VirtualBox on Solaris hosts.

VirtualBox 5.0.4 crashes Solaris 11.3 beta

Postby kloczek » 11. Sep 2015, 14:29

https://forums.virtualbox.org/viewtopic ... 11&t=70075 is now locked so I'm sending new new topic.

Exactly the same end result as with 5.0.0 RC1.
Last edited by kloczek on 12. Sep 2015, 17:14, edited 1 time in total.
kloczek
 
Posts: 14
Joined: 9. Sep 2015, 15:35

Re: VirtualBox 5.0.4 crashes Solaris 11.3 beta

Postby kloczek » 11. Sep 2015, 14:57

Just rebooted with -k in kernel command line and after yet another crash

Code: Select all   Expand viewCollapse view
root@bootstrap:/var/crash/0# savecore 0
savecore: System dump time: Fri Sep 11 12:32:08 2015

savecore: Saving decompressed system crash dump files in directory /var/crash/data/283f0a4f-dc0b-416e-b6f9-cdabb43bf5c1
Constructing corefile /var/crash/data/283f0a4f-dc0b-416e-b6f9-cdabb43bf5c1/vmcore.0
 0:14 100% done (679771 pages): 679771 of 679771 pages saved
Constructing corefile /var/crash/data/283f0a4f-dc0b-416e-b6f9-cdabb43bf5c1/vmcore-zfs.0
 0:00 100% done (18986 pages): 18986 of 18986 pages saved
root@bootstrap:/var/crash/0# mdb 0
Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc pcplusmp
zvpsm scsi_vhci iommu zfs sd ip hook neti arp usba uhci kssl sockfs lofs random
idm cpc crypto fcip fctl nfs zvmm ufs logindmux ptm sppp ]
> ::status
debugging crash dump vmcore.0 (64-bit, non-DEBUG) from bootstrap
operating system: 5.11 11.3 (i86pc)
usr/src version: 34781:f2dcf50db899:0.175.3.0.0.25.0:on11u3_25+2
usr/closed version: 2734:1f583953c078:0.175.3.0.0.25.0:on11u3_25+2
image uuid: 283f0a4f-dc0b-416e-b6f9-cdabb43bf5c1
panic message:
BAD TRAP: type=6 (#ud Invalid opcode) rp=fffffffc81b67910 addr=ffffa10014134b40
complete: yes, all pages present as configured
dump content: kernel [LOADED,UNVERIFIED] (core kernel pages)
              zfs [LOADED,UNVERIFIED] (ZFS metadata (ZIO buffers))
panicking PID: 1273 (not dumped)
> ::stack
intel_vmread_insn()
intel_update_rip+0x20(ffffa10051144e00, 0)
vcpu_check_critical+0x29(ffffa100513df000, ffffa10051144e00)
mach_vcpu_enter+0x75(ffffa10051144e00)
vcpu_enter+0x27a(ffffa10051144e00)
zvmm_vcpu_enter+0x10c(ffffa100513df000, ffffa10012b6d000, 202003)
do_zvmm_ioctl+0x1cd(ffffa100513df000, 6a4f6505, 7ffba0401b00, fffffffc81b67e14,
202003)
zvmm_ioctl+0x7a(11a00000001, 6a4f6505, 7ffba0401b00, 202003, ffffa10015262b08,
fffffffc81b67e14)
cdev_ioctl+0x6e(11a00000001, 6a4f6505, 7ffba0401b00, 202003, ffffa10015262b08,
fffffffc81b67e14)
spec_ioctl+0x5d(ffffa1005110bd80, 6a4f6505, 7ffba0401b00, 202003,
ffffa10015262b08, fffffffc81b67e14)
fop_ioctl+0xd6(ffffa1005110bd80, 6a4f6505, 7ffba0401b00, 202003,
ffffa10015262b08, fffffffc81b67e14)
ioctl+0x188(3, 6a4f6505, 7ffba0401b00)
sys_syscall+0x251()
> ::msgbuf -v
           TIMESTAMP           LOGCTL MESSAGE                                 
2015 Sep 11 12:31:30 ffffa10015b2e300 sd3 at cpqary31: target 1 lun 0
2015 Sep 11 12:31:30 ffffa10015b2e240
sd3 is /pci@0,0/pci8086,340a@3/pci103c,3234@0/sd@1,0
2015 Sep 11 12:31:30 ffffa10015b2e180
/pci@0,0/pci8086,340a@3/pci103c,3234@0/sd@1,0 (sd3) online
2015 Sep 11 12:31:30 ffffa1001680ef40 sd4 at cpqary31: target 2 lun 0
2015 Sep 11 12:31:30 ffffa1001680ee80
sd4 is /pci@0,0/pci8086,340a@3/pci103c,3234@0/sd@2,0
2015 Sep 11 12:31:30 ffffa1001680ed00
/pci@0,0/pci8086,340a@3/pci103c,3234@0/sd@2,0 (sd4) online
2015 Sep 11 12:31:30 ffffa1001680ec40 sd5 at cpqary31: target 3 lun 0
2015 Sep 11 12:31:30 ffffa1001680eb80
sd5 is /pci@0,0/pci8086,340a@3/pci103c,3234@0/sd@3,0
2015 Sep 11 12:31:30 ffffa1001680eac0
/pci@0,0/pci8086,340a@3/pci103c,3234@0/sd@3,0 (sd5) online
2015 Sep 11 12:31:30 ffffa1001680ea00 sd6 at cpqary31: target 4 lun 0
2015 Sep 11 12:31:30 ffffa1001680e940
sd6 is /pci@0,0/pci8086,340a@3/pci103c,3234@0/sd@4,0
2015 Sep 11 12:31:30 ffffa1001680e880
/pci@0,0/pci8086,340a@3/pci103c,3234@0/sd@4,0 (sd6) online
2015 Sep 11 12:31:32 ffffa100144521c0
NOTICE: bnxe0: Phy 0 supported: 1G 2.5G 10G
2015 Sep 11 12:31:32 ffffa1001680e700
NOTICE: bnxe0: Phy 0 link config: switch/10G speed/auto flow/auto
2015 Sep 11 12:31:32 ffffa1001680e640
WARNING: bnxe0: Phy autoneg requested along with other speeds, ignoring others a
nd forcing autoneg
2015 Sep 11 12:31:32 ffffa1001680e580
NOTICE: bnxe0: Requesting Phy 0 speed: 1G 10G auto
2015 Sep 11 12:31:32 ffffa1001680e4c0
WARNING: bnxe0: Phy TX flow requested but not supported
2015 Sep 11 12:31:32 ffffa1001680e400
WARNING: bnxe0: Phy RX flow requested but not supported
2015 Sep 11 12:31:32 ffffa1001680e340
NOTICE: bnxe0: Requesting Phy 0 flow: auto
2015 Sep 11 12:31:32 ffffa1001680e280 pseudo-device: fasttrap0
2015 Sep 11 12:31:32 ffffa1001680e1c0 fasttrap0 is /pseudo/fasttrap@0
2015 Sep 11 12:31:32 ffffa1001680e100 pseudo-device: fbt0
2015 Sep 11 12:31:32 ffffa100168dfec0 fbt0 is /pseudo/fbt@0
2015 Sep 11 12:31:32 ffffa100168dfe00 pseudo-device: fcp0
2015 Sep 11 12:31:32 ffffa100168dfd40 fcp0 is /pseudo/fcp@0
2015 Sep 11 12:31:32 ffffa100168dfc80 pseudo-device: fcsm0
2015 Sep 11 12:31:32 ffffa100168dfbc0 fcsm0 is /pseudo/fcsm@0
2015 Sep 11 12:31:32 ffffa100168dfb00 pseudo-device: llc10
2015 Sep 11 12:31:32 ffffa100168dfa40 llc10 is /pseudo/llc1@0
2015 Sep 11 12:31:32 ffffa100168df980 pseudo-device: lockstat0
2015 Sep 11 12:31:32 ffffa100168df800 lockstat0 is /pseudo/lockstat@0
2015 Sep 11 12:31:32 ffffa100168df740 pseudo-device: lofi0
2015 Sep 11 12:31:32 ffffa100168df680 lofi0 is /pseudo/lofi@0
2015 Sep 11 12:31:32 ffffa100168df500 pseudo-device: power0
2015 Sep 11 12:31:32 ffffa100168df440 power0 is /pseudo/power@0
2015 Sep 11 12:31:32 ffffa100168df380 pseudo-device: profile0
2015 Sep 11 12:31:32 ffffa100168df200 profile0 is /pseudo/profile@0
2015 Sep 11 12:31:32 ffffa100168df140 pseudo-device: ramdisk1024
2015 Sep 11 12:31:32 ffffa100168df080 ramdisk1024 is /pseudo/ramdisk@1024
2015 Sep 11 12:31:32 ffffa10016b8df00 pseudo-device: sdt0
2015 Sep 11 12:31:32 ffffa10016b8de40 sdt0 is /pseudo/sdt@0
2015 Sep 11 12:31:32 ffffa10016b8dd80 pseudo-device: srn0
2015 Sep 11 12:31:32 ffffa10016b8dcc0 srn0 is /pseudo/srn@0
2015 Sep 11 12:31:32 ffffa10016b8dc00 pseudo-device: systrace0
2015 Sep 11 12:31:32 ffffa10016b8db40 systrace0 is /pseudo/systrace@0
2015 Sep 11 12:31:32 ffffa10016b8da80 pseudo-device: ucode0
2015 Sep 11 12:31:32 ffffa10016b8d9c0 ucode0 is /pseudo/ucode@0
2015 Sep 11 12:31:32 ffffa10016b8d840 pseudo-device: uvfs0
2015 Sep 11 12:31:32 ffffa10016b8d780 uvfs0 is /pseudo/uvfs@0
2015 Sep 11 12:31:32 ffffa10016b8d6c0 pseudo-device: vboxdrv0
2015 Sep 11 12:31:32 ffffa10016b8d600 vboxdrv0 is /pseudo/vboxdrv@0
2015 Sep 11 12:31:32 ffffa10016b8d540 pseudo-device: vboxusbmon0
2015 Sep 11 12:31:32 ffffa10016b8d480 vboxusbmon0 is /pseudo/vboxusbmon@0
2015 Sep 11 12:31:32 ffffa10016b8d3c0 pseudo-device: bpf0
2015 Sep 11 12:31:32 ffffa10016b8d300 bpf0 is /pseudo/bpf@0
2015 Sep 11 12:31:32 ffffa10016b8d180 pseudo-device: fssnap0
2015 Sep 11 12:31:32 ffffa10016b8d0c0 fssnap0 is /pseudo/fssnap@0
2015 Sep 11 12:31:33 ffffa1001971be80 IP Filter: v4.1.9, running.
2015 Sep 11 12:31:33 ffffa1001971bc40 pseudo-device: nsmb0
2015 Sep 11 12:31:33 ffffa1001971bac0 nsmb0 is /pseudo/nsmb@0
2015 Sep 11 12:31:33 ffffa1001971b940 pseudo-device: pm0
2015 Sep 11 12:31:33 ffffa1001971b7c0 pm0 is /pseudo/pm@0
2015 Sep 11 12:31:33 ffffa1001971b1c0 NOTICE: bnxe0: Link Down
2015 Sep 11 12:31:33 ffffa1001971b100
NOTICE: bnxe0: BnxeHwStartCore: Hardware started (clients None)
2015 Sep 11 12:31:33 ffffa1001d597ec0
NOTICE: bnxe0: BnxeHwStartL2: L2 started (clients L2)
2015 Sep 11 12:31:33 ffffa1001d597d40 NOTICE: oss_spoke0 registered
2015 Sep 11 12:31:33 ffffa1001d597a40
NOTICE: bnxe0: 1Gb Full Duplex Rx Flow ON Tx Flow ON Link Up
2015 Sep 11 12:31:33 ffffa1001d597980
NOTICE: bnxe0 link up, 1000 Mbps, full duplex
2015 Sep 11 12:31:33 ffffa10011dbac80
NOTICE: oss_spoke0 link up, 1000 Mbps, unknown duplex
2015 Sep 11 12:31:33 ffffa1001d5978c0 NOTICE: bnxe0: Link Down
2015 Sep 11 12:31:33 ffffa10014454d80 NOTICE: bnxe0 link down
2015 Sep 11 12:31:33 ffffa1001d597800 NOTICE: oss_spoke0 link down
2015 Sep 11 12:31:33 ffffa1001d597680
NOTICE: bnxe0: 1Gb Full Duplex Rx Flow ON Tx Flow ON Link Up
2015 Sep 11 12:31:33 ffffa1001d5975c0
NOTICE: bnxe0 link up, 1000 Mbps, full duplex
2015 Sep 11 12:31:33 ffffa1001d597440
NOTICE: oss_spoke0 link up, 1000 Mbps, unknown duplex
2015 Sep 11 12:31:33 ffffa1001d716980
NOTICE: bnxe0: Adding multicast: 01:00:5e:00:00:01
2015 Sep 11 12:31:34 ffffa1001d597140
NOTICE: bnxe0: Adding multicast: 33:33:00:00:00:01
2015 Sep 11 12:31:34 ffffa10014452d00
NOTICE: bnxe0: Adding multicast: 33:33:ff:c4:70:28
2015 Sep 11 12:31:35 ffffa1001d8596c0
NOTICE: bnxe0: Removing multicast: 01:00:5e:00:00:01
2015 Sep 11 12:31:35 ffffa1001d71a640
NOTICE: bnxe0: Adding multicast: 01:00:5e:00:00:01
2015 Sep 11 12:31:37 ffffa1001d854340
NOTICE: bnxe0: Adding multicast: 33:33:00:00:02:02
2015 Sep 11 12:31:41 ffffa1001d854d00
/pseudo/zconsnex@1/zcons@0 (zcons0) online
2015 Sep 11 12:31:42 ffffa1001d84ec80
/pseudo/zconsnex@1/zcons@0 (zcons0) online
2015 Sep 11 12:31:42 ffffa1001d716080 NOTICE: net0 registered
2015 Sep 11 12:32:03 ffffa1000010c480 pseudo-device: vboxusbmon0
2015 Sep 11 12:32:03 ffffa10014016300 vboxusbmon0 is /pseudo/vboxusbmon@0
2015 Sep 11 12:32:04 ffffa10011dc31c0 pseudo-device: devinfo0
2015 Sep 11 12:32:04 ffffa1001d71f900 devinfo0 is /pseudo/devinfo@0
2015 Sep 11 12:32:05 ffffa1001d8541c0 vboxdrv: fffffffff8044020 VMMR0.r0
2015 Sep 11 12:32:05 ffffa10011750200 vboxdrv: fffffffff812d020 VBoxDDR0.r0
2015 Sep 11 12:32:05 ffffa100117502c0 vboxdrv: fffffffff82b5020 VBoxDD2R0.r0
2015 Sep 11 12:32:06 ffffa1001da3d6c0
panic[cpu7]/thread=ffffa10014134b40:
2015 Sep 11 12:32:06 ffffa1000010f380
BAD TRAP: type=6 (#ud Invalid opcode) rp=fffffffc81b67910 addr=ffffa10014134b40
2015 Sep 11 12:32:06 ffffa1001d8599c0

2015 Sep 11 12:32:06 ffffa10012fb6080 kzhost:
2015 Sep 11 12:32:06 ffffa1001da3dd80 #ud Invalid opcode
2015 Sep 11 12:32:06 ffffa10011d4a3c0 addr=0xffffa10014134b40
2015 Sep 11 12:32:06 ffffa1001d84e740
pid=1273, pc=0xfffffffff841fe40, sp=0xfffffffc81b67a08, eflags=0x10282
2015 Sep 11 12:32:06 ffffa1001d859b40
cr0: 80050033<pg,wp,ne,et,mp,pe> cr4: 6f8<xmme,fxsr,pge,mce,pae,pse,de>
2015 Sep 11 12:32:06 ffffa100092f9e00 cr2: 98d6fe4
2015 Sep 11 12:32:06 ffffa1001d7165c0 cr3: 7a310b000
2015 Sep 11 12:32:06 ffffa1001418df40 cr8: c
2015 Sep 11 12:32:06 ffffa100168df2c0
2015 Sep 11 12:32:06 ffffa10014454a80
        rdi: fffffffff841fe40 rsi: fffffffc81b67908 rdx:         ffffffff
2015 Sep 11 12:32:06 ffffa10014454780
        rcx:               38  r8: ffffa10012af7900  r9: ffffa100116fb240
2015 Sep 11 12:32:06 ffffa100142f6980
        rax:                0 rbx:             681e rbp: fffffffc81b67a30
2015 Sep 11 12:32:06 ffffa100142f6d40
        r10:             b128 r11: fffffffffc0186d0 r12: ffffa100513df000
2015 Sep 11 12:32:06 ffffa10011750740
        r13:                3 r14: ffffa10051169000 r15: ffffa10014134b40
2015 Sep 11 12:32:06 ffffa10011ac0c40
        fsb: ffff80ffbf6aba40 gsb: ffffa10011c33000  ds:               38
2015 Sep 11 12:32:06 ffffa100117505c0
         es:               38  fs:                0  gs:                0
2015 Sep 11 12:32:06 ffffa10011ac0580
        trp:                6 err:                0 rip: fffffffff841fe40
2015 Sep 11 12:32:06 ffffa10011ac07c0
         cs:               30 rfl:            10282 rsp: fffffffc81b67a08
2015 Sep 11 12:32:06 ffffa10011e0e6c0    ss:               38
2015 Sep 11 12:32:06 ffffa10011ac0340

cpu          address    timestamp type  vc  handler   pc
2015 Sep 11 12:32:06 ffffa10014452100
2015 Sep 11 12:32:06 ffffa10011b47380
fffffffc81b67820 unix:real_mode_stop_cpu_stage2_end+d31e ()
2015 Sep 11 12:32:06 ffffa10012fb6800 fffffffc81b67900 unix:trap+13c1 ()
2015 Sep 11 12:32:06 ffffa1001d859e40 fffffffc81b67910 unix:cmntrap+e7 ()
2015 Sep 11 12:32:06 ffffa100142f6c80
fffffffc81b67a30 zvmm:intel_vmread_insn+0 ()
2015 Sep 11 12:32:06 ffffa1001418d640
fffffffc81b67a60 zvmm:intel_update_rip+20 ()
2015 Sep 11 12:32:06 ffffa1001418d700
fffffffc81b67a90 zvmm:vcpu_check_critical+29 ()
2015 Sep 11 12:32:06 ffffa10010d8b640
fffffffc81b67ae0 zvmm:mach_vcpu_enter+75 ()
2015 Sep 11 12:32:06 ffffa10012fb68c0 fffffffc81b67b50 zvmm:vcpu_enter+27a ()
2015 Sep 11 12:32:06 ffffa1001418d880
fffffffc81b67bc0 zvmm:zvmm_vcpu_enter+10c ()
2015 Sep 11 12:32:06 ffffa1001418d940
fffffffc81b67c30 zvmm:do_zvmm_ioctl+1cd ()
2015 Sep 11 12:32:06 ffffa10014016c00 fffffffc81b67c90 zvmm:zvmm_ioctl+7a ()
2015 Sep 11 12:32:06 ffffa10014016540 fffffffc81b67d10 genunix:cdev_ioctl+6e ()
2015 Sep 11 12:32:06 ffffa10014016600 fffffffc81b67d50 specfs:spec_ioctl+5d ()
2015 Sep 11 12:32:06 ffffa100140166c0 fffffffc81b67df0 genunix:fop_ioctl+d6 ()
2015 Sep 11 12:32:06 ffffa10014016780 fffffffc81b67ef0 genunix:ioctl+188 ()
2015 Sep 11 12:32:06 ffffa10014016840
fffffffc81b67f00 unix:brand_sys_syscall+2d2 ()
2015 Sep 11 12:32:06 ffffa10014016900
2015 Sep 11 12:32:06 ffffa100140169c0 syncing file systems...
2015 Sep 11 12:32:06 ffffa10014016a80  done
>
kloczek
 
Posts: 14
Joined: 9. Sep 2015, 15:35

Re: VirtualBox 5.0.4 crashes Solaris 11.3 beta

Postby Ramshankar » 14. Sep 2015, 16:48

Run once:
Code: Select all   Expand viewCollapse view
VBoxManage setproperty hwvirtexclusive off


Reboot the host system and try again. The crash seems to be when you're using Solaris kernel zones (zvmm).
Oracle Corp.
Ramshankar
Oracle Corporation
 
Posts: 774
Joined: 7. Jan 2008, 16:17

Re: VirtualBox 5.0.4 crashes Solaris 11.3 beta

Postby kloczek » 15. Sep 2015, 20:02

I just done the same test with VBox 5.0.4 on Sol 11.2 with applied latest SRU.
One step forward. Solaris 11.2 with SRUs is not crashing!!! :)

Looking on VM logs I see that possibly system is now booting correctly. Because my blank system is booting over network I see some DHCP queries on DHCP server as well so probably everything is OK.

However I have some issue with accessing to RDP console of this VM.
In my script I'm using the line:
Code: Select all   Expand viewCollapse view
VBoxManage modifyvm $VM --memory 4096 --vram 128 --vrde on

And network interface is initialized by:

Code: Select all   Expand viewCollapse view
VBoxManage modifyvm $VM --nic1 bridged --bridgeadapter1 oss_spoke0 --macaddress1 auto

oss_spoke0 vnic is created on top of net0 so theoretically after VM boot I should be able to access over RDP to console over my host address on default RDP port 3389.
Am I right or what am I doing wrong?

I'm trying to fing on my Sol host some traces that some VBox process is listening on RDP port but I cannot find it ..

Still I see in system logs on each VM start three log entries:

Sep 15 17:08:16 bootstrap vboxdrv: [ID 702911 kern.notice] vboxdrv: fffffffff84c5020 VMMR0.r0
Sep 15 17:08:16 bootstrap vboxdrv: [ID 702911 kern.notice] vboxdrv: fffffffff8144020 VBoxDDR0.r0
Sep 15 17:08:16 bootstrap vboxdrv: [ID 702911 kern.notice] vboxdrv: fffffffff7808020 VBoxDD2R0.r0

I'm not sure is it something which should be fixed or ceased .. or maybe not (?)
kloczek
 
Posts: 14
Joined: 9. Sep 2015, 15:35

Re: VirtualBox 5.0.4 crashes Solaris 11.3 beta

Postby Ramshankar » 16. Sep 2015, 10:52

Do NOT create a VNIC manually unless it matches the MAC address of the VM's network card used to bridge over it and the VNIC is exclusively used by the VM. If you just want to bridge over 'net0', just supply 'net0' instead of creating a VNIC yourself.
Oracle Corp.
Ramshankar
Oracle Corporation
 
Posts: 774
Joined: 7. Jan 2008, 16:17

Re: VirtualBox 5.0.4 crashes Solaris 11.3 beta

Postby kloczek » 16. Sep 2015, 14:11

Problem is that I want to have static MAC addresses on each VM to have possibility to distinguish each one in KickStart server DHCP/TFTP PXE boot settings.
I've already started static MAC addresses using instead auto.
If you know other/simpler way to per VM mac address please let me know.

My current VM it is only kind of POC which I'm going to use to create AWS Linux AMIs. and on describing automated assembly process IMO best is use KS profiles which in other scenarios can be straight used on deploying exactly the same system images on bare metal.
Simple I found in Amazon documentation that VMDK images can be straight pushed to AWS as EBS images (I've not tested it yet as I'm still have not working first system created over VBox).
I've started using VBox as bootstrap platform only because lorax OL7 tool is useless as tool which could be used to generate AMIs.
I've started working on assembly my own custom AMIs because I want to have DTrace support in all our AWS systems.

What about these kernel messages? Should I raise some SR with those messages or it can be ignored?
Another question: I cannot find how to specify RDP port over VBoxManage. Q: how to do this?
kloczek
 
Posts: 14
Joined: 9. Sep 2015, 15:35

Re: VirtualBox 5.0.4 crashes Solaris 11.3 beta

Postby Ramshankar » 17. Sep 2015, 11:41

I don't really know or understand your setup but as I said, the MAC address of the VNIC needs to match the MAC address of the network card of the VM you are using to bridge over that VNIC.

The kernel messages are normal, they are just indicating the load address of the dynamically loaded ring-0 modules.
Oracle Corp.
Ramshankar
Oracle Corporation
 
Posts: 774
Joined: 7. Jan 2008, 16:17

Re: VirtualBox 5.0.4 crashes Solaris 11.3 beta

Postby kloczek » 18. Sep 2015, 18:28

OK, I found how to change RDP port over VBoxManage command.
It is "VBoxManage modifyvm <VM_name> --vrdeport <port>"
kloczek
 
Posts: 14
Joined: 9. Sep 2015, 15:35

Re: VirtualBox 5.0.4 crashes Solaris 11.3 beta

Postby kloczek » 12. Oct 2015, 20:11

One step forward. Solaris 11.2 with SRUs is not crashing!!! :)


I was wrong. It was not failing only because I had disabled all kernel zones.
As it was suggested after
Code: Select all   Expand viewCollapse view
VBoxManage setproperty hwvirtexclusive off

VBox is now working with working on side kernel zones.
kloczek
 
Posts: 14
Joined: 9. Sep 2015, 15:35


Return to VirtualBox on Solaris Hosts

Who is online

Users browsing this forum: Majestic-12 [Bot] and 4 guests