Re: virt-install returns error
On Tue, Sep 1, 2020 at 11:16 PM Kenneth Parker <sea7kenp@gmail.com> wrote:
>
>
>
> On Tue, Sep 1, 2020 at 10:58 PM Charles Zeitler <cfzeitler@gmail.com> wrote:
>>
>> i get:
>>
>> debian@debian:~$ su -c 'virt-install --name test --cdrom
>> /home/debian/mnt/sdi/Downloads/0_distros/windows/Win10* --memory 4000
>> --disk size=5 --cpu=host'
>> Password:
>>
>> Starting install...
>> Allocating 'test.qcow2'
>> | 5.0 GB 00:00:00
>> ERROR internal error: process exited while connecting to monitor:
>> nput0,bus=usb.0,port=1 -spice
>> port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on
>> -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2
>> -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
>> hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev
>> spicevmc,id=charredir0,name=usbredir -device
>> usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev
>> spicevmc,id=charredir1,name=usbredir -device
>> usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device
>> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on
>> ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
>> failed to initialize KVM: Device or resource busy
>> Removing disk 'test.qcow2'
>>
>> also from dmesg:
>>
>>
>>
>> [27901.188584] kvm: enabling virtualization on CPU1 failed
>> [27901.188589] kvm: enabling virtualization on CPU2 failed
>> [27901.188601] kvm: enabling virtualization on CPU0 failed
>> [27901.501308] audit: type=1400 audit(1599004754.100:55):
>> apparmor="STATUS" operation="profile_load" profile="unconfined"
>> name="libvirt-845413b9-8775-499f-bfaa-bf583e4040ae" pid=11035
>> comm="apparmor_parser"
>> [27901.570108] virbr0: port 2(vnet0) entered blocking state
>> [27901.570114] virbr0: port 2(vnet0) entered disabled state
>> [27901.570271] device vnet0 entered promiscuous mode
>> [27901.590262] virbr0: port 2(vnet0) entered blocking state
>> [27901.590268] virbr0: port 2(vnet0) entered listening state
>> [27901.844514] audit: type=1400 audit(1599004754.448:56):
>> apparmor="STATUS" operation="profile_replace" info="same as current
>> profile, skipping" profile="unconfined"
>> name="libvirt-845413b9-8775-499f-bfaa-bf583e4040ae" pid=11059
>> comm="apparmor_parser"
>> [27901.892175] audit: type=1400 audit(1599004754.496:57):
>> apparmor="DENIED" operation="open"
>> profile="libvirt-845413b9-8775-499f-bfaa-bf583e4040ae"
>> name="/sys/devices/system/node/" pid=11119 comm="qemu-system-x86"
>> requested_mask="r" denied_mask="r" fsuid=64055 ouid=0
>> [27901.892187] audit: type=1400 audit(1599004754.496:58):
>> apparmor="DENIED" operation="open"
>> profile="libvirt-845413b9-8775-499f-bfaa-bf583e4040ae"
>> name="/sys/devices/system/cpu/" pid=11119 comm="qemu-system-x86"
>> requested_mask="r" denied_mask="r" fsuid=64055 ouid=0
>> [27901.895201] kvm: enabling virtualization on CPU0 failed
>> [27901.895205] kvm: enabling virtualization on CPU2 failed
>> [27901.895212] kvm: enabling virtualization on CPU1 failed
>> [27901.899325] virbr0: port 2(vnet0) entered disabled state
>> [27901.904663] device vnet0 left promiscuous mode
>> [27901.904666] virbr0: port 2(vnet0) entered disabled state
>> [27902.165074] audit: type=1400 audit(1599004754.768:59):
>> apparmor="STATUS" operation="profile_remove" profile="unconfined"
>> name="libvirt-845413b9-8775-499f-bfaa-bf583e4040ae" pid=11145
>> comm="apparmor_parser"
>
>
> Looks like your BIOS doesn't support Virtualization.
>
>> any hints/tips?
>
>
> I had to enter my computer's BIOS and tell it that Virtualization is allowed. (KVM requires Hardware Virtualization. Qemu by itself doesn't, just in case you have a CPU that doesn't support this).
>
bios claims it's enabled
cpu=amd phenom ii
>> charkes zeitler
>> --
>> The Perfect Is The Enemy Of
>> The Good Enough
>
>
> Kenneth Parker
--
The Perfect Is The Enemy Of
The Good Enough
Reply to: