On 3/29/25 7:10 PM, Sam Varshavchik wrote:
ToddAndMargo via users writes:
Hi All,
Anyone know where "upstream" is for qemu-kvm. I'd like to
post an RFE.
rpm -q -i qemu-kvm
comes back with a bunch of stuff, including:
URL : http://www.qemu.org/
and that's whe
ToddAndMargo via users wrote:
> On 3/28/25 4:49 PM, Samuel Sieb wrote:
>> On 3/28/25 2:41 PM, ToddAndMargo via users wrote:
>>> What happens to a running qemu-kvm virtual machine
>>> when the host shuts down or reboots?
>>>
>>> Does the hypervisor
On Sun, 2025-03-30 at 15:00 +1030, Tim via users wrote:
> On Sat, 2025-03-29 at 22:10 -0400, Sam Varshavchik wrote:
> > rpm -q -i qemu-kvm
>
> I always did "rpm -qi", since -i is short for install.
+1, though in this cas
On Sat, 2025-03-29 at 22:10 -0400, Sam Varshavchik wrote:
> rpm -q -i qemu-kvm
I always did "rpm -qi", since -i is short for install.
--
uname -rsvp
Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
Boilerplate: All unexpected mail to my mailbox is
On 3/29/25 7:10 PM, Sam Varshavchik wrote:
ToddAndMargo via users writes:
Hi All,
Anyone know where "upstream" is for qemu-kvm. I'd like to
post an RFE.
rpm -q -i qemu-kvm
comes back with a bunch of stuff, including:
URL : http://www.qemu.org/
and that's whe
On Sat, Mar 29, 2025 at 8:29 PM ToddAndMargo via users
wrote:
>
> Anyone know where "upstream" is for qemu-kvm. I'd like to
> post an RFE.
Let me Google that for you:
<https://www.google.com/search?q=fedora+determi
ToddAndMargo via users writes:
Hi All,
Anyone know where "upstream" is for qemu-kvm. I'd like to
post an RFE.
rpm -q -i qemu-kvm
comes back with a bunch of stuff, including:
URL : http://www.qemu.org/
and that's where I would go to dig up contact info.
Hi All,
Anyone know where "upstream" is for qemu-kvm. I'd like to
post an RFE.
Many thanks,
-T
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora
On 3/29/25 1:19 AM, ToddAndMargo via users wrote:
On 3/28/25 2:41 PM, ToddAndMargo via users wrote:
Hi All,
What happens to a running qemu-kvm virtual machine
when the host shuts down or reboots?
Does the hypervisor issue a shutdown to the VM?
Or freeze and save the vm? Or just cut the vm&#
On 3/28/25 2:41 PM, ToddAndMargo via users wrote:
Hi All,
What happens to a running qemu-kvm virtual machine
when the host shuts down or reboots?
Does the hypervisor issue a shutdown to the VM?
Or freeze and save the vm? Or just cut the vm's
leg off?
Many thanks,
-T
Oh holy Poop!
On 3/28/25 7:39 PM, Todd Zullinger wrote:
ToddAndMargo via users wrote:
On 3/28/25 4:49 PM, Samuel Sieb wrote:
On 3/28/25 2:41 PM, ToddAndMargo via users wrote:
What happens to a running qemu-kvm virtual machine
when the host shuts down or reboots?
Does the hypervisor issue a shutdown to the
On 3/28/25 8:01 PM, ToddAndMargo via users wrote:
On 3/28/25 7:39 PM, Todd Zullinger wrote:
It is handled by the libvirt-guest service, which is not
enabled by default.
$ systemctl status libvirt-guests.service
○ libvirt-guests.service - libvirt guests suspend/resume service
Loaded: loade
On 3/28/25 7:39 PM, Todd Zullinger wrote:
ToddAndMargo via users wrote:
On 3/28/25 4:49 PM, Samuel Sieb wrote:
On 3/28/25 2:41 PM, ToddAndMargo via users wrote:
What happens to a running qemu-kvm virtual machine
when the host shuts down or reboots?
Does the hypervisor issue a shutdown to the
On 3/28/25 4:49 PM, Samuel Sieb wrote:
On 3/28/25 2:41 PM, ToddAndMargo via users wrote:
What happens to a running qemu-kvm virtual machine
when the host shuts down or reboots?
Does the hypervisor issue a shutdown to the VM?
Or freeze and save the vm? Or just cut the vm's
leg off?
It s
On 3/28/25 2:41 PM, ToddAndMargo via users wrote:
What happens to a running qemu-kvm virtual machine
when the host shuts down or reboots?
Does the hypervisor issue a shutdown to the VM?
Or freeze and save the vm? Or just cut the vm's
leg off?
It should freeze it and restore at boot.
Hi All,
What happens to a running qemu-kvm virtual machine
when the host shuts down or reboots?
Does the hypervisor issue a shutdown to the VM?
Or freeze and save the vm? Or just cut the vm's
leg off?
Many thanks,
-T
--
___
users mailing
On 3/25/25 6:05 PM, ToddAndMargo via users wrote:
On 3/25/25 6:01 PM, ToddAndMargo via users wrote:
I never installed "qemu-ga-x86_64.msi" on the guest.
I just did. I have to wait till after hours to reboot the
thing to see if it is fixed and the UAC gets enabled.
I just re
qemu-kvm-9.1.3-2.fc41.x86_64
Windows Server 2025 STD
virto-win-0.1.240.1
I am constantly getting this error in my Windows System
log. Googling tells me what it is but not how to fix it.
But does tell me that if if crashes, it could crash the OS.
A timeout was reached (45000 milliseconds) while
On 3/25/25 6:01 PM, ToddAndMargo via users wrote:
I never installed "qemu-ga-x86_64.msi" on the guest.
I just did. I have to wait till after hours to reboot the
thing to see if it is fixed and the UAC gets enabled.
I just rebooted and cleared the system log. N
On 3/25/25 4:58 PM, ToddAndMargo via users wrote:
On 3/25/25 3:22 PM, Samuel Sieb wrote:
On 3/25/25 3:13 PM, ToddAndMargo via users wrote:
On 3/25/25 12:43 PM, Samuel Sieb wrote:
On 3/25/25 12:28 PM, ToddAndMargo via users wrote:
Hi All,
Fedora 41
qemu-kvm-9.1.3-2.fc41.x86_64
Windows Server
On 3/25/25 3:22 PM, Samuel Sieb wrote:
On 3/25/25 3:13 PM, ToddAndMargo via users wrote:
On 3/25/25 12:43 PM, Samuel Sieb wrote:
On 3/25/25 12:28 PM, ToddAndMargo via users wrote:
Hi All,
Fedora 41
qemu-kvm-9.1.3-2.fc41.x86_64
Windows Server 2025 STD
virto-win-0.1.240.1
I am constantly
On 3/25/25 3:13 PM, ToddAndMargo via users wrote:
On 3/25/25 12:43 PM, Samuel Sieb wrote:
On 3/25/25 12:28 PM, ToddAndMargo via users wrote:
Hi All,
Fedora 41
qemu-kvm-9.1.3-2.fc41.x86_64
Windows Server 2025 STD
virto-win-0.1.240.1
I am constantly getting this error in my Windows System
log
On 3/25/25 12:43 PM, Samuel Sieb wrote:
On 3/25/25 12:28 PM, ToddAndMargo via users wrote:
Hi All,
Fedora 41
qemu-kvm-9.1.3-2.fc41.x86_64
Windows Server 2025 STD
virto-win-0.1.240.1
I am constantly getting this error in my Windows System
log. Googling tells me what it is but not how to fix
On 3/25/25 12:28 PM, ToddAndMargo via users wrote:
Hi All,
Fedora 41
qemu-kvm-9.1.3-2.fc41.x86_64
Windows Server 2025 STD
virto-win-0.1.240.1
I am constantly getting this error in my Windows System
log. Googling tells me what it is but not how to fix it.
But does tell me that if if crashes
Hi All,
Fedora 41
qemu-kvm-9.1.3-2.fc41.x86_64
Windows Server 2025 STD
virto-win-0.1.240.1
I am constantly getting this error in my Windows System
log. Googling tells me what it is but not how to fix it.
But does tell me that if if crashes, it could crash the OS.
A timeout was reached
Hi All,
If I do not have any activity in my virtual machine (does
matter what OS) for a bit of time, say 30 minutes, the
mouse works, but I can't type. Exiting the viewer
and restarting it and happy camping returns.
Is this just a bug or is it just some configuration?
Many thanks,
-T
--
~
moving along OK with the install and am now up to my use of
qemu and virt-manager:
dnf groupinstall "virtualization"
dnf install qemu virt-manager libvirt
dnf group install virtualization
No quotes needed. Now. I did need those, I believe, some versions ago.
That was only needed i
up to my use of
qemu and virt-manager:
dnf groupinstall "virtualization"
dnf install qemu virt-manager libvirt
dnf group install virtualization
No quotes needed. Now. I did need those, I believe, some versions ago.
That was only needed if you used the long name and it had s
the VM.
With both it should be possible to get things going with virt manager.
My VMs have their images in /var/lib/libvirt/images and their XML
config file in /etc/libvirt/qemu.
I guess you copy into these folders and startup virt manager.
Yep. Got those steps down in my notes from last time
On 2/25/25 17:18, Samuel Sieb wrote:
On 2/25/25 2:01 PM, Robert Moskowitz wrote:
I am finally upgrading from my F38 system. I do a clean install on
another system, then migrate my user account.
So I am moving along OK with the install and am now up to my use of
qemu and virt-manager
On 2/25/25 2:01 PM, Robert Moskowitz wrote:
I am finally upgrading from my F38 system. I do a clean install on
another system, then migrate my user account.
So I am moving along OK with the install and am now up to my use of qemu
and virt-manager:
dnf groupinstall "virtualization
it should be possible to get things going with virt manager.
My VMs have their images in /var/lib/libvirt/images and their XML config file
in /etc/libvirt/qemu.
I guess you copy into these folders and startup virt manager.
Make sure you have added your user to the libvirt group to allow virt manager t
On Tue, 2025-02-25 at 17:01 -0500, Robert Moskowitz wrote:
> I am finally upgrading from my F38 system. I do a clean install on
> another system, then migrate my user account.
>
> So I am moving along OK with the install and am now up to my use of qemu
> and virt-manager:
>
I am finally upgrading from my F38 system. I do a clean install on
another system, then migrate my user account.
So I am moving along OK with the install and am now up to my use of qemu
and virt-manager:
dnf groupinstall "virtualization"
dnf install qemu virt-manager libvirt
Wel
On 2/1/25 10:27 PM, ToddAndMargo via users wrote:
Hi All,
I am trying to mount two qemu-kvm shared directories.
I have the following configured:
function="0x0"/>
function="0x0"/>
Do I need a separate type="pci" a
Hi All,
I am trying to mount two qemu-kvm shared directories.
I have the following configured:
function="0x0"/>
function="0x0"/>
Do I need a separate type="pci" address?
Many thanks,
-T
--
__
I sincerely thank everyone who provided feedback - it was incredibly
detailed and helpful. In the meantime, I discovered an alternative
approach to achieving a shared setup by using:
Windows VirtIO Drivers (https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers)
+
Virtiofs (https://virtio-fs.gitlab
On Sun, 2025-01-19 at 18:29 -0800, ToddAndMargo via users wrote:
> Tip: if you are sharing between Windows machines,
> share on the oldest OS, not the newest. M$ acts
> like a jerk sharing from a new machine to an older
> machine.
I always tweaked the parameter that determined who would be master
On 1/19/25 7:05 AM, Earl Ramirez wrote:
And got nowhere trying SMB.
I had similar headache with a windows VM on Fedora host and permitting
SMB on firewalld libvirt zone resolved the issue
Hi Earl,
I have Windows qemu-kvm virtual machines with my Fedora 41
host Samba (cifs) sharing
On 1/19/25 2:03 AM, Tim via users wrote:
And is this consistent in describing when you share a resource, and how
networking is described?
Superficially, yes. But all kind of stuff pop up to
annoy you. And it is not always straight forward.
But far easier than Samba initially. Certainly very
> And got nowhere trying SMB.
>
I had similar headache with a windows VM on Fedora host and permitting SMB
on firewalld libvirt zone resolved the issue
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le..
Tim:
>> Which versions of Windows have you discovered have that backwards?
ToddAndMargo:
> All of them. The problem is the user only see the words "public"
> and "private". They do not read the description of either as
> they do not understand such "geek" speak. M$ does adequately
> describe w
On 1/18/25 11:02 PM, Tim via users wrote:
Which versions of Windows have you discovered have that backwards?
All of them. The problem is the user only see the words "public"
and "private". They do not read the description of either as
they do not understand such "geek" speak. M$ does adequa
On Sat, 2025-01-18 at 08:00 -0800, ToddAndMargo via users wrote:
> M$ has a bizarre way of stating such:
>
> Private: a hazardous environment with lots of
> potential bad guys on the same network.
> You are a network island and can see no
> network resour
On 1/18/25 8:00 AM, ToddAndMargo via users wrote:
In the registry, first identiry the {} from
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\NetworkList\Profiles\
Then switch "catagory" to the type of network you want. For example:
if {} was {162BD447-E8
On 1/17/25 5:33 AM, Paul Smith wrote:
Dear Fedora Users,
I’m encountering an issue where I cannot access a Samba shared folder
from a Windows 10 guest running on a host configured with virt-manager
+ QEMU/KVM. Here are the details of the situation:
--> Host Configuration and Status
The Sa
Dear Fedora Users,
I’m encountering an issue where I cannot access a Samba shared folder
from a Windows 10 guest running on a host configured with virt-manager
+ QEMU/KVM. Here are the details of the situation:
--> Host Configuration and Status
The Samba shared folder is accessible from
> >> will start running.
> >> To use Virtual machine manager without password prompts add your user to
> >> the libvirt group.
> >>
> >> sudo useradd -G libvert -a
> >>
> >> useradd -G libvirt -a rm3
> >> userad
x27;a'
Usage: useradd [options] LOGIN
useradd -D
useradd -D [options]
This is from a Ubuntu 20 machine with QEMU/KVM:
$ cat /etc/group | grep virt
libvirt:x:145:jwalton,lboszormenyi,djb,pgutmann,apolyakov
libvirt-qemu:x:64055:libvirt-qemu
libvirt-dnsmasq:x:146:
gt; useradd: invalid option -- 'a'
> Usage: useradd [options] LOGIN
> useradd -D
> useradd -D [options]
This is from a Ubuntu 20 machine with QEMU/KVM:
$ cat /etc/group | grep virt
libvirt:x:145:jwalton,lboszormenyi,djb,pgutmann,apolyakov
libvirt-qemu:x:6405
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
ne to remove. If
> > > it's only a recommends, then you could probably just uninstall qemu
> > > anyway.
> > > Why is it a problem to have qemu installed?
> >
> > I'd rather not have software installed that I don't ever plan on using.
> >
bably just uninstall qemu anyway.
Why is it a problem to have qemu installed?
I'd rather not have software installed that I don't ever plan on using.
I should probably do a clean install on this system, I've been upgrading it
since FC 25 or so.
You might try a `dnf group remove con
On Wed, Dec 4, 2024 at 8:16 PM Patrick Mansfield via users
wrote:
>
> On Wed, Dec 04, 2024 at 10:32:48AM -0800, Samuel Sieb wrote:
> > If you aren't using any containers, then it should be fine to remove. If
> > it's only a recommends, then you could probably just un
On Wed, Dec 04, 2024 at 10:32:48AM -0800, Samuel Sieb wrote:
> If you aren't using any containers, then it should be fine to remove. If
> it's only a recommends, then you could probably just uninstall qemu anyway.
> Why is it a problem to have qemu installed?
I'd
On 12/4/24 9:59 AM, Patrick Mansfield via users wrote:
On Wed, Dec 04, 2024 at 10:44:00AM -0500, Todd Zullinger wrote:
Dave Close wrote:
Patrick Mansfield wrote:
Why does the most recent systemd update pull in qemu?
That seems excessive.
Currently running Fedora 41 with systemd version
On Wed, Dec 04, 2024 at 10:44:00AM -0500, Todd Zullinger wrote:
> Dave Close wrote:
> > Patrick Mansfield wrote:
> >
> >> Why does the most recent systemd update pull in qemu?
> >> That seems excessive.
> >>
> >> Currently running Fedora 41 with
Dave Close wrote:
> Patrick Mansfield wrote:
>
>> Why does the most recent systemd update pull in qemu?
>> That seems excessive.
>>
>> Currently running Fedora 41 with systemd version 256.8-1,
>> looks like the update moves me to systemd version
>
Patrick Mansfield wrote:
>Why does the most recent systemd update pull in qemu?
>That seems excessive.
>
>Currently running Fedora 41 with systemd version 256.8-1, looks like
>the update moves me to systemd version 256.9-2.
My two systems running F41 include systemd 256.9-2 and
Why does the most recent systemd update pull in qemu?
That seems excessive.
Currently running Fedora 41 with systemd version 256.8-1, looks like the update
moves me
to systemd version 256.9-2.
-- Patrick
--
___
users mailing list -- users
On Wed, 2024-10-16 at 10:48 +0200, Jouk Jansen via users wrote:
> Hi all,
>
> I have a virtual machine (KVM/Qemu) on a Fedora host, that uses an internet
> device by using the passthrough option. However after upgrading from kernel
> 6.10.12-200.fc40.x86_64 to 6.11.3-200.fc40.x86_
Hi all,
I have a virtual machine (KVM/Qemu) on a Fedora host, that uses an internet
device by using the passthrough option. However after upgrading from kernel
6.10.12-200.fc40.x86_64 to 6.11.3-200.fc40.x86_64, The virtual machine
refuses to run, telling me that I have to check the IOMMU option
On 5/14/24 3:06 PM, Sbob wrote:
Where do I find the logs?
The logs from the Linux system that you ran the "ifconfig" on.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fed
Where do I find the logs?
On 5/14/24 2:46 PM, Samuel Sieb wrote:
On 5/14/24 10:48 AM, Sbob wrote:
However, I have several ALMA 8 VMWare vm's and I am able to convert
them like this:
# virt-v2v -i vmx /data/vmware/Alma-HA-DR-Data3/Alma-HA-DR-Data3.vmx
-o libvirt -of qcow2 -os default -n defa
On 5/14/24 10:48 AM, Sbob wrote:
However, I have several ALMA 8 VMWare vm's and I am able to convert them
like this:
# virt-v2v -i vmx /data/vmware/Alma-HA-DR-Data3/Alma-HA-DR-Data3.vmx -o
libvirt -of qcow2 -os default -n default
where the original VMware folder is at /data/vmware/Alma-HA-DR
Hi;
I have just installed Fedora 40 and all the kvm/qemu/libvirt bits
I can run virt-manager and install a new guest and when I start the
guest it comes up automatically with a valid network / ip address
I also converted a fedora 38 vm that has a gui interface and it also
works fine
On 12/12/23 20:03, Sbob wrote:
Hi;
I'm running Fedora 39, I have installed qemu / libvirt / kvm
I have found many guides on setting up bridged networking but none have
worked. Can someone point me to a proper guide?
Thanks in advance
Setting up bridged networking is nowhere ne
On Tue, 12 Dec 2023 19:03:01 -0700
Sbob wrote:
> Hi;
>
>
> I'm running Fedora 39, I have installed qemu / libvirt / kvm
>
>
> I have found many guides on setting up bridged networking but none have
> worked. Can someone point me to a proper guide?
>
For wha
Hi;
I'm running Fedora 39, I have installed qemu / libvirt / kvm
I have found many guides on setting up bridged networking but none have
worked. Can someone point me to a proper guide?
Thanks in advance
--
___
users mailing list --
d mksSandbox-0.logvmware.log
> Dev-Fedora-s001.vmdk Dev-Fedora.vmdkmksSandbox-1.log
>
> I tried this:
>
>
> 1) use qemu-img convert to convert the Dev-Fedora.vmdk file:
>
> # qemu-img convert -f vmdk -O qcow2 Dev-Fedora.vmdk Dev-Fedora.qcow2
>
> this c
-Fedora.vmx.lck
vmware-1.log
Dev-Fedora-9.scoreboard Dev-Fedora-s006.vmdk mksSandbox
vmware-2.log
Dev-Fedora.nvram Dev-Fedora.scoreboard mksSandbox-0.log
vmware.log
Dev-Fedora-s001.vmdk Dev-Fedora.vmdk mksSandbox-1.log
I tried this:
1) use qemu-img convert to
On Wed, Nov 1, 2023 at 6:27 PM Patrick O'Callaghan
wrote:
>
> On Wed, 2023-11-01 at 18:22 -0400, Jeffrey Walton wrote:
> > Hi Everyone,
> >
> > I recently started using libvirt/KVM/QEMU. In the past I used
> > VirtualBox. When using VirtualBox I turned off Sec
On Wed, 2023-11-01 at 18:22 -0400, Jeffrey Walton wrote:
> Hi Everyone,
>
> I recently started using libvirt/KVM/QEMU. In the past I used
> VirtualBox. When using VirtualBox I turned off Secure Boot because I
> did not want to manage signing of tainted modules.
>
> My que
Hi Everyone,
I recently started using libvirt/KVM/QEMU. In the past I used
VirtualBox. When using VirtualBox I turned off Secure Boot because I
did not want to manage signing of tainted modules.
My question is, are libvirt/KVM/QEMU modules signed out-of-the-box?
Or, can I enable Secure Boot
On 7/8/23 21:55, ToddAndMargo via users wrote:
Fedora 38
Is the version of qemu-kvm in the Fedora
repo using monolithic or modular daemons?
Many thanks,
-T
I do believe it is modular.
I followed these direction (I think Sam gave them to me)
https://www.libvirt.org/daemons.html#switching-to
Fedora 38
Is the version of qemu-kvm in the Fedora
repo using monolithic or modular daemons?
Many thanks,
-T
--
~~
Computers are like air conditioners.
They malfunction when you open windows
On 3/10/23 01:25, Peter Boy wrote:
Am 10.03.2023 um 07:00 schrieb Robert McBroom via
users:
On 3/10/23 00:41, Jeffrey Walton wrote:
On Fri, Mar 10, 2023 at 12:36 AM Robert McBroom via users
wrote:
Installed CentOS-STREAM 8 ON A QEMU/KVM virtual machine. Initially the
reboot went only
> Am 10.03.2023 um 07:00 schrieb Robert McBroom via users
> :
>
>
> On 3/10/23 00:41, Jeffrey Walton wrote:
>> On Fri, Mar 10, 2023 at 12:36 AM Robert McBroom via users
>> wrote:
>>> Installed CentOS-STREAM 8 ON A QEMU/KVM virtual machine. Initially
On 3/10/23 00:41, Jeffrey Walton wrote:
On Fri, Mar 10, 2023 at 12:36 AM Robert McBroom via users
wrote:
Installed CentOS-STREAM 8 ON A QEMU/KVM virtual machine. Initially the
reboot went only to a blank display. Editing the grub menu to give a
terminal boot was successful.
Succeeded to get
On Fri, Mar 10, 2023 at 12:36 AM Robert McBroom via users
wrote:
>
> Installed CentOS-STREAM 8 ON A QEMU/KVM virtual machine. Initially the
> reboot went only to a blank display. Editing the grub menu to give a
> terminal boot was successful.
>
> Succeeded to get a graphical
Installed CentOS-STREAM 8 ON A QEMU/KVM virtual machine. Initially the
reboot went only to a blank display. Editing the grub menu to give a
terminal boot was successful.
Succeeded to get a graphical screen with xinit and a terminal to
explore the options. Was able to install xfce for a
Dario Lesca wrote:
>When I try to install a new VM with virt-manager, (es Rocky Linux 9 or
>Fedora 37 WS) from a verified ISO file, the live setup do not start and
>the installation procedure is blocked before displaying the graphical
>environment.
...
>Is this a know issue?
There is an issue whic
When I try to install a new VM with virt-manager, (es Rocky Linux 9 or
Fedora 37 WS) from a verified ISO file, the live setup do not start and
the installation procedure is blocked before displaying the graphical
environment.
I can only force restart o stop the VM.
This occur only with last kerne
On 10/25/22 14:11, Greg Woods wrote:
A problem you could run into doing this is licensing. WIndows uses a
variety of methods to detect if a valid product key is being run on
multiple machines, which includes some checks on the hardware. Since a
virtual machine is never going to have virtual har
On Tue, Oct 25, 2022 at 3:29 PM ToddAndMargo via users
wrote:
>
> On 10/25/22 07:23, Go Canes wrote:
> > Also, before even starting, you should confirm the target machine has
> > hardware support for virtualization, and that it is enabled.
>
> Oh poop. Did not think of that.Thank you!
You ar
on, Oct 24, 2022 at 9:39 PM ToddAndMargo via users <
users@lists.fedoraproject.org> wrote:
> Hi All,
>
> Is there a way to tape a native Windows hard
> drive and port it to qemu-kvm?
>
>
___
users mailing list -- users@lists.fedora
dual boot. I said yes,
but it is froth with issues.
So I was thinking of porting his Windows to qemu-kvm
if he really wanted Windows. But better yet, just
put in new hard drive and pack up his old drive in
a static bag for safe keeping. He has several
computers, so he can run his windows stuff of
> but it is froth with issues.
>
> So I was thinking of porting his Windows to qemu-kvm
> if he really wanted Windows. But better yet, just
> put in new hard drive and pack up his old drive in
> a static bag for safe keeping. He has several
> computers, so he can run his
On 10/25/22 07:23, Go Canes wrote:
Also, before even starting, you should confirm the target machine has
hardware support for virtualization, and that it is enabled.
Oh poop. Did not think of that.Thank you!
It is an OLD Windows 7 machine. There
would be no support for virtualization.
On 10/25/22 04:56, Sinthia Vicious wrote:
What did you mean by tape a windows hard drive? All you need to do is
make partitions and you can have windows and linux run side by side on
the same drive. There is no need for something as complicated as a
virtual machine. I ran dual boot machines lik
On 10/25/22 03:51, Sam Varshavchik wrote:
Samuel Sieb writes:
On 10/24/22 21:26, ToddAndMargo via users wrote:
On 10/24/22 21:09, Slade Watkins via users wrote:
On 10/24/22 11:38 PM, ToddAndMargo via users wrote:
Is there a way to tape a native Windows hard
drive and port it to qemu-kvm
1 - 100 of 677 matches
Mail list logo
