我安装了Jenkins（版本2.74）并安装了vagrant插件。创建了一个创建vagrantfile并执行vagrant box add命令的作业
vagrant box add test solaris.box
并执行vagrant up命令，VM在jenkins作业中成功运行。
但VM未在VirtualBox Manager中显示。
在命令提示符中，VBoxManage.exe list vms命令也未列出正在运行的VM名称。
Vagrant版本：1.7.4 VirtualBox版本：5.0.12
命令提示输出：
D:\>vagrant global-status
id name provider state directory
------------------------------------------------------------------------
ee544e4 default virtualbox running D:/nBOL_VMS/nbolapp
67df2d1 default virtualbox running D:/nBOL_VMS/nbolapptest
206a5c8 default virtualbox running D:/nBOL_VMS/Jenkins-slave
VBoxManage.exe list runningvms
当我执行VBoxManage.exe list runningvms时，我的命令提示符输出显示为null。
Jenkins输出：
Vagrant global Status :
id name provider state directory
------------------------------------------------------------------------
ee544e4 default virtualbox running D:/nBOL_VMS/nbolapp
67df2d1 default virtualbox running D:/nBOL_VMS/nbolapptest
206a5c8 default virtualbox running D:/nBOL_VMS/Jenkins-slave
VBoxManage list runningvms
"nbolapptest" {bc04dd64-c868-4304-a3b7-eff6d66f862e}
"Jenkins-slave" {c73ead23-ecd7-499d-b5b9-2d52c3b49d7e}
"nbolapp" {4c762312-013e-4ae7-9649-8239abe0f92d}
VBoxManage showvminfo bc04dd64-c868-4304-a3b7-eff6d66f862e
Name: nbolapptest
Groups: /
Guest OS: Oracle Solaris 11 (64-bit)
UUID: bc04dd64-c868-4304-a3b7-eff6d66f862e
Config file: C:\Users\sbsa\VirtualBox VMs\nbolapptest\nbolapptest.vbox
Snapshot folder: C:\Users\sbsa\VirtualBox VMs\nbolapptest\Snapshots
Log folder: C:\Users\sbsa\VirtualBox VMs\nbolapptest\Logs
Hardware UUID: bc04dd64-c868-4304-a3b7-eff6d66f862e
Memory size: 8192MB
Page Fusion: off
VRAM size: 12MB
CPU exec cap: 100%
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 2
PAE: off
Long Mode: on
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI: on
IOAPIC: on
Time offset: 0ms
RTC: UTC
Hardw. virt.ext: on
Nested Paging: on
Large Pages: on
VT-x VPID: on
VT-x unr. exec.: on
Paravirt. Provider: Default
State: running (since 2016-11-07T11:40:20.291000000)
Monitor count: 1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0): SATA
Storage Controller Type (0): IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 30
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
SATA (0, 0): C:\Users\sbsa\VirtualBox VMs\nbolapptest\box-disk1.vmdk (UUID: 03b32e37-f77c-456c-a4e9-fe6753d87761)
SATA (1, 0): Empty
NIC 1: MAC: 080027015DD9, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 1 Rule(0): name = ssh, protocol = tcp, host ip = 127.0.0.1, host port = 2222, guest ip = , guest port = 22
NIC 1 Rule(1): name = tcp1521, protocol = tcp, host ip = , host port = 1521, guest ip = , guest port = 1521
NIC 1 Rule(2): name = tcp6000, protocol = tcp, host ip = , host port = 6000, guest ip = , guest port = 6000
NIC 1 Rule(3): name = tcp8080, protocol = tcp, host ip = , host port = 2200, guest ip = , guest port = 8080
NIC 1 Rule(4): name = tcp9043, protocol = tcp, host ip = , host port = 9043, guest ip = , guest port = 9043
NIC 1 Rule(5): name = tcp9060, protocol = tcp, host ip = , host port = 9060, guest ip = , guest port = 9060
NIC 1 Rule(6): name = tcp9443, protocol = tcp, host ip = , host port = 9443, guest ip = , guest port = 9443
NIC 2: MAC: 0800272C9857, Attachment: Bridged Interface 'Intel(R) Ethernet Connection (2) I219-LM', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
LPT 1: disabled
LPT 2: disabled
Audio: enabled (Driver: DSOUND, Controller: AC97, Codec: STAC9700)
Clipboard Mode: disabled
Drag and drop Mode: disabled
Session name: headless
Video mode: 1024x768x32 at 0,0 enabled
VRDE: disabled
USB: enabled
EHCI: disabled
XHCI: disabled
USB Device Filters:
<none>
Available remote USB devices:
<none>
Currently Attached USB Devices:
<none>
Bandwidth groups: <none>
Shared folders:
Name: 'vagrant', Host path: 'D:/nBOL_VMS/nbolapptest' (machine mapping), writable
VRDE Connection: not active
Clients so far: 0
Video capturing: not active
Capture screens: 0
Capture file: C:\Users\sbsa\VirtualBox VMs\nbolapptest\nbolapptest.webm
Capture dimensions: 1024x768
Capture rate: 512 kbps
Capture FPS: 25
Guest:
Configured memory balloon size: 0 MB
OS type: Solaris_64
Additions run level: 2
Additions version: 4.3.18 r96516
Guest Facilities:
Facility "VirtualBox Base Driver": active/running (last update: 2016/11/07 11:41:19 UTC)
Facility "VirtualBox System Service": active/running (last update: 2016/11/07 11:41:47 UTC)
Facility "Seamless Mode": not active (last update: 2016/11/07 11:41:19 UTC)
Facility "Graphics Mode": not active (last update: 2016/11/07 11:41:19 UTC)
它显示了通过jenkins作业执行上述命令时的所有细节。 会是什么问题。
答案 0 :(得分：4)
（对于Windows）尝试以管理员身份运行虚拟框，看看现在是否可以看到正在运行的虚拟机。
答案 1 :(得分：1)
以root身份运行虚拟框：
sudo virtualbox
答案 2 :(得分：0)
我在Windows 10中通过运行以管理员身份运行Vagrant命令的Powershell窗口解决了此问题。一旦这样做，VirtualBox便开始显示正确的状态，即使它不是以管理员身份启动的。
答案 3 :(得分：0)
您必须使用su user＃特权或sudo virtualbox来启动virtualbox或以root用户身份在ubuntu中登录，这将在我第一次遇到相同问题的情况下起作用，但这种方式已解决
答案 4 :(得分：0)
在Windows 10中，只有当cmd（从Vagrant开始的地方）和VirtualBox Manager都以普通用户身份启动，或者同时以管理员身份启动时，Vagrant Box才会在VirtualBox Manager中显示。如果您从以管理员身份启动的cmd和以常规用户VirtualBox Manager身份启动的VirtualBox Manager中启动Vagrant，则Vagrant Box将不会显示在const options = [
{ key: 1, text: "Name", value: "name", icon: "sort" },
{ key: 2, text: "Time", value: "time", icon: "sort" },
{ key: 3, text: "Type", value: "type", icon: "sort" }
];
中。
答案 5 :(得分：0)
如果您更改启动VM Services的凭据，并使用用于启动VirtualBox Manager的管理特权来配置用户，它将正常运行。