Hi Hans,
On Donnerstag, 1. Juni 2017 15:59:10 CEST Hans de Goede wrote:
> Hi,
>
> On 01-06-17 15:42, Frank Mehnert wrote:
> > Hi Hans,
> >
> > On Donnerstag, 1. Juni 2017 14:22:29 CEST Hans de Goede wrote:
> >>> Again, this is not a VirtualBox bug although this panic will probably not
> >>>
Hi,
On 01-06-17 15:42, Frank Mehnert wrote:
Hi Hans,
On Donnerstag, 1. Juni 2017 14:22:29 CEST Hans de Goede wrote:
Again, this is not a VirtualBox bug although this panic will probably not
happen on real hardware.
[...]
No as for the disagree-ing with this not being a VirtualBox bug,
even
On Dienstag, 30. Mai 2017 09:14:31 CEST Hans de Goede wrote:
> On 29-05-17 17:28, Frank Mehnert wrote:
> > On Montag, 29. Mai 2017 16:58:28 CEST Frank Mehnert wrote:
> >> Hi Hans,
> >>
> >> On Montag, 29. Mai 2017 16:22:09 CEST Hans de Goede wrote:
> >>> [...]
> >>>
> >>> Ok, can you try install a
On Montag, 29. Mai 2017 16:58:28 CEST Frank Mehnert wrote:
> Hi Hans,
>
> On Montag, 29. Mai 2017 16:22:09 CEST Hans de Goede wrote:
> > [...]
> >
> > Ok, can you try install a 4.12 kernel, e.g.:
> >
> > https://koji.fedoraproject.org/koji/buildinfo?buildID=892258
> >
> > Download
Hi Hans,
On Montag, 29. Mai 2017 16:22:09 CEST Hans de Goede wrote:
> [...]
>
> Ok, can you try install a 4.12 kernel, e.g.:
>
> https://koji.fedoraproject.org/koji/buildinfo?buildID=892258
>
> Download kernel-core... and kernel-modules... and then do
> rpm -ivh kernel*.rpm
> as root from a dir
Hi,
On 29-05-17 15:12, Frank Mehnert wrote:
Hi Hans,
On Montag, 29. Mai 2017 13:27:33 CEST Hans de Goede wrote:
On 29-05-17 12:23, Hans de Goede wrote:
On 25-05-17 11:57, Hans de Goede wrote:
On 24-05-17 18:13, Michael Thayer wrote:
24.05.2017 16:02, Michael Thayer wrote:
24.05.2017
Hi Hans,
On Montag, 29. Mai 2017 13:27:33 CEST Hans de Goede wrote:
> On 29-05-17 12:23, Hans de Goede wrote:
> > On 25-05-17 11:57, Hans de Goede wrote:
> >> On 24-05-17 18:13, Michael Thayer wrote:
> >>> 24.05.2017 16:02, Michael Thayer wrote:
> 24.05.2017 15:16, Hans de Goede wrote:
>
Hi,
On 29-05-17 12:23, Hans de Goede wrote:
Hi,
On 25-05-17 11:57, Hans de Goede wrote:
Hi,
On 24-05-17 18:13, Michael Thayer wrote:
24.05.2017 16:02, Michael Thayer wrote:
24.05.2017 15:16, Hans de Goede wrote:
[...]
I cannot get a Fedora 26 guest to boot with either distro-provided or
Hi,
On 25-05-17 11:57, Hans de Goede wrote:
Hi,
On 24-05-17 18:13, Michael Thayer wrote:
24.05.2017 16:02, Michael Thayer wrote:
24.05.2017 15:16, Hans de Goede wrote:
[...]
I cannot get a Fedora 26 guest to boot with either distro-provided or
self-built 4.12-rc# kernels, the
Hi,
On 24-05-17 16:02, Michael Thayer wrote:
24.05.2017 15:16, Hans de Goede wrote:
[...]
I cannot get a Fedora 26 guest to boot with either distro-provided or
self-built 4.12-rc# kernels, the distro-provided 4.11 kernel works fine.
After selecting a 4.12# kernel in the grub menu the vm shows
24.05.2017 15:16, Hans de Goede wrote:
[...]
I cannot get a Fedora 26 guest to boot with either distro-provided or
self-built 4.12-rc# kernels, the distro-provided 4.11 kernel works fine.
After selecting a 4.12# kernel in the grub menu the vm shows an empty
text screen with a cursor in the top
Hi,
I cannot get a Fedora 26 guest to boot with either distro-provided or
self-built 4.12-rc# kernels, the distro-provided 4.11 kernel works fine.
After selecting a 4.12# kernel in the grub menu the vm shows an empty text
screen with a cursor in the top left corner and then just hangs.
12 matches
Mail list logo