VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1339 - 1341 of 16363)

Ticket Resolution Summary Owner Reporter
#1367 duplicate Guru Meditation -2403 (VERR_TRPM_DONT_PANIC) smitna
Description

Occurs during installation of guest rPath LAMP appliance when the installer is searching for LAMP appliance installations (please see attached screenshot). rPath LAMP Appliance version is 1.3.2.1 x86, obtainable via < http://www.rpath.org/rbuilder/project/lamp/release?id=5922 >. The sha1 of the iso used is: 05af33a7adbffaeb166790540752ee55521c1391. Host OS is Foresight Linux 1.4.2 (2.6 kernel).

#1368 invalid Problem to build VirtualBox on Slackware 12.0 => Fixed in 1.6.2 iguito
Description

When I tried to build VirtualBox 1.5.6 from the source code (tar.bz2), the follow message error appeared after command "kmk all":

kBuild: Compiling VBoxREM - translate-op.c In file included from /usr/src/virtualbox/vbox/src/recompiler/translate-op.c:70: /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h: In function 'dyngen_code': /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4596: error: 'memcpy' redeclared as different kind of symbol /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4597: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4613: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4630: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4646: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4662: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4803: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4819: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4835: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4851: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4951: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4967: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4983: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4999: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:5016: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:5030: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:5044: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:5058: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:7156: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:7245: error: called object 'memcpy' is not a function /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:7334: error: called object 'memcpy' is not a function kmk[2]: * usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/translate-op.o Error 1 The failing command: @gcc -c -O2 -Wall -g -fomit-frame-pointer -fno-gcse -IInnoTek -IInnoTek/crt -Itarget-i386 -Ifpu -I/usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM -I/usr/src/virtualbox/vbox/src/VBox/VMM -I/usr/src/virtualbox/vbox/src/recompiler -I/usr/src/virtualbox/vbox/include -I/usr/src/virtualbox/vbox/out/linux.x86/release -DVBOX -DVBOX_OSE -DREM_PHYS_ADDR_IN_TLB -DRT_OS_LINUX -D_FILE_OFFSET_BITS=64 -DRT_ARCH_X86 -DX86 -DIN_REM_R3 -DREM_INCLUDE_CPU_H -DIN_RING3 -DLOG_USE_C99 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_REENTRANT -Wp,-MD,/usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/translate-op.o.dep -Wp,-MT,/usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/translate-op.o -Wp,-MP -o /usr/src/virtualbox/vbox/out/linux.x86/release/obj/src/recompiler/VBoxREM/translate-op.o /usr/src/virtualbox/vbox/src/recompiler/translate-op.c kmk[2]: Leaving directory `/usr/src/virtualbox/vbox/src/recompiler' kmk[1]: * [pass_dlls_before] Error 2 kmk[1]: Leaving directory `/usr/src/virtualbox/vbox/src' kmk: * [pass_dlls_before] Error 2

I solved my problem getting the binary on https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=innotek-1.5.6-G-F@CDS-CDS_SMI

thanks :)

#1369 fixed createrawvmdk with partition switch: sharing violation Martin Huebner
Description

Good afternoon,

after a flawless installation of a W2K Professional SP4 Guest on a Vista SP1 Host (not all of my programs are cooperating well with Vista) I tried to enable the raw hard disk support of Virtual Box.

I have several NTFS-Partitions, the last one listed is intended to be accessible to the guest.

The listpartitions command gives me the partition no. 4:

VBoxManage internalcommands listpartitions -rawdisk \.\PhysicalDrive1

Output: VirtualBox Command Line Management Interface Version 1.5.6 (C) 2005-2008 innotek GmbH All rights reserved.

Number Type StartCHS EndCHS Size (MiB) Start (Sect) 1 0x27 0 /32 /33 130 /170/40 1024 2048 2 0x07 130 /171/1 1023/254/63 30728 2099223 5 0x07 1023/1 /2 1023/254/63 102437 65031184 6 0x07 1023/1 /1 1023/254/63 5122 274824018 4 0x07 1023/0 /1 1023/254/63 13311 285314400

O.K., so I entered:

VBoxManage internalcommands createrawvmdk -filename "C:\P4.vmdk" -rawdisk \.\PhysicalDrive1 - partitions 4

Output: ERROR: VMDK: could not create new partition data file 'C:\P4-pt.vmdk' Error code VERR_SHARING_VIOLATION at C:\vbox\branch\w32-1.5\src\VBox\Devices\Storage\VmdkHDDCore.cpp(2224) in function vmdkCreateImage Error while creating the raw disk VMDK: VERR_SHARING_VIOLATION

Even dismounting the partition by removing the drive letter in Vista's Disk Management leads to the same effect.

Omitting the -partition parameter works, no sharing violation, but then all my physical partitions are accessible to the guest.

Any suggestions would be appreciated. Thanks in advance.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy