Custom Query (16363 matches)
Results (2005 - 2007 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10117 | obsolete | BSOD upon starting a VM | ||
| Description |
Host: Windows 7 SP1 x64 with latest updates and drivers Technical information
Exception: SYSTEM_SERVICE_EXCEPTION I have attached an analysis of the memory dump |
|||
| #10118 | obsolete | “SWbemObjectEx: Access denied” error calling GetDWORDValue on guest VirtualBox machine | ||
| Description |
Using "vboxmanage guestcontrol" to execute a .vbs script on guest machine which queries the registry with GetDWORDValue returns the error: "SWbemObjectEx: Access denied". Note: Occasionally, the error "Illegal operation attempted on a registry key that has been marked for deletion." will occur on the first attempt, and then the "SWbemObjectEx: Access denied" thereafter. Guest Environment: Windows 7 or Vista. Is NOT a problem with Windows XP guest, at least for me. Steps:
const HKEY_LOCAL_MACHINE = &H80000002
strComputer = "."
set oReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\" & strComputer & "\root\default:StdRegProv")
strKeyPath = "SOFTWARE\test"
strValueName = "test"
oReg.GetDWORDValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,dwValue
msgbox dwValue
vboxmanage guestcontrol "Win7x86" execute --image "C:\windows\system32\cscript.exe" --wait-stderr --username testlogin --password mypassword -- "C:\Users\testlogin\Desktop\test.vbs"
I should be able to work around this by using other tool (e.g. sysinternals PsExec.exe) to run the script on the guest. If this is closed as by design or deferred for some other reason, I would still appreciate a your insight into why / how this is happening; I don't understand all the moving parts. will attach vbox.log file on request. |
|||
| #10120 | obsolete | Host-only adapter spontaneously loses DHCP-leased IP | ||
| Description |
Hello! My Setup:I'm running VB 4.1.6 on an Ubuntu 10.04 LTS host with a Debian Squeeze as guest. My network configuration is 1) Host-only adapter for convenient host<->guest accessibility through 192.168.56.x IPs. The guest network corresponding to this adapter is configured dynamically via DHCP. 2) NAT adapter for "internet access" in the guest. The host is a workstation which I've never rebooted so far during the time I'm working with VB (I have been using VB for a few weeks now). The problem:I've experienced the host-only adapter "losing its IP" already two times now. Each of the times, it happened like this: 1) I started the VM up to the Debian login screen and did not graphically log in. 2) I made sure that the guest's network interface corresponding to the host-only adapter successfully got its network configuration via DHCP (including the IP 192.168.56.101) by hovering the mouse pointer over the network symbol of the VB window corresponding to the VM. It said for example (among others): Adapter 1 (Host-only adapter): IP 192.168.56.101, cable connected 3) I then made sure that I can connect from the host to the guest via ssh user@192.168.56.101 This worked pretty well. 4) Basically, I then did not use the guest for a few days. I did not use VB at all in the meantime. This means that I did not start other VMs. I simply did not touch VB, I just left the VM described here running and running....
5) After a few days, I tried to 6) Hovering over the network symbol of the VB window corresponding to the VM said: Adapter 1 (Host-only adapter): cable connected I.e. the host-only adapter of the guest "lost" its IP address. As I said, I've observed this two times now. I do not know how to reliably reproduce it but it seems like a severe problem to me, because this issue renders the VM inaccessible from the outside. Do you know this problem? What should I do to further debug it? I did not try version 4.1.8, because the changelog does not indicate a change regarding the host-only adapter. Could it be a problem of configuration within the guest (some power saving stuff)? Thanks, Jan-Philip Gehrcke |
|||

