On Tuesday, 31 May 2016 16:18:49 AEST you wrote:
> Julian, Fryderyk, or someone else who's affected,
>
> If you aren't seeing a cloud-init.log on affected instances, could you
> instead tar up all of /var/log and put it somewhere we can examine?
>
The problem is that the disk image doesn't get flushed at any point, so
there's nothing in the logs at all - it's the original qcow. And because I
have to hard kill the VM, it will never flush.
On Tuesday, 31 May 2016 16:18:49 AEST you wrote:
> Julian, Fryderyk, or someone else who's affected,
>
> If you aren't seeing a cloud-init.log on affected instances, could you
> instead tar up all of /var/log and put it somewhere we can examine?
>
The problem is that the disk image doesn't get flushed at any point, so
there's nothing in the logs at all - it's the original qcow. And because I
have to hard kill the VM, it will never flush.
root@proxmox15: /var/lib/ vz/images/ 204# qemu-nbd --connect=/dev/nbd0 vm- /var/lib/ vz/images/ 204# mount /dev/nbd0p1 /mnt/tmp /var/lib/ vz/images/ 204# ls /mnt/tmp/var/log
disk-0.qcow2
root@proxmox15:
root@proxmox15:
apt btmp dist-upgrade fsck landscape lastlog unattended-upgrades
upstart wtmp