VirtualBox

Changes between Initial Version and Version 1 of Ticket #4034


Ignore:
Timestamp:
May 18, 2009 10:06:38 AM (15 years ago)
Author:
Frank Mehnert
Comment:

This is already fixed in SVN. The reason for the problem was that the output format of VBoxManage list runningvms changed. Why do you need the sudo command? Stopping the VM should actually work as super user without doing sudo as we set VBOX_IPC_SOCKETID.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4034 – Description

    initial v1  
    55I have made the following modification to the stop_vm function to make it work.
    66
    7 
    8   elif [ "$SHUTDOWN" = "savestate" ]; then
    9                     begin_msg "Saving state of remaining VMs"
    10                     for v in $VMS; do
    11                         v=`echo ${v:1}`
    12                         v=`echo ${v%\"}`
    13                         sudo -H -u $i $VBOXMANAGE -nologo controlvm $v savestate
    14                     done
    15                     succ_msg
    16 
    17 
     7{{{
     8elif [ "$SHUTDOWN" = "savestate" ]; then
     9    begin_msg "Saving state of remaining VMs"
     10    for v in $VMS; do
     11        v=`echo ${v:1}`
     12        v=`echo ${v%\"}`
     13        sudo -H -u $i $VBOXMANAGE -nologo controlvm $v savestate
     14    done
     15    succ_msg
     16}}}
    1817I am using VirtualBox 2.2.2. and Ubuntu 8.0.4.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette