Custom Query (16363 matches)
Results (1681 - 1683 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5792 | fixed | cannot step by instruction in dbx/mdb inside guest => Fixed in SVN | ||
| Description |
64bit host OpenSolaris 09/06 (on x2250) + vbox 3.1.0 from extra repository happens in 64 bit guests nv129 & OpenSolaris 09/06 , NAT I ssh through a forwarded port to the machine & I do $ mdb /usr/bin/ls > main::bp > ::run > ::step mdb: target stopped at: main+4: pushl %esi > ::step mdb: target stopped at: main+0xc: xorl %ebx,%ebx > main::dis main: pushl %ebp main+1: movl %esp,%ebp main+3: pushl %ebx main+4: pushl %esi main+5: pushl %edi main+6: subl $0x2bc,%esp main+0xc: xorl %ebx,%ebx main+0xe: movl %ebx,0xfffffd74(%ebp) as you can see the step command skipped more than one instruction same thing is happening for dbx I am not sure if this is a bug of emulation or mdb/dbx, hence this bug ;) thanks much for clearing it up for me |
|||
| #6044 | invalid | removing a directory with VM with snapshots will break VM register | ||
| Description |
create a VM now VirtualBox GUI and cli is in a weird state, since such machine cannot be unregistered nor deleted I get errors like: % VBoxManage unregistervm OpenSolaris0906 VirtualBox Command Line Management Interface Version 3.1.2 (C) 2005-2009 Sun Microsystems, Inc. All rights reserved. ERROR: Cannot unregister the machine 'OpenSolaris0906' because it has 1 snapshots Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Machine, interface IMachine, callee nsISupports Context: "UnregisterMachine(uuid, machine.asOutParam())" at line 167 of file VBoxManageMisc.cpp obviously the directory with the VDI and the snapshot are long gone from the disk ... :( |
|||
| #5667 | obsolete | downloading files via scp in linux guest to shared folders fails for some files with Protocoll error | ||
| Description |
Hi, If transferring (mainly) huge files via scp from an external machine to a shared folder in Linux guest results for some files (not all) reproducable in a Protocol error on scp and the resulting file is corrupt afterwards: test@virtualbox:~/SharedFolder$ scp storage:test.tar.gz . test.tar.gz 100% 16MB 458.7KB/s 00:36 ./test.tar.gz: Protocol error test@virtualbox:~/SharedFolder$ ls -lsh insgesamt 15M 15M -rwxrwxrwx 1 test test 15M 2009-12-04 17:43 test.tar.gz When running the same scp with same file in a not shared folder, the resulting files are in a fine state: test@virtualbox:/tmp$ scp storage:test.tar.gz . test.tar.gz 100% 16MB 458.7KB/s 00:36 test@virtualbox:/tmp$ ls -lsh insgesamt 17M 17M -rw-r--r-- 1 test test 17M 2009-12-04 17:57 test.tar.gz The strange thing is that this problem does not occur for all files. But if you have a affected file, this is reproducable all the time. Till now I only have the feeling, that the chance to run into this problem is higher in case the transferred file is huge (several MB). For files of only a few KB I have not encountered this problem yet. |
|||

