Custom Query (16363 matches)
Results (1522 - 1524 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17323 | duplicate | Feature request: Add a way to get VM's IP address through the API without guest additions | ||
| Description |
I am constantly reading about VirtualBox networking and trying to find a way to get the IP of a VM without installing Guest Additions to it, mainly when using Bridged Networking. From what I have read from the manual - it should be possible with a little tweak. I work in a project that uses the VirtualBox Main API through the VirtualBox Web Service. I use it to make and configure VMs. The IP needs to be taken automatically, without user interaction and no logging with SSH - because you don't know the IP. I have read the following from the manual:
From this statement it looks like VirtualBox already knows the IP address of a VM using Bridged Adapter - yet I haven't found a way to get it without Guest Additions. |
|||
| #17320 | fixed | VirtualBox-5.2-5.2.2_119230_fedora26-1.x86_64 config fails -> fixed in 5.2.8 | ||
| Description |
Installed VirtualBox-5.2-5.2.2_119230_fedora26-1.x86_64 but config fails. Same with the latest development version. /tmp/vbox.0/r0drv/linux/timer-r0drv-linux.c:1588:13: error: implicit declaration of function ‘init_timer_pinned’; did you mean ‘init_timer_key’? [-Werror=implicit-function-declaration] |
|||
| #17316 | fixed | Wrong instruction after single-step exception with 'rdtsc' -> fixed in 6.0 | ||
| Description |
There was bug 5 years ago (#10947) and was fixed, but in current release still appears. Here slightly modified code with looping 1000000 times around RDTSC call with charged TF. If at least one call does not work correctly, a corresponding message is displayed: .586
.model flat, stdcall
option casemap :none ; case sensitive
include \masm32\include\windows.inc
include \masm32\include\kernel32.inc
include \masm32\include\user32.inc
includelib \masm32\lib\kernel32.lib
includelib \masm32\lib\user32.lib
.data
Flag dd 0
Address dd 0
Counter dd 0
szRight db 'Flag Value is right!, address = 0x%lx, counter = %ld',0
szWrong db 'Flag Value is wrong!, address = 0x%lx, counter = %ld',0
szMessage db 256 dup(0)
szInfo db 'Info:'
.code
start:
assume fs: nothing
test_loop:
call @MyCode
mov ecx, dword ptr [esp+0Ch]
mov ecx, dword ptr [ecx+0B8h] ;;Ecx = Seh.eip
mov Address, ecx
.if ecx == offset @WrongExceptionEip
mov Flag,0
.else
mov Flag,1
.endif
xor eax, eax
retn
@MyCode:
push dword ptr fs:[0]
mov dword ptr fs:[0], esp
push 397h ;;Set Eflags
popfd
rdtsc
@RightExceptionEip: ;;Normally,Seh.eip should be pointed here
nop
@WrongExceptionEip: ;;In Guest system,('Without' VT-X/AMD-V),Seh.eip is pointed here.But 'With' VT-X/AMD-V,Seh.eip is right.
cmp Flag, 1
jnz flag_wrong
pop eax
pop fs:[0]
inc Counter
cmp Counter, 1000000
jnz test_loop
invoke wsprintf,offset szMessage, offset szRight, Address, Counter
jmp exit
flag_wrong:
invoke wsprintf,offset szMessage, offset szWrong, Address, Counter
exit:
invoke MessageBoxA,0,offset szMessage,offset szInfo,MB_OK
invoke ExitProcess,0
end start
(compiled sample attached rdtsc.exe) For example, in the real world, this misbehavior is used by the vmprotect to detect a virtual machine. I hope there is no good program crashing because of this misbehavior... |
|||

