May 10 01:16:39 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: *** Including module: virtiofs *** May 10 01:16:48 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: virtiofs May 10 01:16:50 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: -rwxr-xr-x 1 root root 208 Jun 19 2022 usr/lib/dracut/hooks/cmdline/95-parse-virtiofs.sh May 10 01:16:50 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: -rwxr-xr-x 1 root root 637 Jun 19 2022 usr/lib/dracut/hooks/pre-mount/99-mount-virtiofs.sh May 10 01:16:53 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: -rw-r--r-- 1 root root 12964 Jan 4 01:56 usr/lib/modules/5.14.0-427.16.1.el9_4.aarch64/kernel/drivers/block/virtio_blk.ko.xz May 10 01:16:53 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: -rw-r--r-- 1 root root 14760 Jan 4 01:56 usr/lib/modules/5.14.0-427.16.1.el9_4.aarch64/kernel/drivers/char/virtio_console.ko.xz May 10 01:16:53 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: -rw-r--r-- 1 root root 3744 Jan 4 01:56 usr/lib/modules/5.14.0-427.16.1.el9_4.aarch64/kernel/drivers/dma/virt-dma.ko.xz May 10 01:16:53 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: -rw-r--r-- 1 root root 6472 Jan 4 01:56 usr/lib/modules/5.14.0-427.16.1.el9_4.aarch64/kernel/drivers/gpio/gpio-virtio.ko.xz May 10 01:16:53 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: -rw-r--r-- 1 root root 4024 Jan 4 01:56 usr/lib/modules/5.14.0-427.16.1.el9_4.aarch64/kernel/drivers/i2c/busses/i2c-virtio.ko.xz May 10 01:16:54 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: -rw-r--r-- 1 root root 31252 Jan 4 01:56 usr/lib/modules/5.14.0-427.16.1.el9_4.aarch64/kernel/drivers/net/virtio_net.ko.xz May 10 01:16:54 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: -rw-r--r-- 1 root root 9152 Jan 4 01:56 usr/lib/modules/5.14.0-427.16.1.el9_4.aarch64/kernel/drivers/scsi/virtio_scsi.ko.xz May 10 01:16:55 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: drwxr-xr-x 2 root root 0 Jan 4 01:56 usr/lib/modules/5.14.0-427.16.1.el9_4.aarch64/kernel/drivers/virtio May 10 01:16:55 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: -rw-r--r-- 1 root root 16192 Jan 4 01:56 usr/lib/modules/5.14.0-427.16.1.el9_4.aarch64/kernel/drivers/virtio/virtio_mem.ko.xz May 10 01:16:55 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: -rw-r--r-- 1 root root 6056 Jan 4 01:56 usr/lib/modules/5.14.0-427.16.1.el9_4.aarch64/kernel/drivers/virtio/virtio_mmio.ko.xz May 10 01:16:55 i-0d789f7fe1298cec4.us-west-2.compute.internal dracut[23600]: -rw-r--r-- 1 root root 14840 Jan 4 01:56 usr/lib/modules/5.14.0-427.16.1.el9_4.aarch64/kernel/fs/fuse/virtiofs.ko.xz May 10 01:19:28 i-0d789f7fe1298cec4.us-west-2.compute.internal setsebool[43467]: The virt_use_nfs policy boolean was changed to 1 by root May 10 01:19:28 i-0d789f7fe1298cec4.us-west-2.compute.internal setsebool[43467]: The virt_sandbox_use_all_caps policy boolean was changed to 1 by root May 10 01:30:18 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[166763]: ec2-user : PWD=/home/ec2-user/microshift ; USER=root ; COMMAND=/bin/dnf install -y libvirt virt-manager virt-install virt-viewer libvirt-client qemu-kvm qemu-img sshpass May 10 01:31:42 i-0d789f7fe1298cec4.us-west-2.compute.internal groupadd[167288]: group added to /etc/group: name=libvirt, GID=982 May 10 01:31:42 i-0d789f7fe1298cec4.us-west-2.compute.internal groupadd[167288]: group added to /etc/gshadow: name=libvirt May 10 01:31:42 i-0d789f7fe1298cec4.us-west-2.compute.internal groupadd[167288]: new group: name=libvirt, GID=982 May 10 01:32:05 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[172622]: ec2-user : PWD=/home/ec2-user/microshift ; USER=root ; COMMAND=/bin/systemctl enable --now libvirtd May 10 01:32:06 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: Listening on libvirt legacy monolithic daemon socket. May 10 01:32:06 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: Listening on libvirt legacy monolithic daemon admin socket. May 10 01:32:06 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: Listening on libvirt legacy monolithic daemon read-only socket. May 10 01:32:06 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: Listening on libvirt locking daemon socket. May 10 01:32:06 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: Listening on libvirt logging daemon socket. May 10 01:32:06 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: Starting libvirt legacy monolithic daemon... May 10 01:32:06 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: Started libvirt legacy monolithic daemon. May 10 01:32:06 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[172684]: ec2-user : PWD=/home/ec2-user/microshift ; USER=root ; COMMAND=/sbin/usermod -a -G libvirt ec2-user May 10 01:32:06 i-0d789f7fe1298cec4.us-west-2.compute.internal usermod[172689]: add 'ec2-user' to group 'libvirt' May 10 01:32:06 i-0d789f7fe1298cec4.us-west-2.compute.internal usermod[172689]: add 'ec2-user' to shadow group 'libvirt' May 10 01:32:06 i-0d789f7fe1298cec4.us-west-2.compute.internal dnsmasq[172874]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses May 10 01:32:06 i-0d789f7fe1298cec4.us-west-2.compute.internal dnsmasq-dhcp[172874]: read /var/lib/libvirt/dnsmasq/default.hostsfile May 10 01:32:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[172660]: libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:32:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[172660]: hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:32:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[172660]: operation failed: failed to read the PCI VPD data: missing read-only section May 10 01:32:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[172660]: operation failed: failed to read the PCI VPD data: missing read-only section May 10 01:32:24 i-0d789f7fe1298cec4.us-west-2.compute.internal dnsmasq[173428]: read /var/lib/libvirt/dnsmasq/isolated.addnhosts - 0 addresses May 10 01:32:24 i-0d789f7fe1298cec4.us-west-2.compute.internal dnsmasq-dhcp[173428]: read /var/lib/libvirt/dnsmasq/isolated.hostsfile May 10 01:32:25 i-0d789f7fe1298cec4.us-west-2.compute.internal dnsmasq[173510]: read /var/lib/libvirt/dnsmasq/multus.addnhosts - 0 addresses May 10 01:32:25 i-0d789f7fe1298cec4.us-west-2.compute.internal dnsmasq-dhcp[173510]: read /var/lib/libvirt/dnsmasq/multus.hostsfile May 10 01:32:25 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[173522]: ec2-user : PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/firewall-cmd --permanent --zone=libvirt --add-service=mdns May 10 01:34:41 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: libvirtd.service: Deactivated successfully. May 10 01:34:41 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: libvirtd.service: Unit process 172874 (dnsmasq) remains running after unit stopped. May 10 01:34:41 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: libvirtd.service: Unit process 172875 (dnsmasq) remains running after unit stopped. May 10 01:34:41 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: libvirtd.service: Unit process 173428 (dnsmasq) remains running after unit stopped. May 10 01:34:41 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: libvirtd.service: Unit process 173429 (dnsmasq) remains running after unit stopped. May 10 01:34:41 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: libvirtd.service: Unit process 173510 (dnsmasq) remains running after unit stopped. May 10 01:34:41 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: libvirtd.service: Unit process 173511 (dnsmasq) remains running after unit stopped. May 10 01:34:41 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: libvirtd.service: Consumed 1.674s CPU time. May 10 01:35:57 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: Starting libvirt legacy monolithic daemon... May 10 01:35:57 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: Started libvirt legacy monolithic daemon. May 10 01:36:01 i-0d789f7fe1298cec4.us-west-2.compute.internal dnsmasq[173510]: read /var/lib/libvirt/dnsmasq/multus.addnhosts - 0 addresses May 10 01:36:01 i-0d789f7fe1298cec4.us-west-2.compute.internal dnsmasq[173428]: read /var/lib/libvirt/dnsmasq/isolated.addnhosts - 0 addresses May 10 01:36:01 i-0d789f7fe1298cec4.us-west-2.compute.internal dnsmasq[172874]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses May 10 01:36:01 i-0d789f7fe1298cec4.us-west-2.compute.internal dnsmasq-dhcp[173510]: read /var/lib/libvirt/dnsmasq/multus.hostsfile May 10 01:36:01 i-0d789f7fe1298cec4.us-west-2.compute.internal dnsmasq-dhcp[172874]: read /var/lib/libvirt/dnsmasq/default.hostsfile May 10 01:36:01 i-0d789f7fe1298cec4.us-west-2.compute.internal dnsmasq-dhcp[173428]: read /var/lib/libvirt/dnsmasq/isolated.hostsfile May 10 01:36:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:36:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:36:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: operation failed: failed to read the PCI VPD data: missing read-only section May 10 01:36:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: operation failed: failed to read the PCI VPD data: missing read-only section May 10 01:36:03 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[180754]: ec2-user : TTY=pts/0 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name cos9-src-backup-and-restore-on-reboot-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-cos9-src@backup-and-restore-on-reboot,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/centos9-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.8tLNAWfS.ks' --initrd-inject /tmp/kickstart.8tLNAWfS.ks --initrd-inject /tmp/kickstart-includes.tzaVKa0v/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.tzaVKa0v/main-liveimg.cfg May 10 01:36:04 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[181638]: ec2-user : TTY=pts/1 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name cos9-src-backups-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-cos9-src@backups,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/centos9-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.9hC6payV.ks' --initrd-inject /tmp/kickstart.9hC6payV.ks --initrd-inject /tmp/kickstart-includes.TfOhlqLu/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.TfOhlqLu/main-liveimg.cfg --initrd-inject May 10 01:36:05 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: Listening on libvirt logging daemon admin socket. May 10 01:36:05 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: Starting libvirt logging daemon... May 10 01:36:05 i-0d789f7fe1298cec4.us-west-2.compute.internal systemd[1]: Started libvirt logging daemon. May 10 01:36:09 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[183092]: ec2-user : TTY=pts/4 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name cos9-src-greenboot-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-cos9-src@greenboot,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/centos9-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.qB6Ch9Zw.ks' --initrd-inject /tmp/kickstart.qB6Ch9Zw.ks --initrd-inject /tmp/kickstart-includes.r7asrt6Z/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.r7asrt6Z/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:36:14 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[184448]: ec2-user : TTY=pts/6 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name cos9-src-log-scan-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-cos9-src@log-scan,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/centos9-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.ieb7HmR4.ks' --initrd-inject /tmp/kickstart.ieb7HmR4.ks --initrd-inject /tmp/kickstart-includes.kccRAvmr/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.kccRAvmr/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:36:19 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[185801]: ec2-user : TTY=pts/8 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name cos9-src-multi-nic-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-cos9-src@multi-nic,size=20 --network network=default,model=virtio --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/centos9-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.8sHPR1Cf.ks' --initrd-inject /tmp/kickstart.8sHPR1Cf.ks --initrd-inject /tmp/kickstart-includes.UqddtmBI/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.UqddtmBI/main-liveimg.cfg If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:36:24 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[187223]: ec2-user : TTY=pts/10 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name cos9-src-optional-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-cos9-src@optional,size=20 --network network=multus,model=virtio --network network=multus,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/centos9-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.gel6IUQp.ks' --initrd-inject /tmp/kickstart.gel6IUQp.ks --initrd-inject /tmp/kickstart-includes.0l7kKJt1/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.0l7kKJt1/main-liveimg.cfg If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:36:29 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[188600]: ec2-user : TTY=pts/12 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name cos9-src-osconfig-cleanup-data-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-cos9-src@osconfig-cleanup-data,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/centos9-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.yBi53D2m.ks' --initrd-inject /tmp/kickstart.yBi53D2m.ks --initrd-inject /tmp/kickstart-includes.45xcfsaq/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.45xcfsaq/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:36:34 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[189957]: ec2-user : TTY=pts/14 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name cos9-src-osconfig-lifecycle-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-cos9-src@osconfig-lifecycle,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/centos9-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.pBM5m7Uy.ks' --initrd-inject /tmp/kickstart.pBM5m7Uy.ks --initrd-inject /tmp/kickstart-includes.cHyyUENW/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.cHyyUENW/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:36:39 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[191316]: ec2-user : TTY=pts/16 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name cos9-src-osconfig-misc-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-cos9-src@osconfig-misc,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/centos9-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.86D2GtuS.ks' --initrd-inject /tmp/kickstart.86D2GtuS.ks --initrd-inject /tmp/kickstart-includes.Dw7wFl0V/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.Dw7wFl0V/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:36:44 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[192679]: ec2-user : TTY=pts/18 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name cos9-src-standard-suite2-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-cos9-src@standard-suite2,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/centos9-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.NBVeL3o0.ks' --initrd-inject /tmp/kickstart.NBVeL3o0.ks --initrd-inject /tmp/kickstart-includes.uagGBzLu/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.uagGBzLu/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:36:49 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[194060]: ec2-user : TTY=pts/20 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name cos9-src-storage-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-cos9-src@storage,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/centos9-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.DaBeH1Ma.ks' --initrd-inject /tmp/kickstart.DaBeH1Ma.ks --initrd-inject /tmp/kickstart-includes.0xyYRiXr/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.0xyYRiXr/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:36:54 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[195511]: ec2-user : TTY=pts/22 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name el94-src-backup-and-restore-on-reboot-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-el94-src@backup-and-restore-on-reboot,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/rhel94-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.CjJF9eje.ks' --initrd-inject /tmp/kickstart.CjJF9eje.ks --initrd-inject /tmp/kickstart-includes.ZJnm8AK0/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.ZJnm8AK0/main-liveimg.cfg If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:36:59 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[196961]: ec2-user : TTY=pts/24 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name el94-src-backups-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-el94-src@backups,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/rhel94-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.Moe5Oswr.ks' --initrd-inject /tmp/kickstart.Moe5Oswr.ks --initrd-inject /tmp/kickstart-includes.MHbKqKx3/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.MHbKqKx3/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:37:04 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[198327]: ec2-user : TTY=pts/26 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name el94-src-greenboot-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-el94-src@greenboot,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/rhel94-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.8ZeKPeDQ.ks' --initrd-inject /tmp/kickstart.8ZeKPeDQ.ks --initrd-inject /tmp/kickstart-includes.3YukqmhK/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.3YukqmhK/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:37:09 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[199718]: ec2-user : TTY=pts/28 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name el94-src-log-scan-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-el94-src@log-scan,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/rhel94-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.QjDQHVv9.ks' --initrd-inject /tmp/kickstart.QjDQHVv9.ks --initrd-inject /tmp/kickstart-includes.PPJiwutB/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.PPJiwutB/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:37:14 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[201174]: ec2-user : TTY=pts/30 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name el94-src-multi-nic-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-el94-src@multi-nic,size=20 --network network=default,model=virtio --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/rhel94-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.4iwY5Z2V.ks' --initrd-inject /tmp/kickstart.4iwY5Z2V.ks --initrd-inject /tmp/kickstart-includes.7W5tX9Lq/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.7W5tX9Lq/main-liveimg.cfg If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:37:20 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[202652]: ec2-user : TTY=pts/32 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name el94-src-optional-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-el94-src@optional,size=20 --network network=multus,model=virtio --network network=multus,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/rhel94-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.xq7lkd4T.ks' --initrd-inject /tmp/kickstart.xq7lkd4T.ks --initrd-inject /tmp/kickstart-includes.vjbbHKNE/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.vjbbHKNE/main-liveimg.cfg If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:37:24 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[204041]: ec2-user : TTY=pts/34 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name el94-src-osconfig-cleanup-data-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-el94-src@osconfig-cleanup-data,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/rhel94-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.47RcOrRy.ks' --initrd-inject /tmp/kickstart.47RcOrRy.ks --initrd-inject /tmp/kickstart-includes.TbqCBKCT/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.TbqCBKCT/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:37:30 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[205476]: ec2-user : TTY=pts/36 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name el94-src-osconfig-lifecycle-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-el94-src@osconfig-lifecycle,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/rhel94-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.USTiHtpo.ks' --initrd-inject /tmp/kickstart.USTiHtpo.ks --initrd-inject /tmp/kickstart-includes.vcddmrIC/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.vcddmrIC/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:37:35 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[206881]: ec2-user : TTY=pts/38 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name el94-src-osconfig-misc-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-el94-src@osconfig-misc,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/rhel94-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.BvZP1QYw.ks' --initrd-inject /tmp/kickstart.BvZP1QYw.ks --initrd-inject /tmp/kickstart-includes.zQyDsb3N/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.zQyDsb3N/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:37:39 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[208277]: ec2-user : TTY=pts/40 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name el94-src-standard-suite2-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-el94-src@standard-suite2,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/rhel94-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.9XTpL5Ck.ks' --initrd-inject /tmp/kickstart.9XTpL5Ck.ks --initrd-inject /tmp/kickstart-includes.wRkxKNnc/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.wRkxKNnc/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:37:45 i-0d789f7fe1298cec4.us-west-2.compute.internal sudo[209677]: ec2-user : TTY=pts/42 ; PWD=/home/ec2-user/microshift/test ; USER=root ; COMMAND=/bin/virt-install --autoconsole text --graphics none --name el94-src-storage-host1 --vcpus 2 --memory 4096 --disk pool=vm-storage-el94-src@storage,size=20 --network network=default,model=virtio --events on_reboot=restart --noreboot --location /home/ec2-user/microshift/_output/test-images/vm-storage/rhel94-bootc.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img --osinfo detect=on --filesystem=/home/ec2-user/microshift/_output/test-images/bootc-images,bootc-images,driver.type=virtiofs --memorybacking=source.type=memfd,access.mode=shared --extra-args 'fips=0 console=ttyAMA0,115200n8 inst.notmux inst.ks=file:/kickstart.pLsm3PGd.ks' --initrd-inject /tmp/kickstart.pLsm3PGd.ks --initrd-inject /tmp/kickstart-includes.hlmrRbeU/main-cdrom.cfg --initrd-inject /tmp/kickstart-includes.hlmrRbeU/main-liveimg.cfg --initrd-inject If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:38:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Failed to terminate process 182059 with SIGKILL: Device or resource busy May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-vrvbvcs8-vmlinuz: No such file or directory May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-4yhnj4mu-initrd.img: No such file or directory May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[210700]: 2024-05-10 01:39:01.504+0000: 210700: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[210700]: 2024-05-10 01:39:01.504+0000: 210700: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[210700]: 2024-05-10 01:39:01.504+0000: 210700: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/cos9-src-backup-and-restore-on-reboot-host1_VARS.qcow2 May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[210700]: 2024-05-10 01:39:01.504+0000: 210700: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-cos9-src@backup-and-restore-on-reboot/cos9-src-backup-and-restore-on-reboot-host1.qcow2 May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-vrvbvcs8-vmlinuz: No such file or directory May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-vrvbvcs8-vmlinuz: No such file or directory May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-hsjqat4n-vmlinuz: No such file or directory May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-zmt9at80-initrd.img: No such file or directory May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[210709]: 2024-05-10 01:39:01.543+0000: 210709: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[210709]: 2024-05-10 01:39:01.543+0000: 210709: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[210709]: 2024-05-10 01:39:01.543+0000: 210709: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/cos9-src-greenboot-host1_VARS.qcow2 May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[210709]: 2024-05-10 01:39:01.543+0000: 210709: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-cos9-src@greenboot/cos9-src-greenboot-host1.qcow2 May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-hsjqat4n-vmlinuz: No such file or directory May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-hsjqat4n-vmlinuz: No such file or directory May 10 01:39:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:39:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-_pxdkhzy-vmlinuz: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-700yyc_1-initrd.img: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211210]: 2024-05-10 01:39:08.730+0000: 211210: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211210]: 2024-05-10 01:39:08.730+0000: 211210: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211210]: 2024-05-10 01:39:08.730+0000: 211210: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/cos9-src-osconfig-cleanup-data-host1_VARS.qcow2 May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211210]: 2024-05-10 01:39:08.731+0000: 211210: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-cos9-src@osconfig-cleanup-data/cos9-src-osconfig-cleanup-data-host1.qcow2 May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-_pxdkhzy-vmlinuz: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211219]: 2024-05-10 01:39:08.766+0000: 211219: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211219]: 2024-05-10 01:39:08.766+0000: 211219: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211219]: 2024-05-10 01:39:08.766+0000: 211219: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/cos9-src-log-scan-host1_VARS.qcow2 May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211219]: 2024-05-10 01:39:08.766+0000: 211219: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-cos9-src@log-scan/cos9-src-log-scan-host1.qcow2 May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-_pxdkhzy-vmlinuz: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211239]: 2024-05-10 01:39:08.800+0000: 211239: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211239]: 2024-05-10 01:39:08.800+0000: 211239: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211239]: 2024-05-10 01:39:08.800+0000: 211239: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/cos9-src-multi-nic-host1_VARS.qcow2 May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211239]: 2024-05-10 01:39:08.800+0000: 211239: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-cos9-src@multi-nic/cos9-src-multi-nic-host1.qcow2 May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211259]: 2024-05-10 01:39:08.836+0000: 211259: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211259]: 2024-05-10 01:39:08.836+0000: 211259: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211259]: 2024-05-10 01:39:08.836+0000: 211259: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/cos9-src-optional-host1_VARS.qcow2 May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[211259]: 2024-05-10 01:39:08.836+0000: 211259: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-cos9-src@optional/cos9-src-optional-host1.qcow2 May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-a1xdz_iy-vmlinuz: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-trq1vglr-initrd.img: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-a1xdz_iy-vmlinuz: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-a1xdz_iy-vmlinuz: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-9p4muisf-vmlinuz: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-jvho69iq-initrd.img: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-9p4muisf-vmlinuz: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-9p4muisf-vmlinuz: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-xcy0bhjb-vmlinuz: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-yy_ha5g9-initrd.img: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-xcy0bhjb-vmlinuz: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-xcy0bhjb-vmlinuz: No such file or directory May 10 01:39:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:39:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-yyk4xmb3-vmlinuz: No such file or directory May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-93pktp46-initrd.img: No such file or directory May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212184]: 2024-05-10 01:39:10.848+0000: 212184: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212184]: 2024-05-10 01:39:10.848+0000: 212184: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212184]: 2024-05-10 01:39:10.848+0000: 212184: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/cos9-src-osconfig-lifecycle-host1_VARS.qcow2 May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212184]: 2024-05-10 01:39:10.849+0000: 212184: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-cos9-src@osconfig-lifecycle/cos9-src-osconfig-lifecycle-host1.qcow2 May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-yyk4xmb3-vmlinuz: No such file or directory May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-yyk4xmb3-vmlinuz: No such file or directory May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-rf2c63db-vmlinuz: No such file or directory May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-_7vv1pyx-initrd.img: No such file or directory May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212192]: 2024-05-10 01:39:10.883+0000: 212192: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212192]: 2024-05-10 01:39:10.883+0000: 212192: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212192]: 2024-05-10 01:39:10.883+0000: 212192: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/cos9-src-standard-suite2-host1_VARS.qcow2 May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212192]: 2024-05-10 01:39:10.883+0000: 212192: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-cos9-src@standard-suite2/cos9-src-standard-suite2-host1.qcow2 May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-rf2c63db-vmlinuz: No such file or directory May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-rf2c63db-vmlinuz: No such file or directory May 10 01:39:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:39:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-esfgri2r-vmlinuz: No such file or directory May 10 01:39:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-7psujuu0-initrd.img: No such file or directory If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:39:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212235]: 2024-05-10 01:39:11.119+0000: 212235: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:39:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212235]: 2024-05-10 01:39:11.119+0000: 212235: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:39:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212235]: 2024-05-10 01:39:11.119+0000: 212235: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/cos9-src-osconfig-misc-host1_VARS.qcow2 May 10 01:39:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212235]: 2024-05-10 01:39:11.119+0000: 212235: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-cos9-src@osconfig-misc/cos9-src-osconfig-misc-host1.qcow2 May 10 01:39:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-esfgri2r-vmlinuz: No such file or directory May 10 01:39:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-esfgri2r-vmlinuz: No such file or directory May 10 01:39:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:39:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:39:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-xyibqaok-vmlinuz: No such file or directory May 10 01:39:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-xijjiuji-initrd.img: No such file or directory May 10 01:39:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212918]: 2024-05-10 01:39:23.338+0000: 212918: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:39:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212918]: 2024-05-10 01:39:23.338+0000: 212918: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:39:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212918]: 2024-05-10 01:39:23.338+0000: 212918: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/el94-src-backup-and-restore-on-reboot-host1_VARS.qcow2 May 10 01:39:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[212918]: 2024-05-10 01:39:23.338+0000: 212918: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-el94-src@backup-and-restore-on-reboot/el94-src-backup-and-restore-on-reboot-host1.qcow2 May 10 01:39:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-xyibqaok-vmlinuz: No such file or directory May 10 01:39:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-xyibqaok-vmlinuz: No such file or directory May 10 01:39:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:39:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:39:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-453qxn5q-vmlinuz: No such file or directory May 10 01:39:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-nukfx4iw-initrd.img: No such file or directory May 10 01:39:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[215920]: 2024-05-10 01:39:41.479+0000: 215920: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:39:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[215920]: 2024-05-10 01:39:41.479+0000: 215920: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:39:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[215920]: 2024-05-10 01:39:41.479+0000: 215920: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/cos9-src-storage-host1_VARS.qcow2 May 10 01:39:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[215920]: 2024-05-10 01:39:41.479+0000: 215920: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-cos9-src@storage/cos9-src-storage-host1.qcow2 May 10 01:39:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-453qxn5q-vmlinuz: No such file or directory May 10 01:39:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-453qxn5q-vmlinuz: No such file or directory May 10 01:39:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:39:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:39:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:39:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-a3kjjkqg-vmlinuz: No such file or directory May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-11a3jfg3-initrd.img: No such file or directory May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[217937]: 2024-05-10 01:40:10.580+0000: 217937: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[217937]: 2024-05-10 01:40:10.580+0000: 217937: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[217937]: 2024-05-10 01:40:10.580+0000: 217937: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/el94-src-backups-host1_VARS.qcow2 May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[217937]: 2024-05-10 01:40:10.580+0000: 217937: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-el94-src@backups/el94-src-backups-host1.qcow2 May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-a3kjjkqg-vmlinuz: No such file or directory May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-a3kjjkqg-vmlinuz: No such file or directory May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-rnhgchz9-vmlinuz: No such file or directory May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-bze0dkh4-initrd.img: No such file or directory May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[217999]: 2024-05-10 01:40:10.826+0000: 217999: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[217999]: 2024-05-10 01:40:10.826+0000: 217999: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[217999]: 2024-05-10 01:40:10.826+0000: 217999: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/el94-src-log-scan-host1_VARS.qcow2 May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[217999]: 2024-05-10 01:40:10.826+0000: 217999: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-el94-src@log-scan/el94-src-log-scan-host1.qcow2 May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-rnhgchz9-vmlinuz: No such file or directory May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-rnhgchz9-vmlinuz: No such file or directory May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-4ht7ynue-vmlinuz: No such file or directory May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-al0s_qju-initrd.img: No such file or directory May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[218027]: 2024-05-10 01:40:10.950+0000: 218027: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[218027]: 2024-05-10 01:40:10.950+0000: 218027: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[218027]: 2024-05-10 01:40:10.950+0000: 218027: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/el94-src-greenboot-host1_VARS.qcow2 May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[218027]: 2024-05-10 01:40:10.950+0000: 218027: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-el94-src@greenboot/el94-src-greenboot-host1.qcow2 May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-4ht7ynue-vmlinuz: No such file or directory May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-4ht7ynue-vmlinuz: No such file or directory May 10 01:40:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:40:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:40:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-j1xnckhk-vmlinuz: No such file or directory May 10 01:40:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-iaihmf_1-initrd.img: No such file or directory May 10 01:40:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[219313]: 2024-05-10 01:40:20.117+0000: 219313: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:40:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[219313]: 2024-05-10 01:40:20.117+0000: 219313: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:40:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[219313]: 2024-05-10 01:40:20.117+0000: 219313: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/el94-src-multi-nic-host1_VARS.qcow2 May 10 01:40:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[219313]: 2024-05-10 01:40:20.118+0000: 219313: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-el94-src@multi-nic/el94-src-multi-nic-host1.qcow2 May 10 01:40:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-j1xnckhk-vmlinuz: No such file or directory May 10 01:40:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-j1xnckhk-vmlinuz: No such file or directory May 10 01:40:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:40:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:40:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-1h9q_e8_-vmlinuz: No such file or directory May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-74b14nkc-initrd.img: No such file or directory May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[219806]: 2024-05-10 01:40:30.228+0000: 219806: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[219806]: 2024-05-10 01:40:30.228+0000: 219806: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[219806]: 2024-05-10 01:40:30.228+0000: 219806: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/el94-src-osconfig-lifecycle-host1_VARS.qcow2 May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[219806]: 2024-05-10 01:40:30.229+0000: 219806: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-el94-src@osconfig-lifecycle/el94-src-osconfig-lifecycle-host1.qcow2 May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-1h9q_e8_-vmlinuz: No such file or directory May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-1h9q_e8_-vmlinuz: No such file or directory May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-dkznztgl-vmlinuz: No such file or directory May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-cwgp2jnt-initrd.img: No such file or directory May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[219863]: 2024-05-10 01:40:30.671+0000: 219863: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[219863]: 2024-05-10 01:40:30.671+0000: 219863: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[219863]: 2024-05-10 01:40:30.671+0000: 219863: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/el94-src-optional-host1_VARS.qcow2 May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[219863]: 2024-05-10 01:40:30.671+0000: 219863: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-el94-src@optional/el94-src-optional-host1.qcow2 May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-dkznztgl-vmlinuz: No such file or directory May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-dkznztgl-vmlinuz: No such file or directory May 10 01:40:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:40:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:40:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-tl221r48-vmlinuz: No such file or directory May 10 01:40:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-byxty49q-initrd.img: No such file or directory May 10 01:40:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[220293]: 2024-05-10 01:40:34.537+0000: 220293: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:40:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[220293]: 2024-05-10 01:40:34.537+0000: 220293: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:40:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[220293]: 2024-05-10 01:40:34.537+0000: 220293: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/el94-src-standard-suite2-host1_VARS.qcow2 May 10 01:40:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[220293]: 2024-05-10 01:40:34.538+0000: 220293: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-el94-src@standard-suite2/el94-src-standard-suite2-host1.qcow2 May 10 01:40:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-tl221r48-vmlinuz: No such file or directory May 10 01:40:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-tl221r48-vmlinuz: No such file or directory May 10 01:40:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:40:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-of4u2gx1-vmlinuz: No such file or directory May 10 01:40:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-g8vm0w2x-initrd.img: No such file or directory May 10 01:40:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[220537]: 2024-05-10 01:40:36.297+0000: 220537: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:40:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[220537]: 2024-05-10 01:40:36.297+0000: 220537: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:40:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[220537]: 2024-05-10 01:40:36.297+0000: 220537: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/el94-src-osconfig-misc-host1_VARS.qcow2 May 10 01:40:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[220537]: 2024-05-10 01:40:36.298+0000: 220537: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-el94-src@osconfig-misc/el94-src-osconfig-misc-host1.qcow2 May 10 01:40:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-of4u2gx1-vmlinuz: No such file or directory May 10 01:40:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-of4u2gx1-vmlinuz: No such file or directory May 10 01:40:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:40:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:40:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:40:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-04pq4kw5-vmlinuz: No such file or directory May 10 01:40:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-t6r3yg94-initrd.img: No such file or directory May 10 01:40:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[221306]: 2024-05-10 01:40:43.068+0000: 221306: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:40:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[221306]: 2024-05-10 01:40:43.068+0000: 221306: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:40:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[221306]: 2024-05-10 01:40:43.068+0000: 221306: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/el94-src-storage-host1_VARS.qcow2 May 10 01:40:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[221306]: 2024-05-10 01:40:43.069+0000: 221306: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-el94-src@storage/el94-src-storage-host1.qcow2 May 10 01:40:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-04pq4kw5-vmlinuz: No such file or directory May 10 01:40:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-04pq4kw5-vmlinuz: No such file or directory May 10 01:40:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:40:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-s66huf2h-vmlinuz: No such file or directory May 10 01:40:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-7a0ku3hk-initrd.img: No such file or directory May 10 01:40:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[222013]: 2024-05-10 01:40:44.568+0000: 222013: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 01:40:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[222013]: 2024-05-10 01:40:44.568+0000: 222013: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 01:40:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[222013]: 2024-05-10 01:40:44.568+0000: 222013: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/el94-src-osconfig-cleanup-data-host1_VARS.qcow2 May 10 01:40:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[222013]: 2024-05-10 01:40:44.569+0000: 222013: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-el94-src@osconfig-cleanup-data/el94-src-osconfig-cleanup-data-host1.qcow2 May 10 01:40:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-s66huf2h-vmlinuz: No such file or directory May 10 01:40:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-s66huf2h-vmlinuz: No such file or directory May 10 01:40:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction May 10 01:40:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:40:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data If max_map_count is a virtualization target # semanage fcontext -a -t virt_image_t 'max_map_count' May 10 01:40:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:40:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:41:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:42:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:43:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:44:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:45:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:46:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:47:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:48:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:49:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:50:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:51:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:52:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:53:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:54:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:55:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:56:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:57:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:58:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 01:59:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:00:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:01:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:02:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:03:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:04:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:05 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:06 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:07 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:08 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:09 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:10 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:11 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:12 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:13 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:14 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:15 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:16 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:17 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:18 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:19 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:20 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:21 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:22 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:23 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:24 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:25 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:26 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:27 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:28 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:29 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:30 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:31 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:32 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:33 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:34 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:35 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:36 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:37 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:38 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:39 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:40 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:41 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:42 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:43 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:44 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:45 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:46 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:47 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:48 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:49 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:50 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:51 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:52 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:53 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:54 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:55 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:56 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:57 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:58 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:05:59 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:06:00 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:06:01 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:06:02 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:06:03 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot parse process status data May 10 02:06:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: End of file while reading data: Input/output error May 10 02:06:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-tsczsihf-vmlinuz: No such file or directory May 10 02:06:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: cannot resolve symlink /var/lib/libvirt/boot/virtinst-467ao7f4-initrd.img: No such file or directory May 10 02:06:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[229560]: 2024-05-10 02:06:04.669+0000: 229560: info : libvirt version: 10.0.0, package: 6.2.el9_4 (Red Hat, Inc. , 2024-04-17-21:17:13, ) May 10 02:06:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[229560]: 2024-05-10 02:06:04.669+0000: 229560: info : hostname: i-0d789f7fe1298cec4.us-west-2.compute.internal May 10 02:06:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[229560]: 2024-05-10 02:06:04.669+0000: 229560: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /var/lib/libvirt/qemu/nvram/cos9-src-backups-host1_VARS.qcow2 May 10 02:06:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[229560]: 2024-05-10 02:06:04.670+0000: 229560: warning : virSecurityDACTransactionRun:281 : Ignoring failed restore attempt on /home/ec2-user/microshift/_output/test-images/vm-storage/vm-storage-cos9-src@backups/cos9-src-backups-host1.qcow2 May 10 02:06:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: internal error: child reported (status=125): unable to stat: /var/lib/libvirt/boot/virtinst-tsczsihf-vmlinuz: No such file or directory May 10 02:06:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: unable to stat: /var/lib/libvirt/boot/virtinst-tsczsihf-vmlinuz: No such file or directory May 10 02:06:04 i-0d789f7fe1298cec4.us-west-2.compute.internal libvirtd[179049]: Unable to run security manager transaction