Jump to content
Updated Privacy Statement
  • 0

Help my please


And Gri

Question

Hello. Please tell me I have a problem. I will describe the situation. There is a Maypol pool - it has 4 hosts. 1 of them (let's call it X1)5ca3144ee31b0_2019-04-0210_41_48.thumb.png.9a5306ff170eaf9574f35d5a61d8a738.png is physically out of order. The admin server was spinning on X1 - and there was no backup. But when I entered the he-vm-list command, it is an X1 virtual machine — it works. BUT in her there is no. When I want to turn off the X1 screen. What do i do?
Xenserver 7.25ca3144d76783_2019-04-0210_49_39.thumb.png.b90500f22ecdc5930e45cf656dcacbbb.png

Link to comment

15 answers to this question

Recommended Posts

I turned it off with this command - xe vm-reset-powerstate force uuid = e08b716a-9972-a1de-7d65-a7a8cc5c627d

Now I want to run -
xe vm-start force uuid = e08b716a-9972-a1de-7d65-a7a8cc5c627d
Error: Failed to parse parameter 'force': expecting 'true' or 'false'
[root @ xenserver-u2 ~] # xe vm-start uuid = e08b716a-9972-a1de-7d65-a7a8cc5c627d
VM on.
The following table could not be started:

xenserver-u2: Cannot start here [VM requires access to SR: 35007d05-97b0-7a4a-67fc-10433a2c1e7a (Local storage)]
    xenserver-u4: Cannot start here [Host down]
    xenserver-u1: Cannot start here [VM requires access to SR: 35007d05-97b0-7a4a-67fc-10433a2c1e7a (Local storage)]


There were no hosts available.

How do i run it on hosts x1 or x2?
Why I can not run it on host X4 - because he died - physically spilled raid

Link to comment

The proper syntax is:

xe vm-reset-powerstate uuid=e08b716a-9972-a1de-7d65-a7a8cc5c627d --force

 

It  didn't accept your power state reset  command and is still in that bad state.

 

Note that you can sometime only restart a VM in a "bad" state typically on the same host it was running on unless the VM can be quieseced and even then, it's occasionally necessary to reboot the host it was on to "free" it.

 

-=Tobias

Link to comment
34 minutes ago, Tobias Kreidl said:

The proper syntax is:

xe vm-reset-powerstate uuid=e08b716a-9972-a1de-7d65-a7a8cc5c627d --force

 

It  didn't accept your power state reset  command and is still in that bad state.

 

Note that you can sometime only restart a VM in a "bad" state typically on the same host it was running on unless the VM can be quieseced and even then, it's occasionally necessary to reboot the host it was on to "free" it.

 

-=Tobias

At the moment it is turned off (screenshot) trying to run it on host 1. And I wrote this message 

 

If I do a he-vm-start command, uuid = e08b716a-9972-a1de-7d65-a7a8cc5c627d then I write this 

 

[root @ xenserver-u2 ~] # xe vm-start uuid = e08b716a-9972-a1de-7d65-a7a8cc5c627d
VM on.
The following table could not be started:

xenserver-u2: Cannot start here [VM requires access to SR: 35007d05-97b0-7a4a-67fc-10433a2c1e7a (Local storage)]
    xenserver-u4: Cannot start here [Host down]
    xenserver-u1: Cannot start here [VM requires access to SR: 35007d05-97b0-7a4a-67fc-10433a2c1e7a (Local storage)]


There were no hosts available.

 

If I want to migrate VM SRV2-ADMINS (uuid=35007d05-97b0-7a4a-67fc-10433a2c1e7a)then he writes this

[root @ xenserver-u2 ~] # xe vm-migrate remote-master = 192.168.50.100 remote-username = root remote-password = password vm = SRV2-ADMINS live = true force = true
Performing a Storage XenMotion migration. Your VM's VDIs will be migrated with the VM.
SRD for migrating VDIs
Will migrate to remote host: xenserver-u2, using remote network: Bond 0 + 1. Here is the VDI mapping:
VDI f9de7144-8339-4976-bdbf-e6d03dd3b2ed -> SR 4e5f0c78-8a3e-f248-b7b7-7c01cb9c94a2
VDI e873bf0d-7c2c-439f-90d8-05832c2bc63d -> SR 4e5f0c78-8a3e-f248-b7b7-7c01cb9c94a2
There were no hosts available.


Maybe I initially did something wrong - I need to start the VM that was enabled on the host 4 - SRV2-ADMINS
How should I be in this situation?

Снимок экрана 2019-04-03 в 10.59.14.png

Link to comment

I think it's stuck after you tried to migrate it, so it's in a weird state. I had that happen recently, as well. In the end, I think I had to reboot the host to clear out all the stale VM states. The fact that local storage gives an error points to the system being in an odd state; an xe-toolstack-restart won't hurt but probably won't help If the host in question is not the master, you could also try a "xe pool-sync-database" to make sure it's synchronized OK with the master.

 

-=Tobias

Link to comment

xenserver-u4 does not work I wrote about it in the above - it failed RAID. It is not possible to restore it. But this host is still in the pool. If I add another server to the pool named xenserver-u4 - will it help me to restore my VM SRV2-ADMINS?

Link to comment

That will not work because the replacement host will have a differnet host UUID assigned to it.

 

If the server is failed. you should permanently eject it from the pool:

xe pool-eject host-uuid=(host_uuid)

 

If that does not work, you may have to force a forget:

xe host-forget uuid=(host_uuid)

 

-=Tobias

Link to comment

I removed the xenserver-u4 server from the pool. I installed XE on a new physical server named Xenserver-u4 and add it to the pool. I started VM xe vm-start uuid = e08b716a-9972-a1de-7d65-a7a8cc5c627d - it started on host-4 but does not work. For some reason, it does not have a storage disk. But I have a lot of files on the NFS. Can I connect them to the VM and find the disk I need?

Снимок экрана 2019-04-04 в 14.15.43.png

Link to comment
17 hours ago, Tobias Kreidl said:

You should be able to import/attach them like any VHD file into a VM and; even without metadata you may be able to figure out what the original VM was based on its content.

 

-=Tobias

I cannot attach a disk to VM SRV2-Admins this function is inactive

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...