On Thu, Jan 2, 2025 at 8:04 PM Samuel Sieb wrote:
>
> On 1/2/25 4:16 PM, Jeffrey Walton wrote:
> > On Thu, Jan 2, 2025 at 12:26 PM Robert McBroom via users
> > wrote:
> >>
> >> On 12/29/24 4:40 AM, Barry Scott wrote:
> >>
> >> On 29 Dec 2024, at 00:12, Jonathan Billings wrote:
> >>
> >> libvirtd
On 1/2/25 4:16 PM, Jeffrey Walton wrote:
On Thu, Jan 2, 2025 at 12:26 PM Robert McBroom via users
wrote:
On 12/29/24 4:40 AM, Barry Scott wrote:
On 29 Dec 2024, at 00:12, Jonathan Billings wrote:
libvirtd was changed to use socket activation, so it *should* start if the
libvirtd.socket is
On Thu, Jan 2, 2025 at 12:26 PM Robert McBroom via users
wrote:
>
> On 12/29/24 4:40 AM, Barry Scott wrote:
>
> On 29 Dec 2024, at 00:12, Jonathan Billings wrote:
>
> libvirtd was changed to use socket activation, so it *should* start if the
> libvirtd.socket is enabled and activated
>
> Running
On 1/2/25 9:25 AM, Robert McBroom via users wrote:
On 12/29/24 4:40 AM, Barry Scott wrote:
On 29 Dec 2024, at 00:12, Jonathan Billings wrote:
libvirtd was changed to use socket activation, so it *should* start
if the libvirtd.socket is enabled and activated
Running Virtual machine Manag
On 12/29/24 4:40 AM, Barry Scott wrote:
On 29 Dec 2024, at 00:12, Jonathan Billings wrote:
libvirtd was changed to use socket activation, so it *should* start
if the libvirtd.socket is enabled and activated
Running Virtual machine Manager will connect to the socket and every
thing will
On 12/29/24 1:33 AM, francis.montag...@inria.fr wrote:
Hi.
On Sun, 29 Dec 2024 01:00:18 -0500 Robert McBroom via users wrote:
On 12/28/24 2:09 PM, francis.montag...@inria.fr wrote:
What gives ?
systemctl is-enabled libvirtd
Says enabled but still requires the start command to find the v
> On 29 Dec 2024, at 00:12, Jonathan Billings wrote:
>
> libvirtd was changed to use socket activation, so it *should* start if the
> libvirtd.socket is enabled and activated
Running Virtual machine Manager will connect to the socket and every thing will
start running.
To use Virtual machine
Hi.
On Sun, 29 Dec 2024 01:00:18 -0500 Robert McBroom via users wrote:
> On 12/28/24 2:09 PM, francis.montag...@inria.fr wrote:
>> What gives ?
>>systemctl is-enabled libvirtd
> Says enabled but still requires the start command to find the virtual
> machines
It is thus probably failing at
On 12/28/24 2:09 PM, francis.montag...@inria.fr wrote:
Hi
On Sat, 28 Dec 2024 14:00:17 -0500 Robert McBroom via users wrote:
What needs to be set to get the virtual machines to initialize on the
second installation?
Just enable this service I think.
What gives ?
systemctl is-enabled libv
On Dec 28, 2024, at 14:00, Robert McBroom via users
wrote:
>
> Have two installations of f41 setup to run virtual machines. On one, all
> that is required to get started is to execute "virt-manager" in a terminal
> with privilege. On the other, I have to use "systemctl start libvirtd" first
On Sat, 28 Dec 2024 at 19:00, Robert McBroom via users <
users@lists.fedoraproject.org> wrote:
> Have two installations of f41 setup to run virtual machines. On one, all
> that is required to get started is to execute "virt-manager" in a
> terminal with privilege. On the other, I have to use "syst
Hi
On Sat, 28 Dec 2024 14:00:17 -0500 Robert McBroom via users wrote:
> What needs to be set to get the virtual machines to initialize on the
> second installation?
Just enable this service I think.
What gives ?
systemctl is-enabled libvirtd
If disabled then executes:
sudo systemctl ena
Have two installations of f41 setup to run virtual machines. On one, all
that is required to get started is to execute "virt-manager" in a
terminal with privilege. On the other, I have to use "systemctl start
libvirtd" first or "virt-manager" doesn't find any of the installed
machines. Nothing
On 11/22/17 20:01, Patrick O'Callaghan wrote:
> I think you mean "semodule -DB" as that's what the manpage gives as an
> example (BTW the page is phenomenally hard to understand, not least
> because at one point it uses MODE, at another it says "module" and at a
> third it says KIND, and it isn't c
On Tue, 2017-11-21 at 16:03 -0800, Samuel Sieb wrote:
> On 11/14/2017 02:31 PM, Patrick O'Callaghan wrote:
> > On trying to fire up a VM using virt-manager, I get "unable to map
> > backing store for guest RAM: Permission denied".
> >
> > I use hugepages to lock down memory for the VM, which may
On Wed, 2017-11-22 at 12:12 +0800, Ed Greshko wrote:
> On 11/15/17 20:20, Patrick O'Callaghan wrote:
> > On Tue, 2017-11-14 at 14:50 -0800, Rick Stevens wrote:
> > > On 11/14/2017 02:31 PM, Patrick O'Callaghan wrote:
> > > > On trying to fire up a VM using virt-manager, I get "unable to map
> > > >
On 11/15/17 20:20, Patrick O'Callaghan wrote:
> On Tue, 2017-11-14 at 14:50 -0800, Rick Stevens wrote:
>> On 11/14/2017 02:31 PM, Patrick O'Callaghan wrote:
>>> On trying to fire up a VM using virt-manager, I get "unable to map
>>> backing store for guest RAM: Permission denied".
>>>
>>> I use huge
On 11/14/2017 02:31 PM, Patrick O'Callaghan wrote:
On trying to fire up a VM using virt-manager, I get "unable to map
backing store for guest RAM: Permission denied".
I use hugepages to lock down memory for the VM, which may be relevant
for the error. This worked correctly on F26 just before t
On Tue, 2017-11-21 at 13:04 -0800, Rick Stevens wrote:
> On 11/21/2017 12:31 PM, Cole Robinson wrote:
> > On 11/14/2017 05:31 PM, Patrick O'Callaghan wrote:
> > > On trying to fire up a VM using virt-manager, I get "unable to map
> > > backing store for guest RAM: Permission denied".
> > >
> > > I
On Tue, 2017-11-21 at 15:31 -0500, Cole Robinson wrote:
> On 11/14/2017 05:31 PM, Patrick O'Callaghan wrote:
> > On trying to fire up a VM using virt-manager, I get "unable to map
> > backing store for guest RAM: Permission denied".
> >
> > I use hugepages to lock down memory for the VM, which may
On 11/21/2017 12:31 PM, Cole Robinson wrote:
> On 11/14/2017 05:31 PM, Patrick O'Callaghan wrote:
>> On trying to fire up a VM using virt-manager, I get "unable to map
>> backing store for guest RAM: Permission denied".
>>
>> I use hugepages to lock down memory for the VM, which may be relevant
>>
On 11/14/2017 05:31 PM, Patrick O'Callaghan wrote:
> On trying to fire up a VM using virt-manager, I get "unable to map
> backing store for guest RAM: Permission denied".
>
> I use hugepages to lock down memory for the VM, which may be relevant
> for the error. This worked correctly on F26 just be
On Tue, 2017-11-14 at 14:50 -0800, Rick Stevens wrote:
> On 11/14/2017 02:31 PM, Patrick O'Callaghan wrote:
> > On trying to fire up a VM using virt-manager, I get "unable to map
> > backing store for guest RAM: Permission denied".
> >
> > I use hugepages to lock down memory for the VM, which may
On 11/14/2017 02:31 PM, Patrick O'Callaghan wrote:
> On trying to fire up a VM using virt-manager, I get "unable to map
> backing store for guest RAM: Permission denied".
>
> I use hugepages to lock down memory for the VM, which may be relevant
> for the error. This worked correctly on F26 just be
On trying to fire up a VM using virt-manager, I get "unable to map backing
store for guest RAM: Permission denied".
I use hugepages to lock down memory for the VM, which may be relevant for
the error. This worked correctly on F26 just before the upgrade to F27. I
have changed nothing in my VM conf
25 matches
Mail list logo
