Opened 15 years ago
Closed 14 years ago
#5384 closed defect (fixed)
VB 3.0.x crashes when creating loop file
Reported by: | romarin12 | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 3.0.10 |
Keywords: | Fedora 11, loop file | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description
Hi All,
Virtual Box (3.0.8 & 3.0.10 , Vistax64 host) crashes every time I launch the code below as root on a Fedora11x64 guest. This code works on a 'real' Fedora11 box, and is meant to create a file system image (via a loop file) to be used as a customized Amazon EC2 AMI. The crashes occurs after about 5 mins, half way through the rpm downloads. The VM simply stops and Vista tries and fails (hangs) to send a crash report. The previous Virtual Box version (2.2) worked fine.
Thanks for all the good work,
Olivier.
#!/bin/sh ver=11 arch=x86_64 loop=loop_F11x64 # clear stuff umount -d /mnt/$loop/proc umount -d /mnt/$loop rm -fR /mnt/$loop rm -f fc$ver-$arch.img # create file system image dd if=/dev/zero of=fc$ver-$arch.img bs=1M count=1 seek=9500 /sbin/mke2fs -F -j fc$ver-$arch.img # mount image as loop file mkdir /mnt/$loop mount -o loop fc$ver-$arch.img /mnt/$loop # create some basic directories mkdir /mnt/$loop/dev mkdir /mnt/$loop/proc mkdir /mnt/$loop/etc for i in console null zero ; do /sbin/MAKEDEV -d /mnt/$loop/dev -x $i ; done # create basic fstab cat <<EOL > /mnt/$loop/etc/fstab /dev/sda1 / ext3 defaults 1 1 /dev/sdb /mnt ext3 defaults 0 0 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 EOL # create proc dir mkdir /mnt/$loop/proc mount -t proc none /mnt/$loop/proc # create local yum conf file for Fedora cat <<EOL > ./yumec2.conf [main] cachedir=/var/cache/yum debuglevel=2 logfile=/var/log/yum.log exclude=*-debuginfo gpgcheck=0 obsoletes=1 reposdir=/dev/null [base] name=Fedora Core $ver - $arch - Base mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$ver&arch=$arch enabled=1 [updates-released] name=Fedora Core $ver - $arch - Released Updates mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f$ver&arch=$arch enabled=1 EOL # install base packages into image yum -c ./yumec2.conf --installroot=/mnt/$loop -y groupinstall Base yum -c ./yumec2.conf --installroot=/mnt/$loop -y clean packages # cleaning mv /mnt/$loop/lib/tls /mnt/$loop/lib/tls-disabled mv /mnt/$loop/lib64/tls /mnt/$loop/lib64/tls-disabled # flush file system buffers sync # unmount umount -d /mnt/$loop/proc umount -d /mnt/$loop
Attachments (3)
Change History (13)
by , 15 years ago
Attachment: | VB-crash-shot.PNG added |
---|
comment:3 by , 15 years ago
priority: | trivial → critical |
---|
comment:4 by , 15 years ago
Are you running that script on a shared folder, that is, is the current directory a shared folder when you run this script?
comment:5 by , 15 years ago
Hi Frank; I am running this script on a subfolder of /root . NOT a shared folder.
comment:6 by , 15 years ago
Hi sandervl73 ; This is reproducible on this VirtualBox/Vistax64. I am currently setting-up VB and a clean Fedora11 guest onto another Vista host(32bits), in order to check for reproducibility in another environment.
comment:7 by , 15 years ago
On the Vista 64bit host I have, after removing and re-installing VB 3.0.10, I experience the same crash with a clean ('out-of-the-box') Fedora 11 x64 guest. See screen capture:
http://www.virtualbox.org/attachment/ticket/5384/VB-crash-shot-cleaninstall.PNG
I cannot reproduce this on the Vista 32bit host I have.
comment:8 by , 14 years ago
the assumption here is that this is somehow to do with the loop file.... But if I understand this correctly, you are doing major *network downloads* of files that you are saving to the loop disk. and you are crashing half-way through the download.
I wonder if this is actually a network bug instead??? there seems to be several problems with networking - for instance see bug #3318. Can you reproduce this crash by saving the downloaded files to a local directory instead?
comment:9 by , 14 years ago
Thanks for following-up of this!
Unfortunately, I cannot reproduce this bug any more, as I don't work with MS Windows any more...
Anyway, I have just tested again the above code: it now works fine on a Fedora14x64 host/virtual machine running VB4.0.4
Please note that when I originally posted this bug, it did not occur on a Vista 32 bit host, but only on a Vista 64 bit, so this is not in favor of the network bug option.
comment:10 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
So let's close this ticket. Reopen if necessary.
screen capture