Hi, On Thu, Oct 17, 2024 at 04:38:13AM +0000, Mike wrote: > I was running `xen-create-image`…
Just a note that Xen is pretty exotic at this point and very few people will know what you are talking about. I use Xen a lot, but most people who play with VMs on Linux only use KVM/qemu. You may have more luck asking xen-related questions on the xen-users mailing list. Also, the xen-tools package which provides xen-create-image I think is pretty old-fashioned and unmaintained now. You may have issues with it. It isn't necessarily the best way to create Xen domUs. > …when it failed near the end trying to `umount` the > `/tmp/SoMeThInG/proc` mount that it had created. `findmnt` showed me > that it was mounted on itself, as was `/proc`! > > I got it unmounted with `--lazy`. > > I'm guessing that the Xen script was merely copying what it saw; the question > remaining then is: Why would /proc have been mounted on itself? Anyone seen > this before? The way that xen-create-image works is that it creates a temporary directory for the root filesystem of the domU and does a debootstrap into it. As part of that process it will have bind mounted virtual filesystems like /dev, /proc and /sys from your dom0 into the temporary directory. That's what you're seeing here. Your problem about being unable to umount it may be down to some process being left running that uses the /proc that is inside the temporary directory. It's possible you could have success with something like `lsof` to try to find which process has /tmp/SoMeThInG/proc in use. Personally I install Debian domUs by booting the netinst installer and doing a (largely automated by preseed) regular install. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
