Hello, In our RHEV 2.2 environment, after upgrading hosts from rhev-h 5.7 (2.6.18-274.17.1) to rhev-h 5.8 (2.6.18-308), we have some guests go into a hung state after a few hours — this includes RHEL 5.x, 6.x and even Windows guests. They are also using virtio disk and network drivers. I wonder if it's related. We opened a case on it, # 00609043.
Best, Daniel ************ Dear all, since yesterday's update we're seeing stability problems with a kvm guest. The guest crashes after 4 to 8 hours of running. It is a Web/DNS/Postfix server without much disk i/o. Sys: Host + Guest RHEL5.8 x86_64 The guest is running with these options; virtio for disk and nic: /usr/libexec/qemu-kvm -m 1024 -boot c -k de \ -daemonize \ -drive file=/dev/sdc1,if=virtio,index=0,boot=on \ -drive file=/dev/mapper/VG00- LVvm2swap,if=virtio,index=1 \ -net nic,vlan=0,macaddr=xxx,model=virtio \ -net nic,vlan=1,macaddr=xxx,model=virtio \ Sadly I only have the vnc console output of the guest; we're getting tasks blocked for 120s in httpd and postfix and obviously complete ceasing of disk io. The kvm host does not show problems in kernel log. Anybody seeing the same problems? With very limited testing it seems: host / guest 2.6.18-308 / 2.6.18-308 crash 2.6.18-308 / 2.6.18-274.18.1 crash 2.6.18-274.18.1 / 2.6.18-308 stable Rainer
_______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list
