On Sun, 16 Feb 2025 at 07:12, wrote:
> On Sat, Feb 15, 2025 at 06:10:35PM -0500, Stefan Monnier wrote:
> > > Sorry for any inconvenience. Calling an LVM volume group kvm is
> > > a really stupid idea.
> > >
> > > This creates a
> > > /dev/kvm so kvm cannot work.
> > Oh, that was clever!
> >
> >
On Sat, Feb 15, 2025 at 06:10:35PM -0500, Stefan Monnier wrote:
> > Sorry for any inconvenience. Calling an LVM volume group kvm is
> > a really stupid idea.
> >
> > This creates a
> > /dev/kvm so kvm cannot work.
>
> Oh, that was clever!
>
> I recently started preferring `/dev/mapper/-` over th
> Sorry for any inconvenience. Calling an LVM volume group kvm is
> a really stupid idea.
>
> This creates a
> /dev/kvm so kvm cannot work.
Oh, that was clever!
I recently started preferring `/dev/mapper/-` over the
(admittedly) prettier `/dev//`, just because it lets me use TAB
completion when
On Sat, Feb 15, 2025 at 08:30:40PM +0100, basti wrote:
> Sorry for any inconvenience. Calling an LVM volume group kvm is a really
> stupid idea.
>
> This creates a
> /dev/kvm so kvm cannot work.
>
Today I learned something useful after using kvm for many years.
It's obvious *now* - congratulatio
No problem. I am learning new things about VMs. Tried various setups
over the years and chose libvirt + qemu as my favorite, assuming all VMs
take a noticable performance hit over running on bare hardware. Your
answer to my suggestion prompted me to research kvm. This is an exiting
new discover
Sorry for any inconvenience. Calling an LVM volume group kvm is a really
stupid idea.
This creates a
/dev/kvm so kvm cannot work.
Am 15.02.25 um 19:39 schrieb basti:
first of all i try to start an existing one -> no kvm/hvm
create a new one will be run in qemu not kvm
Am 15.02.25 um 19:11 sch
first of all i try to start an existing one -> no kvm/hvm
create a new one will be run in qemu not kvm
Am 15.02.25 um 19:11 schrieb Titus Newswanger:
Hi,
Do any VM's run, or are you trying to start a prexisting VM that used to
work? In that case maybe trying to install a new vm would isolate
Hi,
Do any VM's run, or are you trying to start a prexisting VM that used to
work? In that case maybe trying to install a new vm would isolate
whether the problem is with the host or not.
On 2/15/25 11:42, basti wrote:
Hello George,
mostly all have been done.
But nothing solves the Problem
Hello George,
mostly all have been done.
But nothing solves the Problem.
- vmx is seen in lscpu
- user was added to libvirt group
- kvm modules are load
it seem's there is a problem with the hardware, or somthing has chanced
within a a new installed vs. a long running system (since debian 8 o
On Saturday, 15-02-2025 at 02:51 basti wrote:
> Hello I try to install some KVM machines on a i5-4590.
>
> virt-manger say Warning: KVM is not available.
>
> joournal looks like:
>
> Feb 14 16:43:06 kvm libvirtd[563]: Unable to create KVM VM for TSC
> probing: Inappropriate ioctl for device
>
On Fri, Feb 14, 2025 at 04:51:47PM +0100, basti wrote:
virt-manger say Warning: KVM is not available.
try
dmesg | grep -i kvm
You may see a message about kvm failing to activate, which is often
caused by a bios setting disabling the virtualization extensions. If
there's nothing at all, che
Hello I try to install some KVM machines on a i5-4590.
virt-manger say Warning: KVM is not available.
joournal looks like:
Feb 14 16:43:06 kvm libvirtd[563]: Unable to create KVM VM for TSC
probing: Inappropriate ioctl for device
But kvm modules are load:
root@kvm:~# lsmod | grep kvm
kvm_i
12 matches
Mail list logo
