#853 closed defect (invalid)
DevATA_FILETOOBIG problem
Reported by: | yamlc | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 1.5.2 |
Keywords: | file size | Cc: | |
Guest type: | other | Host type: | other |
Description
Problem when i try to install Autocad 2007 under Guest W2003 server, Host Kubuntu 7.10. The Guest disk is NTFS.
Message :
Host system reported that the file limit has been exceeded. VM execution is suspended. You need to move the file to a filesystem which allows bigger files.
ID Erreur : DevATA_FILETOOBIG
Change History (12)
follow-up: 3 comment:1 by , 17 years ago
comment:2 by , 17 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
You are using a file system (on the host) that doesn't support files larger than 4 GB. (fat32?)
follow-up: 4 comment:3 by , 17 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Replying to Technologov:
What is your host OS and host filesystem ? What hardware ?
-Technologov
s i said, host is Kubuntu 7.10, guest is W2003 server NTFS. Hardware is P4 hyperthreading 3.2GHz + 2G0 ram
comment:4 by , 17 years ago
Sandervl73, the host system is Kubuntu and the problem raise with a file of 700 Mb, so....
comment:5 by , 17 years ago
yamlc:
- Try to disable hyper-threading in host OS or in BIOS. (hyper-threading has rare bugs)
- Try to enable or disable VT in VirtualBox (if you have that - most P4's don't, but check it)
# cat /proc/cpuinfo | grep vmx
- Try on different host filesystem (and different hard disk partition, if possible)
- Try using a different file system in guest (FAT32)
- Give use output of 2 commands: "mount" and "df -h"
-Technologov
follow-ups: 7 9 comment:6 by , 17 years ago
DevATA_FILETOOBIG means that you host file system is full. How much memory is free on the file system which contains the .vdi file?
comment:7 by , 17 years ago
Replying to frank:
DevATA_FILETOOBIG means that you host file system is full. How much memory is free on the file system which contains the .vdi file?
My vdi is maximum 20Go. At the moment it is 4Go and i have 19Go free on the file system that contains the vdi file.
- Try to disable hyper-threading in host OS or in BIOS. (hyper-threading has rare bugs)
Still not tried
2-Try to enable or disable VT in VirtualBox (if you have that - most P4's don't, but check it) change nothing
3-cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) 4 CPU 3.20GHz stepping : 3 cpu MHz : 3192.370 cache size : 2048 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 1 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 3 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr bogomips : 6389.54 clflush size : 64
processor : 1 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) 4 CPU 3.20GHz stepping : 3 cpu MHz : 3192.370 cache size : 2048 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 1 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 3 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr bogomips : 6384.01 clflush size : 64.
- Try on different host filesystem (and different hard disk partition, if possible)
tried from my ext3 linux partition, nothing changed
- Try using a different file system in guest (FAT32)
Not tried, all my vdi is in NTFS
- Give use output of 2 commands: "mount" and "df -h"
pascal@Pascal:~$ mount /dev/sda7 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) /sys on /sys type sysfs (rw,noexec,nosuid,nodev) varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755) varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777) procbususb on /proc/bus/usb type usbfs (rw) udev on /dev type tmpfs (rw,mode=0755) devshm on /dev/shm type tmpfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) lrm on /lib/modules/2.6.22-14-generic/volatile type tmpfs (rw) /dev/sda6 on /mnt/Logimine type vfat (rw,noexec,nosuid,nodev,umask=002,iocharset=utf8,codepage=850,shortname=mixed,uid=1000,gid=100) /dev/sda5 on /mnt/Users type vfat (rw,noexec,nosuid,nodev,umask=002,iocharset=utf8,codepage=850,shortname=mixed,uid=1000,gid=100) none on /proc/bus/usb type usbfs (rw,devgid=46,devmode=664) securityfs on /sys/kernel/security type securityfs (rw)
pascal@Pascal:~$ df -h Sys. de fich. Tail. Occ. Disp. %Occ. Monté sur /dev/sda7 17G 3,6G 13G 23% / varrun 1013M 140K 1013M 1% /var/run varlock 1013M 0 1013M 0% /var/lock udev 1013M 116K 1013M 1% /dev devshm 1013M 0 1013M 0% /dev/shm lrm 1013M 34M 980M 4% /lib/modules/2.6.22-14-generic/volatile /dev/sda6 52G 33G 19G 64% /mnt/Logimine /dev/sda5 61G 5,7G 56G 10% /mnt/Users
comment:8 by , 17 years ago
Well,
I cloned my vdi and now, i can't even copy a file of 2Mo from one shared folder into the vdi... I forgot to mention that i have Serial ATA HDD...
comment:9 by , 17 years ago
Replying to frank:
DevATA_FILETOOBIG means that you host file system is full. How much memory is free on the file system which contains the .vdi file?
Do you mean that even if my guest is 4Go and defined to be maximum 20Go i need 20Go free on my host disk to run the vm ??
comment:10 by , 17 years ago
No. But you located your .vdi file on the vfat partition, right? In this case the maximum file size is 4GB. This is a file system limit, not a VBox bug. Locate the file on a partition with another file system, for example on /dev/sda7 => /.
follow-up: 12 comment:11 by , 17 years ago
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
Actually the error message is quite clear to understand. The guest file system is irrelevant, take care of the host file system.
comment:12 by , 17 years ago
Replying to frank:
Actually the error message is quite clear to understand. The guest file system is irrelevant, take care of the host file system.
Well, i feal a little bit stupid... I was focused on the size of the file i tried to copy, but the probleme was the size of the virtual machine itself, like mentionned above... I moved my vdi on the ext3 partition and everything went well.
So now, i have some compatibility problems with some software, but this is another thing !
Thanks all of you for your explanations and patience !
What is your host OS and host filesystem ? What hardware ?
-Technologov