On Mon, Aug 14, 2017 at 2:24 AM, ChristianEhrhardt <1710...@bugs.launchpad.net> wrote: > Ok, thanks for calrification good to know this is in your hands. > > About: > [*] Note: you currently need to boot the Ubuntu kernel w/ apparmor=0 to work > with latest upstream QEMU > > I haven't seen anything like that when testing 2.10-rc1/rc2 - is that arm > specific (apparmor usually prefers to fail everywhere the same way)? > Maybe it depends on the host kernel as most of my tests use Xenial-Kernel + > LXD<newrelease>. > Since soon there will be a 2.10 based upload to artful please let me know if > there is a bug or details about this somewhere else.
It doesn't *look* to be arch-specific, but I haven't tested others. It may just be the way my test works. Starting at: 244a56681 file-posix: Add image locking to perm operations My test case (attached to this bug) began to fail with: error: Failed to start domain 7936-0 error: internal error: process exited while connecting to monitor: 2017-08-14T23:43:10.255604Z qemu-system-aarch64: -drive file=/home/ubuntu/vm-start-stop/vms/7936-0_CODE.fd,if=pflash,format=raw,unit=0,readonly=on: Failed to unlock byte 100 2017-08-14T23:43:10.255750Z qemu-system-aarch64: -drive file=/home/ubuntu/vm-start-stop/vms/7936-0_CODE.fd,if=pflash,format=raw,unit=0,readonly=on: Failed to unlock byte 100 2017-08-14T23:43:10.255936Z qemu-system-aarch64: -drive file=/home/ubuntu/vm-start-stop/vms/7936-0_CODE.fd,if=pflash,format=raw,unit=0,readonly=on: Failed to lock byte 100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710019 Title: support GICv3 ITS save/restore & migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1710019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
