- 00:03:59.510292 VMMDev: Guest Log: pam_vbox: pam_vbox_init: guest lib initialized
00:03:59.511604 VMMDev: Guest Log: pam_vbox: pam_vbox_init: rhost=<none>, tty=:0, prompt=<none>
00:03:59.514200 VMMDev: Guest Log: pam_vbox: pam_vbox_read_prop: read key "/VirtualBox/GuestAdd/PAM/CredsWait"="1"
00:03:59.516808 VMMDev: Guest Log: pam_vbox: pam_vbox_read_prop: read key "/VirtualBox/GuestAdd/PAM/CredsWait" with rc=VINF_SUCCESS
00:03:59.520276 VMMDev: Guest Log: pam_vbox: pam_vbox_read_prop: read key "/VirtualBox/GuestAdd/PAM/CredsWaitTimeout" with rc=VERR_NOT_FOUND
00:03:59.522561 VMMDev: Guest Log: pam_vbox: pam_vbox_read_prop: read key "/VirtualBox/GuestAdd/PAM/CredsMsgWaiting" with rc=VERR_NOT_FOUND
00:03:59.525426 VMMDev: Guest Log: pam_vbox: Showing message "Waiting for credentials ..." (type 4)Denying userspace vmm call type 0x000064 through vboxuser device node
00:03:59.527151 VMMDev: Guest Log: pam_vbox: Error: pam_vbox_check_creds: could not query for credentials! rc=VERR_ACCESS_DENIED. Aborting
I did also ask myself how credentials were supposed to arrive in pam_vbox and kinda doubt that the virtual-machine (manager) can access the Windows credential-store - and noticed that the preceding procedure for Windows guest included a command ...
Code: Select all
VBoxManage controlvm "Windows XP" setcredentials "John Doe" "secretpassword" "DOMTEST
What did I miss?