Custom Query (16363 matches)
Results (1261 - 1263 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17839 | invalid | move vm to new laptop. Critical error running virtual machine | ||
| Description |
Hello, I've moved my vm to a new laptop and now I receive a "Critical error running virtual machine", when the vm has started up and i have logged in. My vm is a Windows Server 2008 R2 machine and my host on both my old and new laptop is Windows 10 Enterprise. Any suggestions? I've included the log |
|||
| #5200 | invalid | mov rsi,rcx doesn't work in Virtual Box 3.0.8 | ||
| Description |
NOTE: This report does NOT concern a mainstream guest OS. I have developed a loader for a small X86-64 hobby OS system. This consists of a bootable floppy-disc image, which loads a binary image into memory, and executes it in 64-bit "long" mode. I have the following to report: My system boots and runs fine on:
However, my system does NOT work when booting from floppy image mounted in Virtual Box 3.0.8. I get a guru error and VBOX bombs out with *either* a clean guru error box, or a dirty Vista-standard "this program has stopped working" dialog. [In fact this might even be a second issue I can report -- something to do with MSVCR80.dll] However, the primary issue concerns me more. I do not know if there are debug facilities within VBOX, so I am debugging by inserting an infinite loop "jmp $" in my NASM code, re-building and running. If VBOX hits this and loops forever and does NOT guru on me, I consider this a "test pass". If VBOX does not get this far because of a guru error I consider this a "test fail". Test results and source code snippets included below. In brief: In a routine to render a text message onto the (graphics mode) linear frame buffer : mov rsi,rcx (of all things) appears not to work:
On entry, rcx is 0x210fdd, which is the address of a message string:
When executed at address 0x210781, with rcx=0x210fdd and rsi=0xccccCCCCccccCCCC, and the null-terminated ASCII string "TEST MESSAGE" at address 0x210fdd, according to VBOX.LOG, "mov rsi,rcx" appears to load rcx with value "0x53454d2054534554" rather than the expected 0x210fdd. Interestingly, "0x53454d2054534554" would be mov rsi,[rcx] OTHER NOTES I am using the 2MB page size. The above memory is covered by a 2MB page at address 0x200000 (2MB). Opcode "4889CE" was generated by the NASM assembler, version 2.06 compiled on Jun 29 2009, and was dis-assembled by the graphic debugger in BOCHS PC Simulator v 2.4.1 Also, the following is the first line of code in my GP Fault (exception 13) handler, however the system is so broken by this stage, it never runs: 00:00:03.487 CPUM: 0008:0000000000210b60 4c 8d 3d 05 00 00 00 lea r15, [000000005h wrt rip] TEST NOTES IN DETAIL FOLLOW. Here I am illustrating the pertinent part of the routine, and I move the "jmp $" infinite-loop instruction down one place per test: TEST 1 : Prove RCX is an OK address =====sv_printf:
jmp $ ; DEBUG Infinite loop here (no Guru message if all is OK)
TEST RESULT: PASS TEST 2 : Prove mov RSI,RCX doesn't immediately crash ========sv_printf:
jmp $ ; DEBUG Infinite loop here (no Guru message if all is OK)
TEST RESULT: PASS TEST 3 : Prove RCX's value copied into RSI OK (FAIL) ========sv_printf:
jmp $ ; DEBUG Infinite loop here (no Guru message if all is OK) TEST RESULT: FAIL I appreciate this is not a standard guest system, so may not be high priority, however, this system does run on the systems listed above, and it is odd that this crashes Virtual Box, which I would quite like to starting using. Please contact me if you need the image file of the boot floppy disc and instructions. Thanks for your time, Jonathan. |
|||
| #5334 | obsolete | mousesupport failed on fedora 12 host starting win7 guest | ||
| Description |
If i start win7 guest on fedora 12 the mouse doesn't work. The cursor don't move anymore on the screen but i can work with the mouse because i see the highligt icons or highlight commands in the menu of win7, so the funktions of the mouse work but i don't see any cursor. Also i can't move back to the host system with the mouse (guest-additions are installed). virtualbox version is 3.0.10 (same on 3.0.8). kernel-2.6.31.5-104.fc12.x86_64. On fedora 10 everthing works fine with same virtualbox versions. So i think it's a prob with the new x-server 1.7. If you need more info's let me know. Best regards
|
|||

