Virt-manager LibVirt error in kvm-qemu.sh #2322
Comments
|
and yes I read:
|
|
Run --issues there is msg about this specific error
El mié, 18 sept 2024, 17:20, xx0red ***@***.***> escribió:
… and yes I read:
Important
:
It is important to assert everything works as expected before moving
forward. The vast majority of errors at this point can be solved by
reinstalling the specific component with kvm-qemu.sh
<https://github.com/kevoreilly/CAPEv2/blob/master/installer/kvm-qemu.sh>.
For example, the error below was raised when trying to open virt-manager
but libvirt installation was corrupted for some reason. Reinstalling
libvirt with the script solved the issue.
—
Reply to this email directly, view it on GitHub
<#2322 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOFH32VT3LGJ5U3WPMZETDZXGK2LAVCNFSM6AAAAABON6D54SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJYG43DKNZSGE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
it just says to run ./kvm-qemu.sh libvirt which I've already done as stated |
|
oh it was bigger previously :D basically some problem here but no logs so i can't help https://github.com/kevoreilly/CAPEv2/blob/master/installer/kvm-qemu.sh#L691-L730 |
|
not sure which logs you need, I didn't see any errors from what I saw but maybe I overlooked.. |
|
they looks fine, idk what is wrong, but i guess some lib wasn't properly linked |
|
Well I’ve reinstalled fresh twice now and still no luck.
…On Wed, Sep 18, 2024 at 2:18 PM doomedraven ***@***.***> wrote:
they looks fine, idk what is wrong, but i guess some lib wasn't properly
linked
—
Reply to this email directly, view it on GitHub
<#2322 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARKCO3WYK62QSHGVULLGHK3ZXHGY5AVCNFSM6AAAAABON6D54SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJZGIZDSOJVGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I really tried to reproduce your error but didn't succeed. Just did what you mentioned here on 2 different systems: Maybe it's a more general underlying failure here. Not sure if this failure appears due to lack of virtualization support but it seems your system did not support virtualization as you can see in your logs: |
|
Thanks Claudio, no, that error is due to incorrectly linked dependency, but I can't reproduce it, but I had it in past too |
|
Hmm what to do lol
…On Thu, Sep 19, 2024 at 2:34 AM doomedraven ***@***.***> wrote:
Thanks Claudio, no, that error is due to incorrectly linked dependency,
but I can't reproduce it, but I had it in past too
—
Reply to this email directly, view it on GitHub
<#2322 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARKCO3V4W7DIWGV4NGWKRO3ZXJ5BVAVCNFSM6AAAAABON6D54SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRQGIYTEOJVGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I've followed the documentation to a T, using VMware Ubuntu 22.04, changed WOOT to 'CORE', rebooted as necessary. Don't know what I'm doing wrong |
|
It doesn't show in the .log file but in the terminal I do see this warning, not sure if relevant? |
|
Yes that one is exactly which says what is wrong |
|
Do you have a fix? |
|
No, bcz it works for me
El jue, 19 sept 2024, 23:15, xx0red ***@***.***> escribió:
… Do you have a fix?
—
Reply to this email directly, view it on GitHub
<#2322 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOFH335T2J5UYC5FWD5GD3ZXM5HNAVCNFSM6AAAAABON6D54SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRSGIYTCNZVHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hmm VMware? So your Ubuntu is in a vm? What about your windows vms... don't say nested! |
|
It is indeed nested, I believe the problem was that the VM was not setup for virtualization. Ideally I'd like to just deploy a second Windows VM and use that instead of being nested, but I'm unsure how atm. |
|
Well doomed and I don't always agree when it comes to this issue, but I think it's a terrible idea and something which you probably should have mentioned in the beginning. The only positive argument for nesting is that it makes the job of installing cape easier somehow for new users - but it comes at a very great price in terms of malware compatibility - to have two distinct hypervisors as well as an extra layer of virtualisation significantly multiplies the chances of samples not running due to vm detection/timing issues. Also issues like this with virtualisation features not being present in the nested hypervisor are to be expected. It is for this reason that I wrote a machinery module for VMware workstation, to complement that for ESXi so all VMware platforms are covered for non-nested use. But ultimately I still recommend ditching VMware completely as it's not good for malware research for reasons mentioned above, and is one of many reasons we recommend KVM above all else. |
|
Well nested not related to the issue, the thing is that till next deploy of
my server and if it fail I won't investigate that, as if I can't reproduce
it I can't fix it, I did deployment last week without issues
El lun, 23 sept 2024, 17:00, kevoreilly ***@***.***> escribió:
… Well doomed and I don't always agree when it comes to this issue, but I
think it's a terrible idea and something which you probably should have
mentioned in the beginning.
The only positive argument for nesting is that it makes the job of
installing cape easier somehow for new users - but it comes at a very great
price in terms of malware compatibility - to have two distinct hypervisors
as well as an extra layer of virtualisation significantly multiplies the
chances of samples not running due to vm detection/timing issues. Also
issues like this with virtualisation features not being present in the
nested hypervisor are to be expected.
It is for this reason that I wrote a machinery modules for VMware
workstation, to complement that for ESXi so all VMware platforms are
covered for non-nested use. But ultimately I still recommend ditching
VMware completely as it's not good for malware research for reasons
mentioned above, and is one of many reasons we recommend KVM above all else.
—
Reply to this email directly, view it on GitHub
<#2322 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOFH344XMUYAB4Z3WF6X6DZYAUJLAVCNFSM6AAAAABON6D54SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRYGU2TANZQGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
About accounts on capesandbox.com
This is open source and you are getting free support so be friendly!
Prerequisites
Please answer the following questions for yourself before submitting an issue.
Expected Behavior
Install kvm-qemu via installation script and install virt-manager
Current Behavior
after running kvm-qemu.sh all {user} and rebooting and running kvm-qemu.sh virt-manager {user} and rebooting again. I attempt to open virt-manager and get the error Namespace LibVirtGlib not available.
Failure Information (for bugs)
Getting this exact error
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
Context
Ubuntu 22.04.x, latest CAPEv2 versions.
The text was updated successfully, but these errors were encountered: