Custom Query (16363 matches)
Results (2374 - 2376 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11172 | obsolete | 5.25 inch floppy image wont work/mount correctly in Virtual Box | ||
| Description |
I discovered some old 5.25 inch (360 KB and 1.2 MB) Floppy Disks which I scanned with WinImage to generate *.IMA-files, they mounts correctly in Virtual Box and I can run DOS 5.0 and 6.22 as VMs. However when trying to format the floppy images from within the VMs, VirtualBox seems to assume that all floppy images is of 1.44 MB size and thereby crashes and corrupts the *.IMA files. Also the same problem seems to occur when using 720 KB floppy images. I know that this might be an obsolete feature, but the fact was that I had very old backups on these floppys, which I thought I had lost, and it was fun to rediscover them. However I needed to creat a DOS 5.0 and 6.22 VM in order to unpack and use the backups. (With todays PC hardware its not possible to install an old DOS 5.x or 6.x system, therefore using VMs instead) Besides that VirtualBox seems not to be able to mount *.IMZ files created by WinImage (= compressed IMA-files) There is another strange behaviour of VirtualBox when running DOS 5.x and 6.x as VMs and its that the VMs tends to almost lock the CPU at 50-100 % load all the time. Also character mode DOS apps, like Borland TurboPascal and EDIT.EXE cannot be correctly resized when run in DOS as VM, the window remains small. |
|||
| #11174 | obsolete | Add Support for Foresight Linux | ||
| Description |
To add support for the Foresight Linux distribution to vboxadd guest additions. A few very simple changes are required in the vboxadd and vboxadd-service startup scripts. Mainly these changes are to check for the existence of /etc/conaryrc, and if so set system to foresight. Then wherever system=redhat, foresight will also use those functions. However, the pidfile needs to change from /var/lock/subsys/vboxadd-service to /var/lock/subsys/vboxadd because foresight scripts don't look for "-service" when navigating scripts at shutdown time. This means that without these changes, vboxsf mounts do not get unmounted when the box is shutdown or reboot. A patch to apply against the latest version of vbox guest tools to support foresight linux follows. So far, my testing with these changes to the init scripts for vboxadd and vboxadd-service work perfectly with the Foresight distribution. --- orig/vboxadd 2012-11-07 22:54:55.000000000 -0700
+++ new/vboxadd 2012-11-07 22:50:30.000000000 -0700
@@ -65,6 +65,8 @@
system=gentoo
elif [ -f /etc/lfs-release -a -d /etc/rc.d/init.d ]; then
system=lfs
+elif [ -f /etc/conaryrc ]; then
+ system=foresight
else
system=other
fi
@@ -85,7 +87,7 @@
}
fi
-if [ "$system" = "redhat" ]; then
+if [ "$system" = "redhat" ] || [ "$system" = "foresight" ]; then
. /etc/init.d/functions
fail_msg() {
echo_failure
diff -Nuar orig/vboxadd-service new/vboxadd-service
--- orig/vboxadd-service 2012-11-07 22:55:03.000000000 -0700
+++ new/vboxadd-service 2012-11-07 22:50:41.000000000 -0700
@@ -49,6 +49,9 @@
elif [ -f /etc/lfs-release ]; then
system=lfs
PIDFILE="/var/run/vboxadd-service.pid"
+elif [ -f /etc/conaryrc ]; then
+ system=foresight
+ PIDFILE="/var/lock/subsys/vboxadd"
else
system=other
if [ -d /var/run -a -w /var/run ]; then
@@ -56,7 +59,7 @@
fi
fi
-if [ "$system" = "redhat" ]; then
+if [ "$system" = "redhat" ] || [ "$system" = "foresight" ] ; then
. /etc/init.d/functions
fail_msg() {
echo_failure
|
|||
| #11179 | obsolete | Bug beim Klonen von Shared Disks | ||
| Description |
"VBoxManage clonevm" hängt, wenn andere User der Shared Disk gestoppt sind. Wenn andere VMs die Shared Disk benutzen, bringt "VBoxManage clonevm" VBox komplett zum Absturz, und zwar sowohl das Clone-Kommando, als auch andere laufende VMs! Während "VBoxManage clonevm" hängt, sieht das Verzeichnis der VM wie folgt aus: user@host:~$ ls -l insgesamt 3994112 -rw------- 1 virtualbox virtualbox 626 Jun 24 13:24 ub-12.04-a-disk1.vmdk -rw------- 1 virtualbox virtualbox 4089614336 Jun 24 13:24 ub-12.04-a.vdi Vermutlich/anscheinend gibt es hohe Plattenaktivität, während die reale Disk auf sich selber kopiert wird ... Grundsätzlich sollte "clonevm" bei angehängten Shared Disks die Disk-Beschreibung NICHT ändern, sondern weiterhin auf die bestehende VMDK-Datei verweisen. |
|||

