Custom Query (16363 matches)
Results (109 - 111 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10718 | fixed | "VBoxmanage snapshot <name> list" errors out when there are no snapshots => Fixed in SVN | ||
| Description |
Running "VBoxManage snapshot <name> list" on a vm having no snapshots throws the following error: VBoxManage: error: This machine does not have any snapshots VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Machine, interface IMachine, callee nsISupports Context: "FindSnapshot(Bstr().raw(), ptrSnapshot.asOutParam())" at line 192 of file VBoxManageSnapshot.cpp Basically, there is no reason to error out like this, a simple "VBoxManage: this machine does not have any snapshots" would be sufficient. Using "list" to check wether there are snapshots or not is - at least I guess it is - a pretty logical approach and it cant cause an error in both cases. |
|||
| #4069 | worksforme | "VERR_VM_DRIVER_VERSION_MISMATCH" on start try for a virtual machine configuration | ||
| Description |
I built and installed the current VirtualBox development (trunk) software for my own kernel. Now I try to look at a virtual machine for the image file "KNOPPIX_V6.0.1-ADRIANE_V1.1CD-2009-02-08-DE.iso". Unfortunately, I get the messsage "RTR3Init failed with rc=-1912" in the dialogue "Error In supR3HardenedMain". Another dialogue contains the message "Virtual machine 'Knoppix 6.0.1' has terminated unexpectedly during startup." and the following details. Fehlercode: NS_ERROR_FAILURE (0x80004005)
Komponente: Machine
Interface: IMachine {13420cbb-175a-4456-85d0-301126dfdec7}
This return code seems to be connected with the symbol "VERR_VM_DRIVER_VERSION_MISMATCH". A solution is offered by the article "Setup Jail". I do not follow this suggestion to create a 64-bit chroot environment because I expect that all required components should be already available for the specific processor architecture on my system. I wonder a bit about the situation that the command "make install" did not put any binaries into the directories "/usr/local/bin" and "/usr/local/lib64". Is the following information useful for this issue? Sonne:~ # VBoxManage -v 2.2.2_OSEr46594 |
|||
| #13899 | fixed | "VboxNetNat.exe" Random crashes -> fixed in 6.0.4 | ||
| Description |
host OS:window 7; host some software:avast!; noteBook:lenovo k27,intel I3,RAM 8G,ssd 128G; host network:LAN,or LAN wifi; guest OS:centos 7; guest network:NAT network,forwarding port(tcp127.0.0.1:22 => 10.0.2.5:22,tcp127.0.0.1:80=>10.0.2.5:80;tcp127.0.0.1:3306 => 10.0.2.5:3306),interface:Intel Pro/1000 MT server (82545EM) mixed mode is disabled; vm virtualbox VER:4.3.23-98520/4.3.22(test both ) when testing,only this guest OS is runing! my email is :qidizi&qq.com If you are using a NAT(not NAT network), this problem will become more serious, see the following https://www.centos.org/forums/viewtopic.php?f=50&t=51112 If you use the "bridging model", this problem would not have arisen; Possible causes:postfix(http://www.postfix.org,Install on CentOS systems) is runing,and A large number of mail is being delivered;and the browser on the host(window on "k27"), constantly refresh a PHP page,the "nginx/php" on Centos;then "VboxNetNat.exe" Random crashes,But I cannot determine what operation caused crash; |
|||

