Gabriel Mougard

Also, interestingly, I tried with a different root size and a different `state.size` like the following: ```bash lxc launch ubuntu:22.04 vtest --vm -d root,size=20GiB -d root,size.state=10GiB -c limits.memory=1GiB -c limits.cpu=2...

Also, I monitored my host IOPS using `watch iostat` and there is no delta between (maybe 2 or 3 kB/s but it fluctuate so it's not that) the `kB_wrtn/s` before...

I also tried to do it "locally" with two VM acting as machines and the same happened (even with LXD `5.0.2-838e1b2` inside my VMs) so I don't think my network...

They have the same arch but they are not 'exactly' the same: source: ``` Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 43 bits physical, 48 bits virtual Byte Order:...

**Update**: I also checked with a ZFS storage driver between my two physical machines and i see the same error happening (`Error: Failed instance creation: Error transferring instance data: Failed...

@mseralessandri I also retried on my side with latest/edge. The problem seems to have disappeared. Maybe I ran into some slow network / machine issue at that time. I'm closing...

I have tried monitoring the `lxdbr0` status (every 0.1s) to check for any bridge flapping while restarting one of my container (`u1`), and here is what I got:  In...

@mr-cal @CalvoM @tomponline I found a hack: In order to ensure that the bridge is always up, regardless of whether containers are running, I created a dummy interface on the...

@CalvoM can you reproduce this workaround ?

@tomponline I opened a new issue as this is a bit different than https://github.com/canonical/lxd/issues/12648