Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Sep 2012 18:38:23 +0200 (CEST)
From:      Przemyslaw Frasunek <venglin@freebsd.lublin.pl>
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   ports/172183: Severe filesystem corruption when running as KVM guest with VirtIO enabled
Message-ID:  <20120930163823.5AEDA47A381@lagoon.freebsd.lublin.pl>
Resent-Message-ID: <201209301640.q8UGe10Z099313@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         172183
>Category:       ports
>Synopsis:       Severe filesystem corruption when running as KVM guest with VirtIO enabled
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Sep 30 16:40:00 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator:     Przemyslaw Frasunek
>Release:        FreeBSD 9.0-RELEASE i386
>Organization:
nette.pl
>Environment:

	FreeBSD 9.0-RELEASE running as KVM guest on Ubuntu 12.04 LTS host.

	virtio-kmod compiled from ports on 26 Sep 2012.

	Libvirt XML domain file on host:

<domain type='kvm'>
  <name>lagoon-9.0</name>
  <uuid>74b2fef0-bd43-11e1-9876-002219d6b4d6</uuid>
  <memory>2097152</memory>
  <currentMemory>2097152</currentMemory>
  <vcpu>1</vcpu>
  <os>
    <type arch='x86_64' machine='pc-0.11'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/kvm</emulator>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source dev='/dev/mapper/vm-vm_lagoon--root'/>
      <target dev='vda' bus='virtio'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source dev='/dev/mapper/vm-vm_lagoon--home'/>
      <target dev='vdb' bus='virtio'/>
    </disk>
    <controller type='scsi' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </controller>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <interface type='bridge'>
      <mac address='54:52:00:2a:c5:6b'/>
      <source bridge='br0'/>
      <model type='virtio'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
    <video>
      <model type='cirrus' vram='9216' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </memballoon>
  </devices>
</domain>

>Description:
	The VM was running stable for about three months with
	emulated IDE block device. Few hours after migrating to VirtIO,
	first panic occured:

	ufs_dirbad: /home: bad dir ino 12294148 at offset 147456: mangled entry

	After reboot & fsck, multiple other inodes were corrupted and
	panic occurred every few minutes. After restoring VM image from
	backup and switching back to emulated IDE, problem was resolved.
	
>How-To-Repeat:
	Unknown.
>Fix:
	Unknown.


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120930163823.5AEDA47A381>