Custom Query (16363 matches)
Results (1786 - 1788 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1784 | fixed | Cannot create raw vmdk file on OpenSolaris | ||
| Description |
Running VirtualBox 1.6.2 on OpenSolaris 2008.05, 64-bit. This command: VBoxManage internalcommands createrawvmdk -filename /export/home/gs145266/fulldisk.vmdk -rawdisk /dev/dsk/c5d0p0 -register Returns: Error opening the raw disk: VERR_ACCESS_DENIED So I thought, okay, I need some privileges. I then ran this command: pfexec VBoxManage internalcommands createrawvmdk -filename /export/home/gs145266/fulldisk.vmdk -rawdisk /dev/dsk/c5d0p0 -register I got *no* response at all. No error message. And no file was created. The VBoxManage command just displays its copyright string and then exits. I used su and then ran VBoxManage again and got the exact same result: *no* result. No error message and no file is created. Is there some log file I can look at? Is there some way to turn on additional error reporting? |
|||
| #11408 | obsolete | Cannot create the machine folder in the parent folder, if machine folder already exists | ||
| Description |
The behavior is cross-platform, but I won't call it a bug for windows or mac, because there isn't an obvious use-case in windows or mac. I call it a bug, because in solaris or linux (if you're using btrfs) you're very likely going to want to create a new zfs or btrfs filesystem for a new VM, which means virtualbox really should have an option to happily move forward and create a new VM in a pre-existing empty directory. Problem is trivial to reproduce. Go to your default machine folder, mkdir somenewmachine. Now try to create a machine called "somenewmachine" and virtualbox refuses to create the new machine. Error message: "Cannot create the machine folder in the parent folder" Problem reproduced in VirtualBox 4.2.6, using the GUI, on openindiana 151a7 and Windows 7 x86_64 Pro fully updated. |
|||
| #8434 | obsolete | Cannot create the virtual disk on NTFS partition | ||
| Description |
Hi, I asked in the forum but no reply in 3 days therefore I open a ticket here. As I mentioned in the title, when I create the virtual disk on the NTFS partiton which was mounted with write permission, I got the below error: Failed to create the hard disk storage /mnt/data/VirtualBox/win2k8.vdi.
Could not create the hard disk storage unit '/mnt/data/VirtualBox/win2k8.vdi'.
VDI: writing pre-header failed for '/mnt/data/VirtualBox/win2k8.vdi' (VERR_NET_OPERATION_NOT_SUPPORTED).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Medium
Interface:
IMedium {aa8167ba-df72-4738-b740-9b84377ba9f1}
My NTFS partiton was mounted with write permission: /dev/sda6 on /mnt/data type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096,default_permissions) $ ls -ld /mnt/data/VirtualBox/ drwxr-xr-x 1 quanta quanta 48 Feb 22 14:56 /mnt/data/VirtualBox/ 'quanta' user is a member of vboxusers group: $ groups quanta wheel audio cdrom cdrw usb users quanta plugdev wireshark vboxusers games The vboxdrv module was loaded in running kernel: $ lsmod | grep vbox vboxnetflt 11304 0 vboxnetadp 5692 0 vboxdrv 114736 2 vboxnetflt,vboxnetadp Below is different result code when I upgrade to version 4.0.4: Result Code:
VBOX_E_FILE_ERROR (0x80BB0004)
Component:
Medium
Interface:
IMedium {9edda847-1279-4b0a-9af7-9d66251ccc18}
Does anyone think of any reason for this? |
|||

