Die Foren-SW läuft ohne erkennbare Probleme. Sollte doch etwas nicht funktionieren, bitte gerne hier jederzeit melden und wir kümmern uns zeitnah darum. Danke!

VM kann nicht mehr zurück verschoben werden im VCNETER

Alles zum Thema vSphere 6, ESXi 6.0 und vCenter Server.

Moderatoren: irix, continuum, Dayworker

Member
Beiträge: 56
Registriert: 04.11.2016, 11:30

VM kann nicht mehr zurück verschoben werden im VCNETER

Beitragvon Mark_Le » 05.02.2017, 15:26

Hallo Leute,

ich habe hier ein VCEnter mit 2 Hosts alles Version HP 6.0.
Heute morgen verschob ich eine VM auf den 2. Host problemlos. Beim zurück verschieben kam nun folgende Meldung:
Die Datei /VMFs/vorulmes/55cf..... kann im Netzwerk nicht kopiert werden.

Hat zufällig jemand einen Tipp, weshalb die Migration abbricht?

zur VM selber W10Pro
Ich verschob Testweise eine andere VM von dem DATASTORE zum 2. mit keinerlei Problemen.

Vielen Dank im voraus!

King of the Hill
Beiträge: 13319
Registriert: 01.10.2008, 12:54
Wohnort: laut USV-Log am Ende der Welt...

Re: VM kann nicht mehr zurück verschoben werden im VCNETER

Beitragvon Dayworker » 05.02.2017, 15:39

Überprüfe Bitte mal deine gemachten Angaben und frage dich, ob du damit etwas anfangen könntest, wenn du den Server nicht vor dir stehen hättest.
Wenigstens die üblichen Log-Dateien hättest du ja mal präsentieren können, wo man die Fehlermeldung mal in Gänze lesen kann. Wir wissen bis jetzt nur, daß die Hosts HP-Geräte sind und irgendwas nicht geklappt hat. Sehr ungünstig ist natürlich die deutsche Benutzeroberfläche, da VMware weiterhin über eine den Sinn entstellende 1:1-Übersetzung nicht hinausgekommen ist und man mit diesem Kauderwelsch nicht mal eine Suchmaschine füttern kann.

Member
Beiträge: 56
Registriert: 04.11.2016, 11:30

Re: VM kann nicht mehr zurück verschoben werden im VCNETER

Beitragvon Mark_Le » 05.02.2017, 16:00

Wo genau bekomme ich ein detailierteres Logfile? Du meinst ja jetzt bestimmt nicht das Event Log aus dem Vsphere Client oder?
Sorry wegen der zu dünn gemachten Angaben. :( Das ahole ich noch nach. Müsste eben bloß wissen, was außer der VM-Version, OS-Version und lock noch wichtig wären für eine Analyse?

Besten Dank für die schnelle Antwort!

Member
Beiträge: 56
Registriert: 04.11.2016, 11:30

Re: VM kann nicht mehr zurück verschoben werden im VCNETER

Beitragvon Mark_Le » 05.02.2017, 16:38

Im LOGfile (DATASTORE) wurde das Ereignis gar nicht gelistet: EreignisID 134792'Cannot relocated virtual machine'
Was benötigst du noch dazu dazu?

Experte
Beiträge: 1335
Registriert: 25.04.2009, 11:17
Wohnort: Thüringen

Re: VM kann nicht mehr zurück verschoben werden im VCNETER

Beitragvon Supi » 05.02.2017, 17:34

Ich antworte mal für Daywalker:

1. Die komplette Fehlermeldung des Vcenters. Am Besten auf englisch.
(Client auf englisch starten: C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe -locale en_US )
2. die Log aus der VM-Verzeichnis.
3. genauer beschreiben, was man gemacht hat.

Also, Was genau hast du denn verschoben bzw. wie ?
VM von Host 1 nach Host 2?
SVMotion ?
ggf. über den Datastore Browser die VM dateien in einen anderen Ordner? ( was man nicht machen sollte?!)

Member
Beiträge: 56
Registriert: 04.11.2016, 11:30

Re: VM kann nicht mehr zurück verschoben werden im VCNETER

Beitragvon Mark_Le » 05.02.2017, 19:22

Okay, leider habe ich keinen englishen Client da, aber die Log ist English.
Insgesamt habe ich über die Migrate-Funktion im Vcenter auf anderen DATASTORE und HOST mirgeiren wollen. Heute morgen in die andere Richtung funktionierte es problemlos.

Hier die Fehlermeldung aus Vcenter:
Verlagern von virtuellen Maschinen
Servername r
Die Datei /vmfs/volumes/55cfe06c-1cad35d0-8955-e4115bbe5e5a/
Servername/servername.vmdk kann im Netzwerk nicht
kopiert werden.

hier die Logdatei:
2017-02-05T16:57:00.443Z| vcpu-1| I120: Starting copy guest manifest.
2017-02-05T16:57:00.499Z| vcpu-3| I120: HGFileCopyCreateSessionCB: Successfully created the session.
2017-02-05T16:57:00.507Z| vcpu-3| I120: ToolsLoadManifestFileCB: Queuing a request to update the manifest information.
2017-02-05T16:57:00.510Z| Worker#0| I120: GetHostManifests: Extracting the manifest file.
2017-02-05T16:57:00.545Z| Worker#0| I120: GetHostManifests: Done extracting the manifest file.
2017-02-05T16:57:00.568Z| Worker#0| I120: ToolsVersion: Status is supported new because this is status of monolithic version, and buslogic_win2k and 13 more components are missing from the guest.
2017-02-05T16:57:00.569Z| Worker#0| I120: ToolsVersionGetStatusWorkerThread: Tools status 4 derived from environment
2017-02-05T16:57:00.569Z| vmx| I120: ToolsUpdateManifestInfoWorkerThreadDone: Compared tools manifest from host and from the guest. Status = 4.
2017-02-05T16:57:00.569Z| vmx| I120: ToolsUpdateManifestInfoWorkerThreadDone: Updating the manifest info.
2017-02-05T16:57:00.569Z| vmx| I120: VMXVmdb_SetToolsVersionStatus: status value set to 'ok', 'supportedNew', install possible
2017-02-05T16:57:00.569Z| vmx| I120: TOOLS installed legacy version 10246, available legacy version 9536
2017-02-05T16:57:00.569Z| vmx| I120: TOOLS manifest update status is 4
2017-02-05T16:57:00.569Z| vmx| I120: TOOLS can be autoupgraded.
2017-02-05T16:57:00.569Z| vmx| I120: TOOLS Setting autoupgrade-checked TRUE.
2017-02-05T16:57:00.569Z| vmx| I120: RPT: Disabled. Skipped.
2017-02-05T16:57:00.717Z| vcpu-1| I120: TOOLS state change 3 returned status 1
2017-02-05T16:57:00.717Z| vcpu-1| I120: Vix: [982709 mainDispatch.c:4210]: VMAutomationReportPowerStateChange: Reporting power state change (opcode=2, err=0).
2017-02-05T16:57:08.546Z| mks| I120: SOCKET 5 (151) Creating VNC remote connection.
2017-02-05T16:57:08.612Z| mks| W110: VNCENCODE 5 failed to allocate VNCBlitDetect
2017-02-05T16:57:08.612Z| mks| W110: VNCENCODE 5 failed to allocate VNCBackBuffer
2017-02-05T16:57:31.472Z| vmx| I120: GuestRpc: Got error for connection 6:Remote connection failure
2017-02-05T16:57:31.704Z| vmx| I120: GuestRpc: Got error for connection 7:Remote connection failure
2017-02-05T16:57:32.703Z| vmx| I120: GuestRpc: Got error for connection 8:Remote connection failure
2017-02-05T16:57:33.718Z| vmx| I120: GuestRpc: Got error for connection 9:Remote connection failure
2017-02-05T16:57:34.718Z| vmx| I120: GuestRpc: Got error for connection 10:Remote connection failure
2017-02-05T16:57:35.720Z| vmx| I120: GuestRpc: Got error for connection 11:Remote connection failure
2017-02-05T16:57:36.721Z| vmx| I120: GuestRpc: Got error for connection 12:Remote connection failure
2017-02-05T16:57:37.735Z| vmx| I120: GuestRpc: Got error for connection 13:Remote connection failure
2017-02-05T16:57:38.334Z| vmx| I120: GuestRpcSendTimedOut: message to toolbox-dnd timed out.
2017-02-05T16:57:38.749Z| vmx| I120: GuestRpc: Got error for connection 14:Remote connection failure
2017-02-05T16:57:39.750Z| vmx| I120: GuestRpc: Got error for connection 15:Remote connection failure
2017-02-05T16:57:40.766Z| vmx| I120: GuestRpc: Got error for connection 16:Remote connection failure
2017-02-05T16:57:41.766Z| vmx| I120: GuestRpc: Got error for connection 17:Remote connection failure
2017-02-05T16:57:42.781Z| vmx| I120: GuestRpc: Got error for connection 18:Remote connection failure
2017-02-05T16:57:43.781Z| vmx| I120: GuestRpc: Got error for connection 19:Remote connection failure
2017-02-05T16:57:44.797Z| vmx| I120: GuestRpc: Got error for connection 20:Remote connection failure
2017-02-05T16:57:45.797Z| vmx| I120: GuestRpc: Got error for connection 21:Remote connection failure
2017-02-05T16:57:46.812Z| vmx| I120: GuestRpc: Got error for connection 22:Remote connection failure
2017-02-05T16:57:47.812Z| vmx| I120: GuestRpc: Got error for connection 23:Remote connection failure
2017-02-05T16:57:48.828Z| vmx| I120: GuestRpc: Got error for connection 24:Remote connection failure
2017-02-05T16:57:49.844Z| vmx| I120: GuestRpc: Got error for connection 25:Remote connection failure
2017-02-05T16:57:50.859Z| vmx| I120: GuestRpc: Got error for connection 26:Remote connection failure
2017-02-05T16:57:51.876Z| vmx| I120: GuestRpc: Got error for connection 27:Remote connection failure
2017-02-05T16:57:52.891Z| vmx| I120: GuestRpc: Got error for connection 28:Remote connection failure
2017-02-05T16:57:53.906Z| vmx| I120: GuestRpc: Got error for connection 29:Remote connection failure
2017-02-05T16:57:54.910Z| vmx| I120: GuestRpc: Got error for connection 30:Remote connection failure
2017-02-05T16:57:55.922Z| vmx| I120: GuestRpc: Got error for connection 31:Remote connection failure
2017-02-05T16:57:56.938Z| vmx| I120: GuestRpc: Got error for connection 32:Remote connection failure
2017-02-05T16:57:57.953Z| vmx| I120: GuestRpc: Got error for connection 33:Remote connection failure
2017-02-05T16:57:58.969Z| vmx| I120: GuestRpc: Got error for connection 34:Remote connection failure
2017-02-05T16:57:59.985Z| vmx| I120: GuestRpc: Got error for connection 35:Remote connection failure
2017-02-05T16:58:00.985Z| vmx| I120: GuestRpc: Got error for connection 36:Remote connection failure
2017-02-05T16:58:02.000Z| vmx| I120: GuestRpc: Got error for connection 37:Remote connection failure
2017-02-05T16:58:03.000Z| vmx| I120: GuestRpc: Got error for connection 38:Remote connection failure
2017-02-05T16:58:04.001Z| vmx| I120: GuestRpc: Got error for connection 39:Remote connection failure
2017-02-05T16:58:05.016Z| vmx| I120: GuestRpc: Got error for connection 40:Remote connection failure
2017-02-05T16:58:06.031Z| vmx| I120: GuestRpc: Got error for connection 41:Remote connection failure
2017-02-05T16:58:07.031Z| vmx| I120: GuestRpc: Got error for connection 42:Remote connection failure
2017-02-05T16:58:08.047Z| vmx| I120: GuestRpc: Got error for connection 43:Remote connection failure
2017-02-05T16:58:09.063Z| vmx| I120: GuestRpc: Got error for connection 44:Remote connection failure
2017-02-05T16:58:10.078Z| vmx| I120: GuestRpc: Got error for connection 45:Remote connection failure
2017-02-05T16:58:11.078Z| vmx| I120: GuestRpc: Got error for connection 46:Remote connection failure
2017-02-05T16:58:12.093Z| vmx| I120: GuestRpc: Got error for connection 47:Remote connection failure
2017-02-05T16:58:13.093Z| vmx| I120: GuestRpc: Got error for connection 48:Remote connection failure
2017-02-05T16:58:14.109Z| vmx| I120: GuestRpc: Got error for connection 49:Remote connection failure
2017-02-05T16:58:15.109Z| vmx| I120: GuestRpc: Got error for connection 50:Remote connection failure
2017-02-05T16:58:16.110Z| vmx| I120: GuestRpc: Got error for connection 51:Remote connection failure
2017-02-05T16:58:17.111Z| vmx| I120: GuestRpc: Got error for connection 52:Remote connection failure
2017-02-05T16:58:18.111Z| vmx| I120: GuestRpc: Got error for connection 53:Remote connection failure
2017-02-05T16:58:19.125Z| vmx| I120: GuestRpc: Got error for connection 54:Remote connection failure
2017-02-05T16:58:20.125Z| vmx| I120: GuestRpc: Got error for connection 55:Remote connection failure
2017-02-05T16:58:21.125Z| vmx| I120: GuestRpc: Got error for connection 56:Remote connection failure
2017-02-05T16:58:22.141Z| vmx| I120: GuestRpc: Got error for connection 57:Remote connection failure
2017-02-05T16:58:23.156Z| vmx| I120: GuestRpc: Got error for connection 58:Remote connection failure
2017-02-05T16:58:24.156Z| vmx| I120: GuestRpc: Got error for connection 59:Remote connection failure
2017-02-05T16:58:25.173Z| vmx| I120: GuestRpc: Got error for connection 60:Remote connection failure
2017-02-05T16:58:26.188Z| vmx| I120: GuestRpc: Got error for connection 61:Remote connection failure
2017-02-05T16:58:27.203Z| vmx| I120: GuestRpc: Got error for connection 62:Remote connection failure
2017-02-05T16:58:28.203Z| vmx| I120: GuestRpc: Got error for connection 63:Remote connection failure
2017-02-05T16:58:29.219Z| vmx| I120: GuestRpc: Got error for connection 64:Remote connection failure
2017-02-05T16:58:30.234Z| vmx| I120: GuestRpc: Got error for connection 65:Remote connection failure
2017-02-05T16:58:31.235Z| vmx| I120: GuestRpc: Got error for connection 66:Remote connection failure
2017-02-05T16:58:32.250Z| vmx| I120: GuestRpc: Got error for connection 67:Remote connection failure
2017-02-05T16:58:33.249Z| vmx| I120: GuestRpc: Got error for connection 68:Remote connection failure
2017-02-05T16:58:34.252Z| vmx| I120: GuestRpc: Got error for connection 69:Remote connection failure
2017-02-05T16:58:35.252Z| vmx| I120: GuestRpc: Got error for connection 70:Remote connection failure
2017-02-05T16:58:36.266Z| vmx| I120: GuestRpc: Got error for connection 71:Remote connection failure
2017-02-05T16:58:37.266Z| vmx| I120: GuestRpc: Got error for connection 72:Remote connection failure
2017-02-05T16:58:38.266Z| vmx| I120: GuestRpc: Got error for connection 73:Remote connection failure
2017-02-05T16:58:39.282Z| vmx| I120: GuestRpc: Got error for connection 74:Remote connection failure
2017-02-05T16:58:40.282Z| vmx| I120: GuestRpc: Got error for connection 75:Remote connection failure
2017-02-05T16:58:41.283Z| vmx| I120: GuestRpc: Got error for connection 76:Remote connection failure
2017-02-05T16:58:42.297Z| vmx| I120: GuestRpc: Got error for connection 77:Remote connection failure
2017-02-05T16:58:43.297Z| vmx| I120: GuestRpc: Got error for connection 78:Remote connection failure
2017-02-05T16:58:44.300Z| vmx| I120: GuestRpc: Got error for connection 79:Remote connection failure
2017-02-05T16:58:45.313Z| vmx| I120: GuestRpc: Got error for connection 80:Remote connection failure
2017-02-05T16:58:46.328Z| vmx| I120: GuestRpc: Got error for connection 81:Remote connection failure
2017-02-05T16:58:47.328Z| vmx| I120: GuestRpc: Got error for connection 82:Remote connection failure
2017-02-05T16:58:48.345Z| vmx| I120: GuestRpc: Got error for connection 83:Remote connection failure
2017-02-05T16:58:49.344Z| vmx| I120: GuestRpc: Got error for connection 84:Remote connection failure
2017-02-05T16:58:50.360Z| vmx| I120: GuestRpc: Got error for connection 85:Remote connection failure
2017-02-05T16:58:51.375Z| vmx| I120: GuestRpc: Got error for connection 86:Remote connection failure
2017-02-05T16:58:52.375Z| vmx| I120: GuestRpc: Got error for connection 87:Remote connection failure
2017-02-05T16:58:53.378Z| vmx| I120: GuestRpc: Got error for connection 88:Remote connection failure
2017-02-05T16:58:54.391Z| vmx| I120: GuestRpc: Got error for connection 89:Remote connection failure
2017-02-05T16:58:55.393Z| vmx| I120: GuestRpc: Got error for connection 90:Remote connection failure
2017-02-05T16:58:56.393Z| vmx| I120: GuestRpc: Got error for connection 91:Remote connection failure
2017-02-05T16:58:57.391Z| vmx| I120: GuestRpc: Got error for connection 92:Remote connection failure
2017-02-05T16:58:58.393Z| vmx| I120: GuestRpc: Got error for connection 93:Remote connection failure
2017-02-05T16:58:59.406Z| vmx| I120: GuestRpc: Got error for connection 94:Remote connection failure
2017-02-05T16:59:00.407Z| vmx| I120: GuestRpc: Got error for connection 95:Remote connection failure
2017-02-05T16:59:01.408Z| vmx| I120: GuestRpc: Got error for connection 96:Remote connection failure
2017-02-05T16:59:02.409Z| vmx| I120: GuestRpc: Got error for connection 97:Remote connection failure
2017-02-05T16:59:03.422Z| vmx| I120: GuestRpc: Got error for connection 98:Remote connection failure
2017-02-05T16:59:04.438Z| vmx| I120: GuestRpc: Got error for connection 99:Remote connection failure
2017-02-05T16:59:05.453Z| vmx| I120: GuestRpc: Got error for connection 100:Remote connection failure
2017-02-05T16:59:06.453Z| vmx| I120: GuestRpc: Got error for connection 101:Remote connection failure
2017-02-05T16:59:07.469Z| vmx| I120: GuestRpc: Got error for connection 102:Remote connection failure
2017-02-05T16:59:08.469Z| vmx| I120: GuestRpc: Got error for connection 103:Remote connection failure
2017-02-05T16:59:09.485Z| vmx| I120: GuestRpc: Got error for connection 104:Remote connection failure
2017-02-05T17:00:47.813Z| vmx| I120: GuestRpc: Got error for connection 204:Remote connection failure
2017-02-05T17:00:50.003Z| mks| I120: SSL: syscall error 104: Connection reset by peer
2017-02-05T17:00:50.003Z| mks| I120: SOCKET 5 (151) recv error 104: Connection reset by peer
2017-02-05T17:00:50.003Z| mks| I120: SOCKET 5 (151) VNC Remote Disconnect.
2017-02-05T17:02:28.580Z| vmx| I120: GuestRpc: Got error for connection 304:Remote connection failure
2017-02-05T17:04:09.469Z| vmx| I120: GuestRpc: Got error for connection 404:Remote connection failure


Zurück zu „vSphere 6.0“

Wer ist online?

Mitglieder in diesem Forum: 0 Mitglieder und 1 Gast