PDA

View Full Version : LEAP 15.4 Error de QEMU despues de update de hoy 23/07



dipra65
23-Jul-2022, 20:44
hola a todos, hoy me la pasé en la PC, para poder recuperar la funcionalidad de sistema.
Hace unos días pasé de la versión 15.3 a la 15.4; hasta aquí nada de problemas.
Todo SW funcionaba bien, aunque noté que con el cambiar a 15.4, cuando voy a arrancar una maquina virtual, la conexión de la interfase gráfica es mucho mas lenta; una vez que se conecta, la maquina virtual corre normal.
Ahora bien, hoy hice unas actualizaciones de sistema sin ninguna notifica de error; todo parecía bien.
Al momento que, arranqué una maquina virtual, la computadora andaba en kernel panic, y no respondía a ningún mando,bajo ninguna circunstancia.
Intenté arrancar otra maquina virtual y lo mismo, intenté modificando varios parámetros de sistema de la maquina virtual, sin suerte.
La sola maquina virtual que me arrancaba sin problema era una con OS guest WinXP.
Después de tanto probar, no llegué a nada y después de 4h de intentos, me rendí y active snapper.
Después de revertir a antes de las actualizaciones de hoy, todo regresó a la normalidad.
alguien tiene idea de lo que pueda ser?
El log no ayuda a nada ya que se traba el kernel.
Ya que soy nuevo en esto, alguien me puede indicar si hay manera de señalar el evento a OpenSUSE?

bknaack483
25-Jul-2022, 09:53
I'm experiencing a similar situation with running a virtual machine under qemu. My Leap and MicroOS virtual machines run just fine. However, my Windows 7 virtual machine would freeze the host. The virtual machine was working after the initial upgrade to 15.4, but quit sometime after that; I don't run it all the time. Thinking the virtual machine was somehow corrupted, I dumped it and tried to create a new machine. The install runs to the point where the installation screens should start, and then freezes the host.

Need a suggestion where to look.

mikrios
25-Jul-2022, 10:54
Hola:

Por lo general, suelen funcionar bien; pero en mi caso uso Virtual Box, cada sistema virtual depende de un kernel y se compila con el mismo, si hay actualizaciones tienen que ir de acorde con ellas (sobre todo si depende del kernel o sus módulos ) .

S i no es así da problemas, o bien no funciona o bien lo hace mal; y en eso creo que pudiese ser la causa de alguna actualización de seguridad del kernel o algunos de sus elementos.

Para ello se ha hecho lo que se conoce como dkms, se instala y se activa en gestión de servicios de yast, dkms se encarga que cuando se haga un cambio en el kernel, de buscar los elementos equivalentes, para que la vm (maquina virtual) siga funcionando con el nuevo kernel .

También al instalar una vm, hacerlo acorde a su numero de núcleos, no asignarle uno o 2 por que ira mas lento, si tiene 6 o 8 darle 3 o 4 ; mis experiencias con lo del cambio de kernel, sin dkms, han sido que dejan de funcionar o lo hacen mal .

Ver en ( /var/log/zypp/) sudo cat/var/log/zypp/history o bien en el historia del instalador de soft de yast, si hubo algún cambio en el kernel cuando empezó el fallo .

También por si lo hay? , mirar si hay algún log de la vm (maquina virtual )

Saludos cordiales .

Post data. las vm se tiene que instalar con dkms activo, para que se genere el correspondiente directorio, también dkms, sirve para adaptar otros programas a los cambios del kernel (eso si dkms es compatible con ello) .

Hello:

They usually work fine; but in my case I use Virtual Box, each virtual system depends on a kernel and is compiled with it, if there are updates they have to go according to them (especially if it depends on the kernel or its modules).

If this is not the case, it causes problems, either it does not work or it does it wrong; and in that I think it could be the cause of some kernel security update or some of its elements.

For this, what is known as dkms has been done, it is installed and activated in yast service management, dkms takes care that when a change is made in the kernel, to search for the equivalent elements, so that the vm (virtual machine ) keep working with the new kernel .

Also when installing a vm, do it according to its number of cores, do not assign one or 2 because it will go slower, if it has 6 or 8 give it 3 or 4; my experiences with the kernel change, without dkms, have been that they stop working or do it wrong.

Look in (/var/log/zypp/) sudo cat/var/log/zypp/history or in the history of the yast soft installer, if there were any changes in the kernel when the failure started.

Also if there is? , look if there is any log of the vm (virtual machine)

Best regards .

Postscript. The vm must be installed with dkms active, so that the corresponding directory is generated, also dkms, it is used to adapt other programs to changes in the kernel (if dkms is compatible with it).

Excuse me if my translation generates any words that could offend or annoy, it is not my intention, mine is to answer as humble and simple as possible, but sometimes the meaning of the translator may change things, if so, I apologize . For the rest, thank you very much and best regards.

Edito:
Si esa vm viene ya compilada con un determinado kernel, y hay un cambio en el mismo, hay que esperar a que se actualice de nuevo esa vm al nuevo kernel (o compilarla uno mismo) .

edit: If that vm is already compiled with a certain kernel, and there is a change in it, you have to wait for that vm to be updated again to the new kernel (or compile it yourself).

dipra65
25-Jul-2022, 10:54
I'm experiencing a similar situation with running a virtual machine under qemu. My Leap and MicroOS virtual machines run just fine. However, my Windows 7 virtual machine would freeze the host. The virtual machine was working after the initial upgrade to 15.4, but quit sometime after that; I don't run it all the time. Thinking the virtual machine was somehow corrupted, I dumped it and tried to create a new machine. The install runs to the point where the installation screens should start, and then freezes the host.

Need a suggestion where to look.

Hy bknaack483, I don't know if you got all I wrote so here you go.
First I have to say that I'm experiencing problems with Win 7 (64bit) too, while with WinXP (32bit) everything is working, so maybe is somehow related.
I have spent a long time trying to figure out what my problem was, with no luck.
Considered that my problem started after an update, where it was involved the kernel, virtual machine manager, and other safety features, I finally decided to rollback installation.
In order to do that I used Snapper and once everything returned as before the update, all VMs were working fine.
Is not easy to have a kernel panic so I think there is a bug in the new kernel version or the virtual machine manager update.
Everything else is working just fine, so if you need the VMs, like me, you should better rollback, while OpenSUSE fix the bug, otherwise there is no reason to do that.