[vbox-dev] VirtualBox Teleporting ... A follow-up question ... Interesting observation ...

[Joseph Smith]

Hi,

Cool ... I can live with that.  The purpose of teleporting in my solution thus 
far is primarily to move VMs to another host so the original host can be taken 
offline usually for modification/upgrade/repair.  Once the original host is back 
online, the VMs will be teleported 'back'.

At some point in the future, the automated teleporting operation will be used to 
load balance a host that might get overwhelmed.

For now, I'll simply use VBoxManage to clear the flag ... and hope that a near 
future release addresses it before I need to handle supporting dynamic 
teleporting back and forth.

Thanks !!!

Joe



________________________________
From: Knut Osmundsen <knut.osmundsen at oracle.com>
To: vbox-dev at virtualbox.org
Sent: Wed, September 29, 2010 12:41:17 PM
Subject: Re: [vbox-dev] VirtualBox Teleporting ... A follow-up question ... 
Interesting observation ...


On Sep 28, 2010, at 7:58 PM, Joseph Smith wrote:

Hi All,
>
>I made the updates based on the suggestions ... with those updates, teleporting 
>any VM has been working reliably in all scenarios regardless of load or 
>performance of the source and target systems.
>
>An observation I have made:  The 'teleporterEnabled' flag is still set on the 
>'source' VM.  I'm guessing it would be my responsibility to reset that flag.  
>Hmmm ... not a big deal ... I can do that.
>
>The interesting part however is:  The target machine, once it is shut-down (at 
>any point after it was teleported), seems to believe it is still in 
>'to-be-teleported' mode.  Therefore, trying to start a target VM that was 
>previously teleported shows the teleporting-in modal dialog.  At this point, the 
>VM is not start-able.
>
>Problem is ... once the teleport has happened ... I will not be able to make any 
>updates to the target VM to reset the teleporterEnabled flag.  To do this ... it 
>implies I would have to persist this information somehow so that after the VM is 
>shutdown or just before an attempt to restart, try to reset the flag.  Though 
>clunky, this would work OK with my UI ... but would still be a problem for users 
>that use the QT UI also.
>
>I would think the resetting of the teleporterEnabled flag on both the source and 
>target VMs should be part of the teleport request itself if the teleport was 
>successful.
>
>Any suggestions on how to 'reset' the target VM teleporterEnabled flag so a 
>restart does not cause it to want to teleport-in again ?
>
>Am I missing something ?  Is this a bug ?
>
>

There is disabled code that tries to clear the teleporterEnabled flag, however 
it was disabled because it didn't work / was incomplete. The problem has to do 
with saving the VM settings at that point in time. It will be addressed in one 
of the next releases, I hope.

-- 

Kind regards / Mit freundlichen Gruessen / Vennlig hilsen,
 bird

--

ORACLE Deutschland B.V. & Co. KG  Knut St. Osmundsen
Werkstrasse 24                    Senior Staff Engineer, VirtualBox
71384 Weinstadt, Germany          mailto:bird at sun.com

Hauptverwaltung: Riesstr. 25, D-80992 Muenchen
Registergericht: Amtsgericht Muenchen, HRA 95603

Komplementaerin: ORACLE Deutschland Verwaltung B.V.
Rijnzathe 6, 3454PV De Meern, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschaeftsfuehrer: J. Kunz, M. van de Molen, A. van der Ven 



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20100929/ba6f4098/attachment.html>