1)
Questions and Answers :
Unix/Linux :
How is virtualization support determined?
(Message 42659)
Posted 29 May 2020 by JasonDD
Post:
Yes, success! Thanks to you and Laurence for the help.
|
2)
Questions and Answers :
Unix/Linux :
How is virtualization support determined?
(Message 42653)
Posted 28 May 2020 by JasonDD
Post:
You're right, and I think it's ready now. There was a kernel module (vmm.ko) loaded for the Bhyve hypervisor, which was causing the VirtualBox VMs to abort. I then tested with a local Linux VM and verified Internet connectivity from within it.
|
3)
Questions and Answers :
Unix/Linux :
How is virtualization support determined?
(Message 42633)
Posted 27 May 2020 by JasonDD
Post:
Found this trace output in one of the VBox slots:
2020-05-25 09:29:42 (493):
Command: VBoxManage -q list hostinfo
Exit Code: 0
Output:
VBoxManage: error: Failed to initialize COM because the global settings directory '/.config/VirtualBox' is not accessible!
VBoxManage had been looking in the wrong path: it should be /var/db/boinc/.config/VirtualBox. I created a soft link to the root directory and that got rid of the VM Hypervisor communication issue. All tasks ran for about 15 s then exited with computation error. Output from that seems to indicate storage-related issues. That may just be due to the previous path issue and hopefully new tasks will work as expected.
00:00:02.321764 nspr-2 VirtualBox: object created
00:00:03.532599 nspr-3 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'boinc_c5b03ff1a8fdc086'}, preserve=false aResultDetail=0
00:00:03.539749 nspr-2 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'boinc_a9943c61fe3eef53'}, preserve=false aResultDetail=0
00:00:03.541719 nspr-2 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'boinc_d9bd85bc731c0ccd'}, preserve=false aResultDetail=0
00:00:03.553741 nspr-5 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'boinc_d6c331d15a368dea'}, preserve=false aResultDetail=0
00:00:03.638864 nspr-4 ERROR [COM]: aRC=NS_ERROR_INVALID_ARG (0x80070057) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={Cannot register the hard disk '/var/db/boinc/slots/10/vm_image.vdi' {c7cbbeeb-c984-467e-9b6e-0d2e670bed58} because a hard disk '/var/db/boinc/slots/11/vm_image.vdi' with UUID {c7cbbeeb-c984-467e-9b6e-0d2e670bed58} already exists}, preserve=false aResultDetail=0
00:00:03.666970 nspr-5 ERROR [COM]: aRC=NS_ERROR_INVALID_ARG (0x80070057) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={Cannot register the hard disk '/var/db/boinc/slots/12/vm_image.vdi' {c7cbbeeb-c984-467e-9b6e-0d2e670bed58} because a hard disk '/var/db/boinc/slots/11/vm_image.vdi' with UUID {c7cbbeeb-c984-467e-9b6e-0d2e670bed58} already exists}, preserve=false aResultDetail=0
00:00:03.694870 nspr-3 ERROR [COM]: aRC=NS_ERROR_INVALID_ARG (0x80070057) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={Cannot register the hard disk '/var/db/boinc/slots/13/vm_image.vdi' {c7cbbeeb-c984-467e-9b6e-0d2e670bed58} because a hard disk '/var/db/boinc/slots/11/vm_image.vdi' with UUID {c7cbbeeb-c984-467e-9b6e-0d2e670bed58} already exists}, preserve=false aResultDetail=0
00:00:03.708839 nspr-4 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'boinc_dc49c621d1a47cc9'}, preserve=false aResultDetail=0
00:00:03.732973 nspr-3 Saving settings file "/var/db/boinc/slots/12/boinc_d6c331d15a368dea/boinc_d6c331d15a368dea.vbox" with version "1.16-freebsd"
00:00:03.846398 nspr-5 Saving settings file "/.config/VirtualBox/VirtualBox.xml" with version "1.12-freebsd"
00:00:08.473439 nspr-6 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={No storage device attached to device slot 0 on port 0 of controller 'Hard Disk Controller'}, preserve=false aResultDetail=0
00:00:08.480386 nspr-6 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={No storage device attached to device slot 0 on port 0 of controller 'Hard Disk Controller'}, preserve=false aResultDetail=0
00:00:08.482060 nspr-3 Saving settings file "/var/db/boinc/slots/12/boinc_d6c331d15a368dea/boinc_d6c331d15a368dea.vbox" with version "1.16-freebsd"
00:00:11.425915 nspr-4 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={This machine does not have any snapshots}, preserve=false aResultDetail=0
00:00:11.427093 nspr-6 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={This machine does not have any snapshots}, preserve=false aResultDetail=0
00:00:11.445746 nspr-6 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={This machine does not have any snapshots}, preserve=false aResultDetail=0
00:00:12.275916 nspr-6 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={This machine does not have any snapshots}, preserve=false aResultDetail=0
00:00:12.276070 nspr-10 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={This machine does not have any snapshots}, preserve=false aResultDetail=0
00:00:12.462268 nspr-2 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={This machine does not have any snapshots}, preserve=false aResultDetail=0
00:00:12.480533 nspr-6 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={This machine does not have any snapshots}, preserve=false aResultDetail=0
00:00:12.486634 nspr-2 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={This machine does not have any snapshots}, preserve=false aResultDetail=0
00:00:14.413734 nspr-12 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:00:14.414254 nspr-12 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:00:23.567057 main VirtualBox: object deletion starts
00:00:23.847278 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:00:23.847887 main VirtualBox: object deleted
|
4)
Questions and Answers :
Unix/Linux :
How is virtualization support determined?
(Message 42626)
Posted 27 May 2020 by JasonDD
Post:
Laurence, I did get a bunch of tasks but they're all in a state of "Postponed: Communication with VM Hypervisor failed." I've fixed several things including permissions for /dev/vbox* files, DBus errors, and missing guest additions .iso file because the VBoxSvc.log file provided some hints. Now, after resolving those issues, there are no more hints - just ACCESSDENIED. Here is the latest output from VBoxSvc.log.
VirtualBox XPCOM Server 5.2.34 r133883 freebsd.amd64 (May 27 2020 01:12:11) release log
00:00:00.001068 main Log opened 2020-05-27T09:06:03.361527000Z
00:00:00.001072 main Build Type: release
00:00:00.001085 main OS Product: FreeBSD
00:00:00.001091 main OS Release: 11.3-RELEASE-p7
00:00:00.001097 main OS Version: FreeBSD 11.3-RELEASE-p7 #0 r325575+ca0f1a6ba25(HEAD): Tue Apr 21 20:46:20 UTC 2020 root@tnbuild01.tn.ixsystems.com:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64
00:00:00.001117 main Host RAM: 32703MB (31.9GB) total, 13457MB (13.1GB) available
00:00:00.001124 main Executable: /usr/local/lib/virtualbox/VBoxSVC
00:00:00.001125 main Process ID: 42491
00:00:00.001127 main Package type: BSD_64BITS_GENERIC (OSE)
00:00:00.003343 main IPC socket path: /tmp/.vbox-boinc-ipc/ipcd
00:00:00.110301 nspr-2 VirtualBox: object creation starts
00:00:00.110496 nspr-2 Home directory: '/var/db/boinc/.config/VirtualBox'
00:00:01.134476 nspr-2 NAT: resolv.conf: nameserver xxx.xxx.xxx.xxx
00:00:01.134552 nspr-2 HostDnsMonitor::updateInfo
00:00:01.134581 nspr-2 HostDnsMonitor: old information
00:00:01.134592 nspr-2 no server entries
00:00:01.134603 nspr-2 no domain set
00:00:01.134613 nspr-2 no search string entries
00:00:01.134624 nspr-2 HostDnsMonitor: new information
00:00:01.134666 nspr-2 server 1: xxx.xxx.xxx.xxx
00:00:01.134677 nspr-2 domain: mydomain.net
00:00:01.134687 nspr-2 search string 1: mydomain.net
00:00:01.140476 nspr-2 VD: VDInit finished with VINF_SUCCESS
00:00:01.141253 nspr-2 VirtualBox: object created
00:00:06.147103 main VirtualBox: object deletion starts
00:00:06.147927 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:00:06.148373 main VirtualBox: object deleted
|
5)
Questions and Answers :
Unix/Linux :
How is virtualization support determined?
(Message 42547)
Posted 20 May 2020 by JasonDD
Post:
Okay, thank-you for your help
|
6)
Questions and Answers :
Unix/Linux :
How is virtualization support determined?
(Message 42545)
Posted 20 May 2020 by JasonDD
Post:
Yes, that's correct, I want to be able to run vbox tasks. Funny you say that because I just took a look at the list of applications this morning and noticed none of the vbox apps are for FreeBSD. Really, that shouldn't be a problem because these are VM images, right? As long as VirtualBox is available, I expected to receive tasks. Even if these were native apps, FreeBSD can run Linux apps, and I'm set up for that. World Community Grid sends me native Linux tasks and they get processed successfully.
|
7)
Questions and Answers :
Unix/Linux :
How is virtualization support determined?
(Message 42542)
Posted 20 May 2020 by JasonDD
Post:
Thanks for that, computezrmle. What I was looking for was to understand how the LHC app/website determines what to put on that line in the computer details webpage describing virtualization support. There must be some value or combination of values indicating level of virtualization support. I found this in samples/vboxwrapper/vbox_vboxmanage.cpp
if (!strstr(aid.host_info.p_features, "vmx") && !strstr(aid.host_info.p_features, "svm")) {
vboxlog_msg("Hardware acceleration CPU extensions not detected. Disabling VirtualBox hardware acceleration support.");
disable_acceleration = true;
}
The value 'svm' or 'vmx' must be in the 'Processor features' line as determined by BOINC. The processor features are, as you indicated, determined by the client/hostinfo_unix.cpp file. The problem is that the code in hostinfo_unix.cpp isn't sufficient to determine svm support for AMD CPUs, or at least my CPU under FreeBSD. I was able to patch the file somewhat so that I get 'svm' on the 'Processor features' line, and now LHC picks that up and reports virtualization is supported.
|
8)
Questions and Answers :
Unix/Linux :
How is virtualization support determined?
(Message 42507)
Posted 15 May 2020 by JasonDD
Post:
What is LHC@home looking for on a host to determine if its CPU supports virtualization? I'm running FreeBSD on an AMD Phenom II X6 with SVM enabled in the BIOS. I noticed in BOINC that the capabilities list is short and the features list is empty. SVM didn't show up anywhere until I modified the client code to recognize SVM and add it to the capabilities.
Fri May 15 15:43:41 2020 | | Processor: 6 amd64 AMD Phenom(tm) II X6 1035T ProcessorAMD Phenom(tm) II X6 1035T Processor [] [sse sse2 pni 3dnow 3dnowext mmx popcnt svm]
Fri May 15 15:43:41 2020 | | Processor features:
Fri May 15 15:43:41 2020 | | OS: FreeBSD: 11.3-RELEASE-p7
Fri May 15 15:43:41 2020 | | Memory: 31.94 GB physical, 0 bytes virtual
Fri May 15 15:43:41 2020 | | Disk: 1.67 TB total, 1.66 TB free
Fri May 15 15:43:41 2020 | | Local time is UTC -7 hours
Fri May 15 15:43:41 2020 | | VirtualBox version: 5.2.34r133883
After restarting and updating to the LHC project, the machine details still show:
Virtualization Virtualbox (5.2.34r133883) installed, CPU does not have hardware virtualization support
Does this condition prevent the machine from receiving any VirtualBox tasks?
I appreciate any help getting the machine to pick up VirtualBox tasks.
|
