[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: QEMU unexpectedly closed the monitor
From: |
Daniel P . Berrangé |
Subject: |
Re: QEMU unexpectedly closed the monitor |
Date: |
Wed, 31 Jul 2024 11:34:03 +0100 |
User-agent: |
Mutt/2.2.12 (2023-09-09) |
On Wed, Jul 31, 2024 at 11:29:01AM +0100, Peter Maydell wrote:
> On Wed, 31 Jul 2024 at 10:52, Alex Bennée <alex.bennee@linaro.org> wrote:
> > You then need to manually strip out all the various chardevs for libvirt
> > control sockets and you can an equivalent command line you can run from
> > the console. One thing that did jump out as a bit weird to me was:
> >
> > -rtc base=utc -no-shutdown -no-acpi -boot strict=on \
> > -kernel /home/realm/Image-v6.10 \
> > -initrd /home/realm/rootfs.cpio \
> > -append 'earlycon console=ttyAMA0 rdinit=/sbin/init rw root=/dev/vda
> > acpi=on'
>
> Also worth checking here I guess is whether virt-install
> is running QEMU as a user which doesn't have access to
> the /home/realm/Image-v6.10 etc files -- are they world
> readable?
Most likely it is the directory permissions which are the problem since
$HOME is typically set to deny access from other users, which would include
the user QEMU runs as.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|