Long lasting bug and huge update, but I think I got the root cause.
FYI, Windows 2003 is having a write cache enabled by default on disk
drivers. Even with virtio (see driver details, policies).
As a consequence, any DLL which is open could be corrupted if we try a
simple 'qemu-img convert'
On 12/03/13 09:48, Sylvain Bauza wrote:
Long lasting bug and huge update, but I think I got the root cause.
FYI, Windows 2003 is having a write cache enabled by default on disk
drivers. Even with virtio (see driver details, policies).
Hi there,
That option did you use in driver policy?
On Wed, Feb 13, 2013 at 10:53:14AM +0100, Sylvain Bauza wrote:
As per documentation, Nova (Openstack Compute layer) is doing a
'qemu-img convert -s' against a running instance.
http://docs.openstack.org/trunk/openstack-compute/admin/content/creating-images-from-running-instances.html
That
On Tue, Feb 12, 2013 at 03:30:37PM +0100, Sylvain Bauza wrote:
We currently run Openstack Essex hosts with KVM-1.0 (Ubuntu 12.04)
instances with qcow2,virtio,cache=none
For Linux VMs, no trouble at all but we do observe filesystem
corruption and inconsistency (missing DLLs, CHKDSK asked by
Hi,
Latest updates, I tried using :
- cache=writethrough / kvm-1.0 : errors in qcow2
- cache=none/kvm-1.3 : no errors using 'qemu-img check', but
EventViewer is complaining
I have to admit I'm lost. I cannot understand what is causing this
corruption, only appearing on some Windows
Interesting point you mention. Even if qcow2 is read only, the image is
changing (especially, I'm running IIS with ASP support and VB DLLs)
while the snapshot is taken.
As asked in a second post, I'm running with latest Windows virtio
drivers, but I only apply a virtio driver update *after*
Hello,
On Tuesday 12 February 2013 15:30:37 Sylvain Bauza wrote:
We currently run Openstack Essex hosts with KVM-1.0 (Ubuntu 12.04)
instances with qcow2,virtio,cache=none
The default answer is to update your qemu-kvm version: 1.0 is very old, qemu-
kvm is fully merged into upstream qemu, which
On Tue, Feb 12, 2013 at 03:30:37PM +0100, Sylvain Bauza wrote:
We currently run Openstack Essex hosts with KVM-1.0 (Ubuntu 12.04)
instances with qcow2,virtio,cache=none
For Linux VMs, no trouble at all but we do observe filesystem
corruption and inconsistency (missing DLLs, CHKDSK asked by
Hi Stefan,
As per documentation, Nova (Openstack Compute layer) is doing a
'qemu-img convert -s' against a running instance.
http://docs.openstack.org/trunk/openstack-compute/admin/content/creating-images-from-running-instances.html
Do you think it could be our root cause ?
Btw, I tested
Hi Philipp,
Indeed. Qemu-kvm.1.0 is pretty old but this version is the stable one
for Ubuntu Precise (12.04 LTS).
No backport is available for later versions, I need to install by hand.
Do you know if qemu-1.3 (with KVM support) is fully compatible with
qemu-kvm.1.0 ?
As I'm relying on
there are known problems, WHEN I/O native and cache=writethrough.
On I/O native put cache to none otherwise your data can get broken.
Check Redhat Pages for that.
marko
Am 2013-02-13 10:56, schrieb Sylvain Bauza:
Hi Philipp,
Indeed. Qemu-kvm.1.0 is pretty old but this version is the stable
[Please stop top-posting. Thank you]
13.02.2013 20:03, we...@zackbummfertig.de wrote:
there are known problems, WHEN I/O native and cache=writethrough.
On I/O native put cache to none otherwise your data can get broken.
Check Redhat Pages for that.
Which problem is that?
And what is
Hi,
We currently run Openstack Essex hosts with KVM-1.0 (Ubuntu 12.04)
instances with qcow2,virtio,cache=none
For Linux VMs, no trouble at all but we do observe filesystem corruption
and inconsistency (missing DLLs, CHKDSK asked by EventViewer, failure at
reboot) with some of our Windows
13 matches
Mail list logo
