Custom Query (16363 matches)
Results (424 - 426 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #698 | fixed | VBoxManage snapshot command error => Fixed in 2.0.2 | ||
| Description |
Calling VBoxManage results in a an error and print trace information on the console. More specifically, this error occurs when calling VBoxManage with the following command syntax: VBoxManage snapshot machine_uuid showvminfo snapshot_uuid The trace output is: [!] FAILED calling display->get_Width(&xRes) at line 1137!
[!] Primary RC = E_ACCESSDENIED (0x80070005) - General access denied error
[!] Full error info present: true , basic error info present: true
[!] Result Code = E_ACCESSDENIED (0x80070005) - General access denied error
[!] Text = The console is not powered up
[!] Component = Display, Interface: IDisplay, {09789f63-4525-48e5-a5e41080453b0eab}
[!] Callee = IDisplay, {09789f63-4525-48e5-a5e4-1080453b0eab}
I have attached a screenshot of VirtualBox GUI showing machine snapshots, together with a log of the output from "VBoxManage showvminfo machine_uuid" to give an overview of my environment. However, the error is demonstated in the attached file "snapshot.txt". A related issue is that the snapshot named "Running snapshot" (UUID: 120558e6-1526-4df3-b713-fd5d375bc47b) was created whilst the virtual machine was powered on. However, the output shown in "snapshot.txt" indicates that the machine was powered off when this snapshot was taken. Is this as intended? If so, how can a shell tool determine from parsing the output from VBoxManage whether a particular snapshot was taken when the virtual machine was powered on or powered off. Kind regards, laser |
|||
| #699 | fixed | Stop error (BSOD) with VirtualBox 1.5 if start TeamSpeak client on host | ||
| Description |
I am experiencing a BSOD (blue screen of death) due to a Windows stop error on host followed by immediate system reboot when TeamSpeak client is executed on host. Symptom only occurs if VB is running and has WinXP guest powered on (haven't tried other guest OSes). BSOD occurs as soon as TeamSpeak client initialises (i.e. before connecting to a TeamSpeak server). I have attached the minidump file for analysis. On reboot, Windows host reports..."You received this message because a device driver installed on your computer caused the Windows operating system to stop unexpectedly." TeamSpeak is a free utility which enables people to speak with one another over the Internet (http://www.goteamspeak.com). This problem was first reported on the forum in thread "BSOD with VirtualBox 1.5 if start TeamSpeak client on host". Host: WinXP 32 Guest: WinXP 32 CPU: AMD Athlon 64 X2 VirtualBox v1.50 TeamSpeak2 client v2.0.32.60 |
|||
| #702 | fixed | after upgrade to ver 1.5.0 no virtualdupmod -> recheck with SVN/1.5.2 | ||
| Description |
after updating the guest additions from 1.4.0 to 1.5.0 my virtualdupmod http://virtualdubmod.sourceforge.net/ does not work anymore... perhaps there is something wrong with the additions :-) MfG PS: SuSE 10.2 host
|
|||

