Search results

We use the same kernel and no issues with Windows machines. Have you tried disabling virtio?

> Still, this type of failure shouldn't be happening. How do people run VMs on lesser hardware? Isn't it possible to do on a software RAID-1 with just two regular HDs? Software RAID is not recommended and I think those who use it configure their VMs for writeback. Otherwise performance would...

Considering provided information I would recommend: 1) disabling balooning 2) switching from virtio (as I suggested before) More questions: 1) amount of RAM on the host 2) number of VMs on the host However the most probable cause I can think about so far is write i/o performance on the host...

Please provide more information here: 1. What physical servers are used and it's configuration? 2. RAID hardware and configuration? 3. May be network configuration if it is somehow special (not IP addresses but architecture) 4. What about backups? What kind of storage is used and when scheduled...

This is weird, I know. And this came from kvm/qemu.

> Okay, but https://pve.proxmox.com/wiki/Performance_Tweaks says to "Avoid to use cache=directsync and writethrough with qcow2 files." but it doesn't say why. Because this disables write cache completely. However hardware RAID with BBU usually ignores such requests and report data being...

It doesn't seem to be the cause for your problem however with out-of-sync blocks you can't rely on HA and can get data corrupted.

Just one. It compares checksums for blocks between nodes.

I recommend trying drbdadm verify before doing anything else.

Pegasus, you say DRBD and at the same time qcow2. I probably misunderstand your configuration. I was talking about LVM on top of DRBD but it seems your configuration is different. Provide more information.

Yes, it is not a good idea. Read more in the Proxmox wiki. Right, I have done some tests before moving with ballooning to production and found that bad idea. No ballooning anymore ever :) I suggest not migrating between DRBD hosts before changing cache mode and checking DRBD consistency...

If you use DRBD you must use either write-through or direct-sync mode for a KVM drive. Be careful with Baloon. When you set for example 1024/4096 this doesn't mean that the VM can take 2048 if needed, this means that other machines can take all but 1024 from this machine and this machine will...

1.x -> 2.x was a major change in architecture/components/interface 2.x -> 3.x was just a Debian distribution upgrade from squeeze to wheezy, so documentation must be valid in most cases

BTW, you join a system to cluster by IP so you can try to configure this IP to another interface and see what happens.

I have suggested changing a web-interface NIC and not cluster NIC.

When you assign an IP to any of NICs then web-interface will be accessible on this IP.

You can just use another network interface for web-management (different from vmbr0), so vmbr0 will only be used for migration.

Is the eBook DRM-protected?

One more. Not related to backup but non-uniq IDs: https://bugzilla.proxmox.com/show_bug.cgi?id=526

Another topic: http://forum.proxmox.com/threads/7603-Where-did-the-names-of-the-VMs-go