Comment 3 for bug 1743643

Can you attach the guest libvirt xml?

I suspect that we're not getting the right disk; the curtin config
includes both serial *and* path; we should have on or the other.
There is another possibility that due to the disk having a valid filesystem
that systemd may be triggering a fsck and mount if the
label of the rootfs matches the host environment.

I'd like to launch a similar guest and recreate the scenario.

On Tue, Jan 16, 2018 at 4:45 PM, Joshua Powers <email address hidden>
wrote:

> First install curtin log: https://paste.ubuntu.com/26400611/
> Checking swapon pointed to /swap.img
>
> Second install
> /tmp/subiquity-curtin-install.conf: https://paste.ubuntu.com/26400656/
> /tmp/subiquity-curtin-install.log: https://paste.ubuntu.com/26400658/
>
> ** Changed in: curtin
> Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1743643
>
> Title:
> Install to dirty disk with swap fails
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1743643/+subscriptions
>