Custom Query (16363 matches)
Results (1867 - 1869 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9543 | obsolete | Cannot run a small application | ||
| Description |
I am a software developer. I usually use VirtualBox to test my application in a 32-bit Windows environment. I attached two zip files of my sample C# projects. The first one, ExpStarter.exe, loads the second file, ExpWorker.dll, dynamically and calls a function of it. These files works fine under Microsoft VirtualPC and real 32-bit WinXP environment. But, they fails in VirtualBox. This is why I think that there is some bug in VirtualBox which prevents them to run correctly. The attached zip files contain the source code and project files of these two files so that you can see what I use in the files. The exe and dll files are also in the zip files so that you can try in VirtualBox. |
|||
| #20304 | duplicate | Cannot run any machine on last windows insiders build (211359 aka 21h2) | ||
| Description |
Hi, it's seems that inside the last insiders build of windows 10 insiders is impossible starting any machine. I know that usually (VERR_NEM_VM_CREATE_FAILED) error is connected with hyper-v windows platform enabled, but teorically in the new releases of virtual box it should coesist with hyper-v and infact first of update there were no problem with hyper-v. I not know if Microsoft have update its hypervisor platform inside last build, I coud not find useful info. the info from virtualbox: Failed to get device handle and/or partition ID for 0000000001ab47f0 (hPartitionDevice=0000000000000bad, Last=0xc0000002/1) (VERR_NEM_VM_CREATE_FAILED).
Codice di uscita:E_FAIL (0x80004005)
Componente: ConsoleWrap
Interfaccia: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
|
|||
| #20320 | fixed | Cannot run executable in shared folder in Linux/Kali -> Fixed in SVN | ||
| Description |
I am running two virtual machines in my Debian host: 1 Kali, 1 Windows 10. Both have a shared folder mounted into the guest machines, called "austausch" (= "shared" in English). In Kali, I start a terminal/bash and try to run an executable bash script like this: $ cd ~/austausch $ cat test.sh #!/bin/bash echo "Hello world!" $ ./test.sh bash: ./test.sh: /bin/bash: Defekter Interpreter: Das Argument ist ungültig (= "broken interpreter: The argument is invalid") $ bash test.sh Hello world! $ cp test.sh ~/ $ cd ~/ $ ./test.sh Hello world! $ mount | grep Austausch Austausch on /media/sf_Austausch type vboxsf (rw,nodev,relatime,iocharset=utf8,uid=0,gid=0) In Windows 10, there is no such issue and I can run arbitrary exe files from the shared folder. I am running VirtualBox 6.1.20 on Debian/Host, and it appears to be 6.1.18 in Kali for some reason although I tried to update *now*: $ apt update [...] $ apt install virtualbox-guest-utils virtualbox-guest-x11 [...] virtualbox-guest-utils ist schon die neueste Version (6.1.18-dfsg-2). (= "is already the newest version") virtualbox-guest-x11 ist schon die neueste Version (6.1.18-dfsg-2). (= "is already the newest version") I am not sure when this problem came up initially, but I think it was in VB 6.1.18. I seem to not be the only one with this problem, as a few colleagues of mine have run into this issue, too. Any ideas what might have gone wrong here? |
|||

