search for: 1623692

...2.503.el6_9.6.x86_64 and booted into kernel-2.6.32-754.3.5.el6.x86_64 unfortunately no positiv effect. The system/host/workstation crashes/panics immediately after starting a guest system (EL6) with virsh start guest-name. BTW upstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1623692 -- LF

...; unfortunately no positiv effect. >> >> The system/host/workstation crashes/panics immediately after >> starting a guest system (EL6) with virsh start guest-name. >> >> >> BTW upstream bug report: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1623692 > > Unfortunately I only get "You are not authorized to access bug #1623692". > Kernel related bugs seems to get a nonpublic-flag. Free account creation ... -- LF

...l-2.6.32-754.3.5.el6.x86_64 > > unfortunately no positiv effect. > > The system/host/workstation crashes/panics immediately after > starting a guest system (EL6) with virsh start guest-name. > > > BTW upstream bug report: > > https://bugzilla.redhat.com/show_bug.cgi?id=1623692 Unfortunately I only get "You are not authorized to access bug #1623692". Simon

Since the update from kernel-2.6.32-754.2.1.el6.x86_64 to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my KVM guests anymore!? The workstation panics immediately! I would not have expected this behavior now (last phase of OS). It was very robust until now (Optiplex Workstation). I see some KVM related lines in the changelog.diff. Before swimming upstream: Does some one have problems

Am 30.08.2018 um 20:28 schrieb Simon Matter <simon.matter at invoca.ch>: > Am 30.08.2018 um 12:16 schrieb Leon Fauster <leonfauster at googlemail.com>: >> >> BTW upstream bug report: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1623692 > > Well, I have an account and am logged in, still can not see the bug. It seems that the default bugzilla classification doesn't allow bug reports associated with the kernel to get a read status or so ... just to summarize the status briefly: They fortunately can reproduce the prob...