ganeti / ganeti

Ganeti is a virtual machine cluster management tool built on top of existing virtualization technologies such as Xen or KVM and other open source software.
http://www.ganeti.org
BSD 2-Clause "Simplified" License
516 stars 110 forks source link

gnt-instance migrate error (vif-ganeti) #1224

Open Ganeti-Issues-Migrator opened 7 years ago

Ganeti-Issues-Migrator commented 7 years ago

Originally reported of Google Code with ID 1171.

Hello everybody,

What software version are you running? Please provide the output of "gnt-
cluster --version", "gnt-cluster version", and "hspace --version".

gnt-cluster (ganeti 2.15.2-1~bpo8+1) 2.15.2
hspace (ganeti) version 2.15.2-1~bpo8+1
compiled with ghc 7.6
running on linux x86_64

<b>What distribution are you using?</b>

Debian Jessie - Xen 4.4 (toolstack = xl)

<b>What steps will reproduce the problem?</b>
1.create instance
2.gnt-instance migrate "instance"

Failed with error (libxl not reading ready message.......)

In the file : /etc/xen/scripts/vif-ganeti (lig. 47):

domname=$(xm domname $domid)  => It should be 'xl' command 

and, this command return : instancename----incoming/0

so, at line 53:

source $NIC_DIR/$domname/$devid => issue an error in xen-hotplug (file not found)... because of the '---incoming' in the name of the file...

I think this is why the migration failed ? 

perhaps there is a workaround ? or a patch ? thank you for helping me, I am very new to ganeti and I don't want to break everything...

sorry for my english, I am french

best regards,
stephane ouvrard

Originally added on 2016-02-17 13:33:15 +0000 UTC.

Ganeti-Issues-Migrator commented 7 years ago
Hi Stephane,
Thanks for reporting this bug. It is definitely an issue with xl support. We are using a different network setup however, so can't reproduce it. Patches are very welcome though.

Originally added on 2016-02-29 11:54:16 +0000 UTC.

Changed State: PatchesWelcome

Ganeti-Issues-Migrator commented 7 years ago
domname=$(xm domname $domid)  => It should be 'xl' command -> No, it should be whatever the xen_cmd setting is for the cluster.

But right now it's hardcoded in the script, so it's borked.

Originally added on 2016-07-06 12:20:38 +0000 UTC.

apoikos commented 6 years ago

xm is long obsolete (since Xen 4.1) and removed in Xen 4.5. It's time to switch everything to xl and drop the xen_cmd-related logic.