<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=5128&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / Chimaera and VirtualBox after kernel update]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=5128</link>
		<description><![CDATA[The most recent posts in Chimaera and VirtualBox after kernel update.]]></description>
		<lastBuildDate>Wed, 20 Jul 2022 17:53:12 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: Chimaera and VirtualBox after kernel update]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=36707#p36707</link>
			<description><![CDATA[<p>VBox 6.1.36 has been released. Builds kernel modules against 5.18 kernel now.</p>]]></description>
			<author><![CDATA[dummy@example.com (rolfie)]]></author>
			<pubDate>Wed, 20 Jul 2022 17:53:12 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=36707#p36707</guid>
		</item>
		<item>
			<title><![CDATA[Re: Chimaera and VirtualBox after kernel update]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=36676#p36676</link>
			<description><![CDATA[<p>same form me, using old kernel all works correctly</p>]]></description>
			<author><![CDATA[dummy@example.com (nomorelogic)]]></author>
			<pubDate>Mon, 18 Jul 2022 08:38:51 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=36676#p36676</guid>
		</item>
		<item>
			<title><![CDATA[Re: Chimaera and VirtualBox after kernel update]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=36645#p36645</link>
			<description><![CDATA[<div class="quotebox"><cite>PengouinPdt wrote:</cite><blockquote><div><p>PS: One tips, reboot on oldier kernel… <br />(if available)</p></div></blockquote></div><p>This works. I had the same problem on Beowulf because I use a kernel from backports. After spending a lot of time trying to repair Windows 8.1, I began to suspect that the problem is not in the guest but on the host. I decided to try rebooting with the previous kernel, and when I did the problem was gone.</p>]]></description>
			<author><![CDATA[dummy@example.com (pcalvert)]]></author>
			<pubDate>Sat, 16 Jul 2022 03:54:41 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=36645#p36645</guid>
		</item>
		<item>
			<title><![CDATA[Re: Chimaera and VirtualBox after kernel update]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=36637#p36637</link>
			<description><![CDATA[<p>Hi, all.</p><p>As I wroted on <a href="https://dev1galaxy.org/viewtopic.php?pid=36593#p36593" rel="nofollow">https://dev1galaxy.org/viewtopic.php?pid=36593#p36593</a>, a bug is open because Virtualbox not function correctly on kernel ≥ 5.10 (including 5.18)</p><p>Wait&#039;n see a new version!</p><p>PS: One tips, reboot on oldier kernel… <br />(if available)</p>]]></description>
			<author><![CDATA[dummy@example.com (PengouinPdt)]]></author>
			<pubDate>Fri, 15 Jul 2022 10:37:12 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=36637#p36637</guid>
		</item>
		<item>
			<title><![CDATA[Re: Chimaera and VirtualBox after kernel update]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=36636#p36636</link>
			<description><![CDATA[<p>i downloaded a .deb package<br />virtualbox-6.1_6.1.30-148432~Debian~bullseye_amd64.deb</p><p>in /etc/apt/sources.list<br />deb [arch=amd64] <a href="https://download.virtualbox.org/virtualbox/debian" rel="nofollow">https://download.virtualbox.org/virtualbox/debian</a> bullseye contrib</p><p>now I&#039;ve Virtualbox is updated to 6.1.34 r150636 (Qt5.15.2)</p><p>I can say I had no problem until this kernel update</p>]]></description>
			<author><![CDATA[dummy@example.com (nomorelogic)]]></author>
			<pubDate>Fri, 15 Jul 2022 07:14:32 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=36636#p36636</guid>
		</item>
		<item>
			<title><![CDATA[Re: Chimaera and VirtualBox after kernel update]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=36632#p36632</link>
			<description><![CDATA[<div class="quotebox"><cite>nomorelogic wrote:</cite><blockquote><div><p>I installed some time ago Virtualbox on my Devuan Chimaera</p></div></blockquote></div><p>How did you do that? VirtualBox is of insufficient quality to be included in the stable release.</p><p><a href="https://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&amp;q=virtualbox&amp;x=submit" rel="nofollow">https://pkginfo.devuan.org/cgi-bin/poli … x&amp;x=submit</a></p>]]></description>
			<author><![CDATA[dummy@example.com (Head_on_a_Stick)]]></author>
			<pubDate>Thu, 14 Jul 2022 18:24:18 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=36632#p36632</guid>
		</item>
		<item>
			<title><![CDATA[Chimaera and VirtualBox after kernel update]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=36624#p36624</link>
			<description><![CDATA[<p>hi all<br />I need some help using virtualbox.</p><p>I installed some time ago Virtualbox on my Devuan Chimaera, kernel was 5.10.0-14.<br />I can use VirtualBox correctly without any trouble with this system</p><p>Recently I updated the kernel</p><div class="codebox"><pre><code>$ uname -a
Linux mapmobile 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux</code></pre></div><p>Now all my VMs can start running but I get some malfunctions on my VMs (in example, inside VM Win10: (1) unaspected and frequent reboots and (2) some software like brawe browser close itself while running).</p><p>Fortunately I can still use 5.10.0-14 at boot.</p><p>Any idea to fix this?<br />Thanks in advance.<br />nomorelogic</p>]]></description>
			<author><![CDATA[dummy@example.com (nomorelogic)]]></author>
			<pubDate>Thu, 14 Jul 2022 11:07:05 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=36624#p36624</guid>
		</item>
	</channel>
</rss>
