|Subject:||[Qemu-discuss] Fwd: Re: Starting without '-kernel'; isolating VMs|
|Date:||Tue, 13 Aug 2013 08:36:52 -0700|
1. Your guide describes setting up a chroot, you'd have to describe where you diverged.
2. I noticed your Guide utilizes an incomplete fs, it requires a bind mounts. As you say, that may be typical of debootstrap which I've only looked at and don't use regularly.
3. The tarballs I've used from OpenVZ were built entirely from official distro repos which ordinarily do not install proprietary apps but as you say there is no gaurantee since all are built by volunteers. Maybe install, then list all packages if that is important to you.
Personally I've never installed a QEMU VM using an ISO except as part of KVM or XEN. All my "pure QEMU" VMs have been built using bootstrap or full fs.
Did you intentionally reply off-list? If not, please resend your
message to the list and forward mine.
> Have you considered running a bootstrap fs just to see whether your
> QEMU is working properly?
I’ve already tried that using this guide . QEMU failed to boot with
“No bootable device.”
> I've found that these are complete file systems (no need for bind
> mounts and the like)
Those tarballs probably contain or might allow to install non-free
software , so I’m not going to use them.
How can I create a filesystem that doesn’t require bind mounts?
‘debootstrap’ requires to bind mount ‘/dev’, for instance.
Note that the above doesn’t explain why I failed to install from two ISO
images using two different QEMU versions on two different machines. So
I’m probably doing something wrong.
Description: PGP signature
|[Prev in Thread]||Current Thread||[Next in Thread]|