Any idea what I’m doing wrong?

p, li { white-space: pre-wrap; }

p, li { white-space: pre-wrap;
Failed to open the hard disk /home/xxx/win7.vmdk.
The medium ‘/home/xxx/win7.vmdk’ can’t be used as the requested device type.Deatails show the following:
p, li { white-space: pre-wrap; }

Result Code:
NS_ERROR_FAILURE (0×80004005)
Component:
Medium
Interface:
IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
Callee:
IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}

#! /bin/bash
# Windows 7 VM boot script for VirtualBox 4.x– you’ll have to always use it instead of running VirtualBox
VBUSER=virtualbox          # name of custom account created (which is a member of disk group)
VM_NAME=Win7           # name of virtual machine

wait_for_closing_machines() {
RUNNING_MACHINES=`sudo -u $VBUSER VBoxManage list runningvms | wc -l`
if [ $RUNNING_MACHINES != 0 ]; then
sleep 5
wait_for_closing_machines
fi
}

sudo chown -R $USER:users /home/$USER/.VirtualBox    # make sure $VBUSER will be able to access VirtualBox settings etc.
                                                     # we use sudo because $VBUSER creates files with its ownership on previous runs
sudo chmod -R g=u /home/$USER/.VirtualBox                 # $VBOXUSER permissions should be the same as ours
sudo chown -R $USER:users /home/$USER/VirtualBox VMs/$VM_NAME    # ditto for VirtualBox VMs directory.
sudo chmod -R g=u /home/$USER/VirtualBox VMs/$VM_NAME

xauth extract /home/$USER/cookieTmp $DISPLAY

chmod g+r /home/$USER/cookieTmp
sudo chmod g+x /home/$USER/

sudo -u $VBUSER XAUTHORITY=/tmp/.Xauthority_$VBUSER xauth merge /home/$USER/cookieTmp
rm /home/$USER/cookieTmp

sudo -u $VBUSER DISPLAY=:0 XAUTHORITY=/tmp/.Xauthority_$VBUSER VBOX_USER_HOME=/home/$USER/.VirtualBox VBoxManage startvm $VM_NAME
#sudo -u $VBUSER DISPLAY=:0 XAUTHORITY=/tmp/.Xauthority_$VBUSER VBOX_USER_HOME=/home/$USER/.VirtualBox virtualbox

echo “Waiting for shutdown of $VM_NAME”
wait_for_closing_machines
echo “$VM_NAME shutdown. Resetting permissions.”
sudo chown -R $USER:users /home/$USER/.VirtualBox    # make sure $VBUSER will be able to access VirtualBox settings etc.
                                                     # we use sudo because $VBUSER creates files with its ownership on previous runs
sudo chmod -R g-rw /home/$USER/.VirtualBox/*                 # $VBOXUSER permissions should be the same as ours
sudo chown -R $USER:users /home/$USER/VirtualBox VMs/$VM_NAME    # ditto for VirtualBox VMs directory.
sudo chmod -R g-rw /home/$USER/VirtualBox VMs/$VM_NAME