search for: apbogdan

Hello, Is there a way to configure the domain cpu in such a way that the info reported to the guest OS system will remain constant ? For example in older versions of of libvirt/qemu the cpu was reported as "QEMU Virtual CPU version (cpu64_rhel6)" but moving the vm on a qemu2.2.0 is is reported as "QEMU Virtual CPU version 2.2.0". Thanks.

I want to create a virtual machine from scratch in ESX but I can't figure out how to create the disks - the vmdk files. Any hints on how that can be done or even if it's possible at all ? Thanks

2015-04-01 18:25 GMT+02:00 Paul Apostolescu <apbogdan@gmail.com>: > I want to create a virtual machine from scratch in ESX but I can't figure > out how to create the disks - the vmdk files. Any hints on how that can be > done or even if it's possible at all ? You can use the following virsh command: vol-create-as --pool ds --nam...

...;model fallback='allow'>core2duo</model> <vendor>Intel</vendor> <topology sockets='1' cores='2' threads='1'/> <feature policy='disable' name='lahf_lm'/> </cpu> ... On 2/5/15, Paul Apostolescu <apbogdan@gmail.com> wrote: > Hello, > > Is there a way to configure the domain cpu in such a way that the info > reported to the guest OS system will remain constant ? For example in older > versions of of libvirt/qemu the cpu was reported as "QEMU Virtual CPU > version (cpu64_rhel...

Is it possible to set the CPU frequency exposed to the guest operating system for a kvm-enabled virtual machine ? The documentation does not mention anything about it. Thanks.

Hello, I am running into issues restoring VMs during reboot for some of my XP VMs - the environment is QEMU 2.2.0, libvirt 1.2.12 on CentOS 6.5 with KVM and libvirt-guests is set to suspend at shutdown. The weird part is Windows 7 is restored properly from the managedsave however XP does not, doing a start from virsh shows this: virsh # start xp-check error: Failed to start domain xp-check