yes!,
host A x86_64
host B x86_64
vm x86_64
i try now this: on 'host B' where vm runs, compile "generic_x86_64"
kernel reboot and recompile complete system with no CPU_FLAGS
and will see if 'vm' runs on 'host A'
marko
Am 2017-08-25 14:26, schrieb Marcos:
Well, linux is easier then wind
Hello,
I have virtual machines running with a ceph storage backend.
When creating an external qcow2 snapshot with a libvirt version without
support for the new object secret passing, the backing file info would
list the ceph secret in plain,e.g.
# virsh snapshot-create-as vm-123 --no-metadata --
Well, linux is easier then windows.The host A is 64 or 32 bits ?The host B is 64 or 32 bits ?The VM is 64 or 32 ?64 bits VM does not runs on 32 bits host___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvir
Hi Macros,
Am 2017-08-25 11:54, schrieb Marcos:
Hi everyone,
Windows are very sensitive with hardware, mainly with CPU.
If you change, you break.
It is not the virtualization system fault.
For libvirt/kvm you can use the CPU kvm64 that hidde some specifics
features from the operational syst
Hi Martin,
Thanks for your answer!
> We cannot guarantee that some events will not fire multiple times as is some
> cases there is no way to check whether it is duplicate or not when libvirt
> gets the information. I have a hunch that the fact that events can happen
> multiple times is written
Hi everyone,Windows are very sensitive with hardware, mainly with CPU.If you change, you break.It is not the virtualization system fault.For libvirt/kvm you can use the CPU kvm64 that hidde some specifics features from the operational system.In this case it is easier to migrate VM from host to host
On Thu, Aug 24, 2017 at 12:54:26PM +, Naud, AntoineX wrote:
Hello,
I am using domain event notifications from libvirt-event API in my application
and it seems to work fine, except for 'suspend' and 'resume' events where I
keep receiving duplicated notifications.
Similarly, the example pro
hey dominik,
Am 2017-08-24 18:14, schrieb Dominik Psenner:
This might be related to the configuration of the virtual machine. A
machine configured to have cpu X might not start up when it is changed
to cpu Y. We also observed that a windows host does not boot on a
ubuntu host with the default k