Search results

Hi, You can try MSI Cleanup Utility available here : http://www.labo-microsoft.org/d/d/?id=13200 I'm still unable to install the Qemu Agent in my VMs , grrrrrr .... Regards,

Just tested with latest virtio 0.1.112 , still the same problem ... Very strange.

Dear Wolfgang, Thank you for your answer. Yes the virtioserial dev was installed on all the virtual machines on which i try to install.... I forgot to mention that all the operations have been made with an admin account and UAC disabled. Regards, Thomas

Hi all, In order to have some consistent VMs backups using VSS Snapshots, we'd like to install the guest agent in our Windows VMs. We obtain an error message when executing qemu-ga-x64.msi : There is a problem with this Windows Installer package. A program run as part of the setup did not...

Okay thanks for the reply. This is problematic in a production environment because if qcow2 files grows over their designed size, this could fill the DATASTORE (like doing thin provisionning) ... Is there any plan to use qcow2 external snapshots ?

Hello everyboy, I'm playing with QCOW2 files / qm snapshot feature for our VMs and i've noticed that some QCOW2 files can became bigger than the VM HDD defined size. For example, VM 202 with a 60Gb QCOW2 HDD : qemu-img info /mnt/pve/nas20/images/202/vm-202-disk-1.qcow2 image...

Seems to be ok since i've made a second reboot of the VM after deleting / re-adding the network card and upgrading the virtio driver. So the process should be : 1 - Shutdown the VM and remove the network card from the VM configuration (or change the card type to e1000) 2 - Sart the vm and...

Some fresh news : I removed the network card, delete it from "hidden's hardware" in the windows hardware manager and readd it with drivers from latest virtio-0.1-65. Problem still occurs, grrrrr I've notice that some STP requests coming from the switch (Cisco Catalyst 2950) occurs...

@spirit and @naves Thank you guys for your suggestions. I'll make some tests tonight when the server will be idle, hope we're on the right way ... ;)

Yes, a SQL Server Std 2008 R2 with a 2gb limit assigned + a SQL Express for WSUS ...

Running a copy of the VM on a spare 3.1 host doesn't reproduce the problem. The only difference between production VM and test VM is the network card running in a vlan in order to isolate the copy vm from the production LAN / VM. So maybe it should be a network issue, like broadcasting or...

Thanks for your post. It's really strange because nothing have changed in the VM configuration, just switching between 2.3 and 3.1 made the VM to work or not ... I'm going to try some things with a copy of this VM, like changing CPU core / sockets number, cpu type, IDE like you suggest, ...

Hi all, Since we migrate our host from 2.3 to 3.1, one of our Windows 2003 32bits VM freezes randomly without BSOD. We noticed that there was some cpu usage peaks due to interrupts hardware there was not before under 2.3. A second W2K3 32bits VM is running on this host without any problems...

Found the problem : RTFM !!! I forget the last step in the migration guide : apt-get purge fuse-utils insserv Works right now !!! Sorry for inconvenience and thanks for your help. Regards, Thomas

Okay, i've done more tests : pvesh --nooutput create /nodes/localhost/stopall : the vm shutdown correctly with an ACPI shutdown sequence So i add a sleep 30 at the end of file /etc/init.d/pve-manager (just before the "exit 0") and reboot the host. I've got few lines saying...

Okay thank you for the test. It should be an upgrade issue ? I do the upgrade from 2.3 with the pve-upgrade-2.3-to-3.0 script dowloaded from the wiki, upgrade was succesfull. If i do a "qm shutdown 102", the VM shutdown occurs normally ... It looks like the host shutdown sequence "skip" the step...

Hello Tom, Thanks for the quick reply. I agree with you and this is the problem, when i initiate a reboot from gui (or from ssh), got only these entries in tasks logs after reboot : VM configuration : Start at boot = yes , order=any Regards, Thomas

Hi, Since we have migrate from 2.3 to 3.0 (on multiple hosts), when we run a "shutdown" on the host, all VM'S (KVM) are instantanely stopped instead of doing a clean shutdown (via ACPI / qm shutdown). Is it the expected behaviour ? Is it possible to change this or to cutomize the shutdown...

Will it be based on lvcreate / lvconvert commands ?

Ok ... If this works and you want to keep this setting at next reboot , put this in your /etc/modprobe.d/local : options kvm ignore_msrs=1 Thomas