Re: [ovirt-users] After realizing HA migration, the virtual machine can still get the virtual machine information by using the "vdsm-client host getVMList" instruction on the host before the migration

2018-02-08 Thread Petr Kotas
Hi Pym, the feature is know in testing. I am not sure when it will be released, but I hope for sooner date. Petr On Tue, Feb 6, 2018 at 12:36 PM, Pym wrote: > Thank you very much for your help, so is this patch released now? Where > can I get this patch? > > > > > > > At 2018-02-05 20:52:04, "

Re: [ovirt-users] After realizing HA migration, the virtual machine can still get the virtual machine information by using the "vdsm-client host getVMList" instruction on the host before the migration

2018-02-05 Thread Petr Kotas
Hi, I have experimented on the issue and figured out the reason for the original issue. You are right, that the vm1 is not properly stopped. This is due to the known issue in the graceful shutdown introduced in the ovirt 4.2. The vm on the host in shutdown are killed, but are not marked as stoppe

Re: [ovirt-users] After realizing HA migration, the virtual machine can still get the virtual machine information by using the "vdsm-client host getVMList" instruction on the host before the migration

2018-02-02 Thread Simone Tiraboschi
On Thu, Feb 1, 2018 at 1:06 PM, Pym wrote: > The environment on my side may be different from the link. My VM1 can be > used normally after it is started on host2, but there is still information > left on host1 that is not cleaned up. > > Only the interface and background can still get the inform

Re: [ovirt-users] After realizing HA migration, the virtual machine can still get the virtual machine information by using the "vdsm-client host getVMList" instruction on the host before the migration

2018-02-01 Thread Pym
The environment on my side may be different from the link. My VM1 can be used normally after it is started on host2, but there is still information left on host1 that is not cleaned up. Only the interface and background can still get the information of vm1 on host1, but the vm2 has been succes

Re: [ovirt-users] After realizing HA migration, the virtual machine can still get the virtual machine information by using the "vdsm-client host getVMList" instruction on the host before the migration

2018-02-01 Thread Simone Tiraboschi
On Thu, Feb 1, 2018 at 2:21 AM, Pym wrote: > > I checked the vm1, he is keep up state, and can be used, but on host1 has > after shutdown is a suspended vm1, this cannot be used, this is the problem > now. > > In host1, you can get the information of vm1 using the "vdsm-client Host > getVMList",

Re: [ovirt-users] After realizing HA migration, the virtual machine can still get the virtual machine information by using the "vdsm-client host getVMList" instruction on the host before the migration

2018-01-31 Thread Simone Tiraboschi
On Wed, Jan 31, 2018 at 12:46 PM, Pym wrote: > Hi: > > The current environment is as follows: > > Ovirt-engine version 4.2.0 is the source code compilation and > installation. Add two hosts, host1 and host2, respectively. At host1, a > virtual machine is created on vm1, and a vm2 is created on ho

[ovirt-users] After realizing HA migration, the virtual machine can still get the virtual machine information by using the "vdsm-client host getVMList" instruction on the host before the migration.

2018-01-31 Thread Pym
Hi: The current environment is as follows: Ovirt-engine version 4.2.0 is the source code compilation and installation. Add two hosts, host1 and host2, respectively. At host1, a virtual machine is created on vm1, and a vm2 is created on host2 and HA is configured. Operation steps: Use the