doomedraven / Tools

Combination of different utilities, have fun!
MIT License
202 stars 96 forks source link

Creating VM's using virt-manager after running the script is not possible #76

Closed anykeypress closed 3 years ago

anykeypress commented 3 years ago

This is opensource and you getting free support so be friendly!

Prerequisites

Please answer the following questions for yourself before submitting an issue.

Expected Behavior

After executing the kvm-qemu.sh script, creating a Virtual Machine using the virt-manager GUI should work as normal

Current Behavior

When creating a virtual machine, everything works as normal until the machine is to be created. Then an error is thrown as shown in the log / error message below.

Failure Information (for bugs)

Unable to complete install: 'internal error: process exited while connecting to monitor: /usr/bin/qemu-system-x86_64: error while loading shared libraries: libjemalloc.so.2: cannot open shared object file: No such file or directory'

Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createvm.py", line 2001, in _do_async_install installer.start_install(guest, meter=meter) File "/usr/share/virt-manager/virtinst/install/installer.py", line 701, in start_install domain = self._create_guest( File "/usr/share/virt-manager/virtinst/install/installer.py", line 649, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/local/lib/python3.8/dist-packages/libvirt.py", line 4366, in createXML raise libvirtError('virDomainCreateXML() failed') libvirt.libvirtError: internal error: process exited while connecting to monitor: /usr/bin/qemu-system-x86_64: error while loading shared libraries: libjemalloc.so.2: cannot open shared object file: No such file or directory

image

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

  1. Install Ubuntu 20.04
  2. Run the script kvm-qemu.sh
  3. The script appears to run normally
  4. Attempt to create a virtual machine, the error shown in the screen shot is shown. Virtual machine cannot be created.

Context

If installing the KVM packages normally (i.e. without any customization as provided by the script, everyhting works fine) The error occurs regardless if the VHD (qcow2) is present beforehand or created "on the fly". KVM / QEMU was not present on the system prior to executing the script.

Question Answer
OS version Ubuntu 20.04
Software version n/a

Failure Logs

kvm-qemu-install.zip

doomedraven commented 3 years ago

thanks i will try to check this when i will have some time, this is the fun of depend of 3rd part libraries that changes frequently

doomedraven commented 3 years ago

did you try this? https://github.com/jemalloc/jemalloc/issues/1327

anykeypress commented 3 years ago

@doomedraven , you're the man. That seems to have fixed it. Installing to test to the end now.... cheers

doomedraven commented 3 years ago

ok without doing any changes it installs fine it here, check if you have this

 locate libjemalloc
/usr/local/lib/libjemalloc.so.2
anykeypress commented 3 years ago

Hi @doomedraven , yes I do have that lib.... but only after installing the "patch" that you suggested... OT, sorry for asking here, but what Linting extension do you guys use in VS?

doomedraven commented 3 years ago

Weird,but thanks for headups

El sáb., 20 feb. 2021 12:56, Phil Benson notifications@github.com escribió:

Hi @doomedraven https://github.com/doomedraven , yes I do have that lib.... but only after installing the "patch" that you suggested...

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/doomedraven/Tools/issues/76#issuecomment-782614128, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOFH37Z33JDRYA77TAR4W3S76PQFANCNFSM4X5ATGSQ .

doomedraven commented 3 years ago

closing this as can't reproduce, and you solved it, next time please also provide the log of the installation if no issue will be invalid, as if something fail and user not check log he should fix it itself ;)

anykeypress commented 3 years ago

@doomedraven , wasn't the log I provided correct? If not please let me know which one would help, unless you want to keep the issue closed...

doomedraven commented 3 years ago

that is error msg, that is required, but that isn't log from my script that installs jemalloc aka when you run kvm-qemu.sh

anykeypress commented 3 years ago

Your log is probably still on the machine, I haven't removed anything, could you point me in the right direction? (i.e. let me know where the log is/was stored) and I will have another look...

doomedraven commented 3 years ago

It not autocreated, you should run script as - - help says with tee command

El lun., 22 feb. 2021 8:35, Phil Benson notifications@github.com escribió:

Your log is probably still on the machine, I haven't removed anything, could you point me in the right direction? (i.e. let me know where the log is/was stored) and I will have another look...

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/doomedraven/Tools/issues/76#issuecomment-783158623, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOFH36UO5ESOHO6V32GOQTTAICM3ANCNFSM4X5ATGSQ .

anykeypress commented 3 years ago

@doomedraven , sorry... would you like me to run it again on a vm?

doomedraven commented 3 years ago

np, you learning. nah i tried to reproduce it on my dev vm restoring snapshot and it didn't fail so meh don't waste time on this