Re: [OpenIndiana-discuss] Virtualbox is core dumping
On 2019-10-01 10:31 a.m., Michal Nowak wrote: On 10/01/19 05:03 PM, Geoff Nordli wrote: Hi. I have a core dump if someone is able to look at it and give me some clues. https://www.dropbox.com/s/cq99x55uj7gspka/vmdump.0.OI.20190925?dl=1 All am doing is default install (text installer), fully update, install virtualbox. Create basic vm: /usr/bin/VBoxManage createvm --name test --ostype Ubuntu_64 --register Run it: VBoxHeadless -s test then it core dumps. thanks, Geoff Hi. Can it be that you have KVM module loaded? Once you crash with the latest OI and VirtualBox, get fresh info from the dump as described at https://illumos.org/docs/user-guide/debug-systems/#gathering-information-from-a-crash-dump. Perhaps better attach it to the email. (I know you provided it before, but it's not clear to me what VirtualBox/illumos version was it back then.) Thanks, Michal Hi. Here is the crashdump https://www.dropbox.com/s/n4ol6wbvsizlpo5/crash.0?dl=1 I can provide the complete vmdump.0 file if that would be helpful. This is a fully patched version of the latest OI. thanks, Geoff ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox is core dumping
In regard to: Re: [OpenIndiana-discuss] Virtualbox is core dumping, xleland...: Can someone direct me to the page where I can unsubscribe from this forum? Thank you It's a mailing list, and membership is managed via some software called 'mailman'. Every email message that is sent out by the mailing list software includes a signature/footer at the end with a link to a web page that will allow you to unsubscribe: openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Just go to that URL and look for the section near the bottom to find information on how you can unsubscribe. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox is core dumping
Can someone direct me to the page where I can unsubscribe from this forum? Thank you On Tuesday, October 1, 2019, 10:32:05 AM PDT, Michal Nowak wrote: On 10/01/19 05:03 PM, Geoff Nordli wrote: > Hi. > > I have a core dump if someone is able to look at it and give me some clues. > > https://www.dropbox.com/s/cq99x55uj7gspka/vmdump.0.OI.20190925?dl=1 > > All am doing is default install (text installer), fully update, install > virtualbox. > > Create basic vm: /usr/bin/VBoxManage createvm --name test --ostype > Ubuntu_64 --register > Run it: VBoxHeadless -s test > > then it core dumps. > > thanks, > > Geoff Hi. Can it be that you have KVM module loaded? Once you crash with the latest OI and VirtualBox, get fresh info from the dump as described at https://illumos.org/docs/user-guide/debug-systems/#gathering-information-from-a-crash-dump. Perhaps better attach it to the email. (I know you provided it before, but it's not clear to me what VirtualBox/illumos version was it back then.) Thanks, Michal ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox is core dumping
On 10/01/19 05:03 PM, Geoff Nordli wrote: Hi. I have a core dump if someone is able to look at it and give me some clues. https://www.dropbox.com/s/cq99x55uj7gspka/vmdump.0.OI.20190925?dl=1 All am doing is default install (text installer), fully update, install virtualbox. Create basic vm: /usr/bin/VBoxManage createvm --name test --ostype Ubuntu_64 --register Run it: VBoxHeadless -s test then it core dumps. thanks, Geoff Hi. Can it be that you have KVM module loaded? Once you crash with the latest OI and VirtualBox, get fresh info from the dump as described at https://illumos.org/docs/user-guide/debug-systems/#gathering-information-from-a-crash-dump. Perhaps better attach it to the email. (I know you provided it before, but it's not clear to me what VirtualBox/illumos version was it back then.) Thanks, Michal ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox is core dumping
On 2019-09-06 10:38 a.m., Michal Nowak wrote: On 09/04/19 08:06 PM, Geoff Nordli wrote: On 2019-09-04 10:40 a.m., Alan Coopersmith wrote: On 9/4/19 10:20 AM, Geoff Nordli wrote: Hi. I posted this a couple of days on the omnios list, but haven't gotten much feedback. I am hoping someone here might have some clues as OI and Omnios share the same vbox code. Posted below is some crash dump information. I have several machines running vbox without issue. The only thing I can think of here is that this machine has a "newer" Intel Xeon Silver 4110 Processor. Any other thoughts? That looks like the crashes we see on Solaris when SMAP is enabled on a CPU new enough to support it. The VirtualBox drivers try to access memory that SMAP blocks access to from kernel space. https://wiki.openindiana.org/oi/7.2+VirtualBox suggests "Workaround is to put: set disable_smap=1 in /etc/system and reboot, before starting VirtualBox" Hi Alan. I tried the smap disable, doesn't seem to make a difference. As well, I was told from the omnios list you don't need to disable smap when using the vbox builds from omnios/OI. They now work without having to disable it. thanks, Geoff If the system was ever "tainted" by the upstream binary VirtualBox packages, it might be actually easier to reinstall the system anew and see if the problem persists - as others were suggesting, it should not. Michal Hi. I have a core dump if someone is able to look at it and give me some clues. https://www.dropbox.com/s/cq99x55uj7gspka/vmdump.0.OI.20190925?dl=1 All am doing is default install (text installer), fully update, install virtualbox. Create basic vm: /usr/bin/VBoxManage createvm --name test --ostype Ubuntu_64 --register Run it: VBoxHeadless -s test then it core dumps. thanks, Geoff ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox is core dumping
On 09/04/19 08:06 PM, Geoff Nordli wrote: On 2019-09-04 10:40 a.m., Alan Coopersmith wrote: On 9/4/19 10:20 AM, Geoff Nordli wrote: Hi. I posted this a couple of days on the omnios list, but haven't gotten much feedback. I am hoping someone here might have some clues as OI and Omnios share the same vbox code. Posted below is some crash dump information. I have several machines running vbox without issue. The only thing I can think of here is that this machine has a "newer" Intel Xeon Silver 4110 Processor. Any other thoughts? That looks like the crashes we see on Solaris when SMAP is enabled on a CPU new enough to support it. The VirtualBox drivers try to access memory that SMAP blocks access to from kernel space. https://wiki.openindiana.org/oi/7.2+VirtualBox suggests "Workaround is to put: set disable_smap=1 in /etc/system and reboot, before starting VirtualBox" Hi Alan. I tried the smap disable, doesn't seem to make a difference. As well, I was told from the omnios list you don't need to disable smap when using the vbox builds from omnios/OI. They now work without having to disable it. thanks, Geoff If the system was ever "tainted" by the upstream binary VirtualBox packages, it might be actually easier to reinstall the system anew and see if the problem persists - as others were suggesting, it should not. Michal ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox is core dumping
On 2019-09-04 10:40 a.m., Alan Coopersmith wrote: On 9/4/19 10:20 AM, Geoff Nordli wrote: Hi. I posted this a couple of days on the omnios list, but haven't gotten much feedback. I am hoping someone here might have some clues as OI and Omnios share the same vbox code. Posted below is some crash dump information. I have several machines running vbox without issue. The only thing I can think of here is that this machine has a "newer" Intel Xeon Silver 4110 Processor. Any other thoughts? That looks like the crashes we see on Solaris when SMAP is enabled on a CPU new enough to support it. The VirtualBox drivers try to access memory that SMAP blocks access to from kernel space. https://wiki.openindiana.org/oi/7.2+VirtualBox suggests "Workaround is to put: set disable_smap=1 in /etc/system and reboot, before starting VirtualBox" Hi Alan. I tried the smap disable, doesn't seem to make a difference. As well, I was told from the omnios list you don't need to disable smap when using the vbox builds from omnios/OI. They now work without having to disable it. thanks, Geoff ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox is core dumping
On 2019-09-04 10:53 a.m., Bob Friesenhahn wrote: On Wed, 4 Sep 2019, Geoff Nordli wrote: Hi. I posted this a couple of days on the omnios list, but haven't gotten much feedback. I am hoping someone here might have some clues as OI and Omnios share the same vbox code. Posted below is some crash dump information. It seems like there has been plenty of feedback. Based on evidence I suspect that somehow you still have a package installed which is intended for Oracle Solaris. Maybe the some of the binaries for Oracle Solaris did not get uninstalled when you installed the OmniOS versions? Bob Hi Bob. That is the part that is weird, it is a clean install, brand new server. I compared the md5sum of some of the vbox executables from a server that is working with the new server and they match. thanks, Geoff ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox is core dumping
On Wed, 4 Sep 2019, Geoff Nordli wrote: Hi. I posted this a couple of days on the omnios list, but haven't gotten much feedback. I am hoping someone here might have some clues as OI and Omnios share the same vbox code. Posted below is some crash dump information. It seems like there has been plenty of feedback. Based on evidence I suspect that somehow you still have a package installed which is intended for Oracle Solaris. Maybe the some of the binaries for Oracle Solaris did not get uninstalled when you installed the OmniOS versions? Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox is core dumping
On 9/4/19 10:20 AM, Geoff Nordli wrote: Hi. I posted this a couple of days on the omnios list, but haven't gotten much feedback. I am hoping someone here might have some clues as OI and Omnios share the same vbox code. Posted below is some crash dump information. I have several machines running vbox without issue. The only thing I can think of here is that this machine has a "newer" Intel Xeon Silver 4110 Processor. Any other thoughts? That looks like the crashes we see on Solaris when SMAP is enabled on a CPU new enough to support it. The VirtualBox drivers try to access memory that SMAP blocks access to from kernel space. https://wiki.openindiana.org/oi/7.2+VirtualBox suggests "Workaround is to put: set disable_smap=1 in /etc/system and reboot, before starting VirtualBox" -- -Alan Coopersmith- alan.coopersm...@oracle.com Oracle Solaris Engineering - https://blogs.oracle.com/alanc ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Virtualbox is core dumping
Hi. I posted this a couple of days on the omnios list, but haven't gotten much feedback. I am hoping someone here might have some clues as OI and Omnios share the same vbox code. Posted below is some crash dump information. I have several machines running vbox without issue. The only thing I can think of here is that this machine has a "newer" Intel Xeon Silver 4110 Processor. Any other thoughts? thanks, Geoff Forwarded Message Subject:Re: [OmniOS-discuss] Re: Virtualbox is core dumping Date: Tue, 3 Sep 2019 12:43:08 -0700 From: Geoff Nordli To: omnios-discuss On 2019-09-03 2:15 a.m., Andy Fiddaman wrote: Hi Geoff, That crash dump looks like you are trying to use a binary virtualbox package from Oracle. That is for Solaris and not compatible with newer illumos/OmniOS kernels. There's a version of Virtualbox in the OmniOS extra package repository that works fine (and also does not require any of those entries in /etc/system) If I'm right and you're trying to use the Oracle one, then remove it and install the OmniOS one: pkg set-publisher -O https://pkg.omniosce.org/r151030/extra extra.omnios pkg install virtualbox@6 Regards, Hi. I thought I would add the crash dump information too, if this is helpful. mdb -k unix.0 vmcore.0 Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc apix scsi_vhci zfs sata sd ip hook neti sockfs arp usba xhci stmf stmf_sbd mm lofs idm mpt_sas i40e cpc random ufs logindmux ptm smbsrv nfs ] ::status debugging crash dump vmcore.0 (64-bit) from ma-stor2 operating system: 5.11 omnios-r151030-1b80ce3d31 (i86pc) image uuid: 890cff2b-333c-6ef8-809e-d257a45c9a79 panic message: BAD TRAP: type=e (#pf Page fault) rp=fe00f4fab8e0 addr=fc7fec89a3a0 occurred in module "" due to an illegal access to a user address dump content: kernel pages and pages from PID -1 ::stack 0xf83f4556() 0xf83ef68e() 0xf83efee5() 0xf84909f6() 0xf83f0b37() supdrvIOCtl+0x15fa() VBoxDrvSolarisIOCtl+0x15b() cdev_ioctl+0x39(113, c0185687, fc7febb16d70, 202003, feb197513b08, fe00f4fabea8) spec_ioctl+0x60(feb18fb8c300, c0185687, fc7febb16d70, 202003, feb197513b08, fe00f4fabea8) fop_ioctl+0x55(feb18fb8c300, c0185687, fc7febb16d70, 202003, feb197513b08, fe00f4fabea8) ioctl+0x9b(b, c0185687, fc7febb16d70) sys_syscall+0x19f() nsmb0 is /pseudo/nsmb@0 pseudo-device: pm0 pm0 is /pseudo/pm@0 pseudo-device: signalfd0 signalfd0 is /pseudo/signalfd@0 /pci@33,0/pci8086,2032@2/pci15d9,808@0 (mpt_sas0): mpt0: Initiator WWNs: 0x5003048023b69e01-0x5003048023b69e08 pseudo-device: timerfd0 timerfd0 is /pseudo/timerfd@0 NOTICE: softmac1000 registered NOTICE: softmac1000 link up, 1000 Mbps, full duplex PCIE-device: pci15d9,808@0, mpt_sas0 PCI Express-device: pci15d9,808@0, mpt_sas0 mpt_sas0 is /pci@33,0/pci8086,2032@2/pci15d9,808@0 mpt_sas1 at mpt_sas0: scsi-iport ff mpt_sas1 is /pci@33,0/pci8086,2032@2/pci15d9,808@0/iport@ff /pci@33,0/pci8086,2032@2/pci15d9,808@0/iport@ff (mpt_sas1) online w500304801f3b1e40 FastPath Capable and Enabled w5000c500a6ad3dbd FastPath Capable and Enabled w5000c500a6d464ad FastPath Capable and Enabled w5000c500adce3bb1 FastPath Capable and Enabled w5000c500a6cdce05 FastPath Capable and Enabled w5000c500a6a91051 FastPath Capable and Enabled w5000c500addd7e61 FastPath Capable and Enabled w5000c500a6cddef5 FastPath Capable and Enabled w5000c500addd5eed FastPath Capable and Enabled smp0 at mpt_sas1: target-port w500304801f3b1e7f smp0 is /pci@33,0/pci8086,2032@2/pci15d9,808@0/iport@ff/smp@w500304801f3b1e7f /pci@33,0/pci8086,2032@2/pci15d9,808@0/iport@ff/smp@w500304801f3b1e7f (smp0) online w500304801f3b1e40 FastPath Capable and Enabled sd2 at scsi_vhci0: unit-address g55cd2e4150944b55: f_sym sd2 is /scsi_vhci/disk@g55cd2e4150944b55 /scsi_vhci/disk@g55cd2e4150944b55 (sd2) online /scsi_vhci/disk@g55cd2e4150944b55 (sd2) multipath status: degraded: path 1 mpt_sas1/disk@w55cd2e4150944b55,0 is online w5000c500a6ad3dbd FastPath Capable and Enabled NOTICE: i40e0 link up, 1000 Mbps, full duplex sd3 at scsi_vhci0: unit-address g5000c500a6ad3dbf: f_sym sd3 is /scsi_vhci/disk@g5000c500a6ad3dbf /scsi_vhci/disk@g5000c500a6ad3dbf (sd3) online /scsi_vhci/disk@g5000c500a6ad3dbf (sd3) multipath status: degraded: path 2 mpt_sas1/disk@w5000c500a6ad3dbd,0 is online w5000c500a6d464ad FastPath Capable and Enabled ISA-device: pit_beep0 pit_beep0 is /pci@0,0/isa@1f/pit_beep sd4 at scsi_vhci0: unit-address g5000c500a6d464af: f_sym sd4 is /scsi_vhci/disk@g5000c500a6d464af /scsi_vhci/disk@g5000c500a6d464af (sd4) online /scsi_vhci/disk@g5000c500a6d464af (sd4) multipath status: degraded: path 3 mpt_sas1/disk@w5000c500a6d464ad,0 is online w5000c500adce3bb1 FastPath Capable and Enabled sd5 at scsi_vhci0: unit-add
