sf...@users.sourceforge.net: > sf...@users.sourceforge.net: >> Thanx for the interesting bug report. >> Although I could not reproduce the bug, I'm afraid it is an aufs >> problem. I will try more and investigate it, but it may take some time.
> On the report, I can see that you use aufs in qemu. > Would you kindly tell me how you invoked it? I mean the exact command > line. Sure. Here's the command line libvirt generated: qemu-system-x86_64 -enable-kvm -name guest=sid-desktop,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-18-sid-desktop/master-key.aes -machine pc-i440fx-2.3,accel=kvm,usb=off,dump-guest-core=off -cpu Haswell-noTSX,vme=on,ss=on,vmx=on,f16c=on,rdrand=on,hypervisor=on,arat=on,tsc_adjust=on,xsaveopt=on,pdpe1gb=on,abm=on -m 2048 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 213ff882-ce4b-035d-e2b1-9059d66cd67d -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-18-sid-desktop/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot menu=off,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device ahci,id=sata0,bus=pci.0,addr=0x5 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -device usb-hub,id=hub0,bus=usb.0,port=1 -drive if=none,id=drive-ide0-1-0,readonly=on -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/var/lib/libvirt/images/sid-desktop.img,format=qcow2,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=26,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:05:17:47,bus=pci.0,addr=0x3 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device virtio-tablet-pci,id=input0,bus=pci.0,addr=0x9 -device virtio-keyboard-pci,id=input2,bus=pci.0,addr=0xa -spice port=5947,addr=127.0.0.1,disable-ticketing,seamless-migration=on -device virtio-vga,id=video0,max_outputs=1,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=1.1 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=1.2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on Note that this bug happens on bare metal too e.g. with https://mirrors.wikimedia.org/tails/stable/tails-amd64-3.5/tails-amd64-3.5.iso > Because I cannot reproduce the problem on my test machine, intel > core2duo (I know this is old machine). Do you have more cpu cores? Do > you think that more and more cores get more chances to reproduce? I've just retried with different numbers of vCPUs allocated to the VM and CONFIG_AUFS_DEBUG enabled. I could reproduce the bug with 1 vCPU, 2 vCPUs, and with my original settings (4 vCPUs). Cheers, -- intrigeri
