search for: 15067

...6.10 host to kernel-2.6.32-754.el6.x86_64 fixes the >> problem. >> >> Screendump of the panic is attached, not very helpful I guess. > > I didn't know attachments are stripped by the list. > > Here is the bugreport: > > https://bugs.centos.org/view.php?id=15067 > > My feeling is that the recent Intel fixes/workarounds have broken it here > for AMD systems :( > I had to set my CPU type to opteron_g3 instead of opteron_g5 for some machines on an AMD server. -------------- next part -------------- A non-text attachment was scrubbed... Name: s...

...wimming upstream: >> >> Does some one have problems related to KVM with >> kernel-2.6.32-754.3.5.el6.x86_64 ?? > > Is there any chance that this is related? Could you try downgrading > qemu-img/qemu-kvm and see if it helps? > > https://bugs.centos.org/view.php?id=15067 > Thanks to pointing to that bug report. I downgraded from qemu-kvm-0.12.1.2-2.506.el6_10.1.x86_64 qemu-img-0.12.1.2-2.506.el6_10.1.x86_64 to qemu-img-0.12.1.2-2.503.el6_9.6.x86_64 qemu-kvm-0.12.1.2-2.503.el6_9.6.x86_64 and booted into kernel-2.6.32-754.3.5.el6.x86_64 unfortunately...

Hi, I have AMD servers running CentOS 6.10 as KVM host and on it guests running CentOS 7.5. Since the latest kernel update on CentOS 6.10, kernel-2.6.32-754.2.1.el6.x86_64, I can't boot the CentOS 7.5 guests with kernel-3.10.0-862.6.3.el7.x86_64 anymore. Reverting CentOS 6.10 host to kernel-2.6.32-754.el6.x86_64 fixes the problem. Screendump of the panic is attached, not very helpful I

...ne have problems related to KVM with >>>> kernel-2.6.32-754.3.5.el6.x86_64 ?? >>> >>> Is there any chance that this is related? Could you try downgrading >>> qemu-img/qemu-kvm and see if it helps? >>> >>> https://bugs.centos.org/view.php?id=15067 >>> >> >> Thanks to pointing to that bug report. >> >> I downgraded from >> >> qemu-kvm-0.12.1.2-2.506.el6_10.1.x86_64 >> qemu-img-0.12.1.2-2.506.el6_10.1.x86_64 >> >> to >> >> qemu-img-0.12.1.2-2.503.el6_9.6.x86_64 &g...

...in src make[2]: Entering directory '/root/libvirt/build/src' GEN access/org.libvirt.api.policy /bin/sh: access/org.libvirt.api.policy: No such file or directory GEN access/viraccessapicheck.h /bin/sh: access/viraccessapicheck.h: No such file or directory make[2]: *** [Makefile:15067: access/viraccessapicheck.h] Error 1 make[2]: Leaving directory '/root/libvirt/build/src' make[1]: *** [Makefile:1957: all-recursive] Error 1 make[1]: Leaving directory '/root/libvirt/build' make: *** [Makefile:1850: all] Error 2 -- Best regards, ----------------------------------...

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

...x86_64 anymore. > > Reverting CentOS 6.10 host to kernel-2.6.32-754.el6.x86_64 fixes the > problem. > > Screendump of the panic is attached, not very helpful I guess. I didn't know attachments are stripped by the list. Here is the bugreport: https://bugs.centos.org/view.php?id=15067 My feeling is that the recent Intel fixes/workarounds have broken it here for AMD systems :( Regards, Simon

...l6.x86_64 fixes the >>> problem. >>> >>> Screendump of the panic is attached, not very helpful I guess. >> >> I didn't know attachments are stripped by the list. >> >> Here is the bugreport: >> >> https://bugs.centos.org/view.php?id=15067 >> >> My feeling is that the recent Intel fixes/workarounds have broken it here >> for AMD systems :( >> > > I had to set my CPU type to opteron_g3 instead of opteron_g5 for some > machines on an AMD server. This was the bug I hit ... not your scenario .. but who...

...lines in the changelog.diff. Before swimming upstream: > > Does some one have problems related to KVM with > kernel-2.6.32-754.3.5.el6.x86_64 ?? Is there any chance that this is related? Could you try downgrading qemu-img/qemu-kvm and see if it helps? https://bugs.centos.org/view.php?id=15067 Regards, Simon

...; >>> Does some one have problems related to KVM with >>> kernel-2.6.32-754.3.5.el6.x86_64 ?? >> >> Is there any chance that this is related? Could you try downgrading >> qemu-img/qemu-kvm and see if it helps? >> >> https://bugs.centos.org/view.php?id=15067 >> > > Thanks to pointing to that bug report. > > I downgraded from > > qemu-kvm-0.12.1.2-2.506.el6_10.1.x86_64 > qemu-img-0.12.1.2-2.506.el6_10.1.x86_64 > > to > > qemu-img-0.12.1.2-2.503.el6_9.6.x86_64 > qemu-kvm-0.12.1.2-2.503.el6_9.6.x86_64 > > an...

Hi, well, how do i replace an element with rubyful_soup ?? I tried soup = BeautifulSoup.new(input) elemnt = soup.find(''quote'') elemnt = tag(''<div></div>'') elemnt = ''<div></div>'' elemnt.replaceWith(''<div></div>'') elemnt = BeautifulSoup.new(''<div></div>'') elemnt

...directory '/root/libvirt/build/src' >   GEN      access/org.libvirt.api.policy > /bin/sh: access/org.libvirt.api.policy: No such file or directory >   GEN      access/viraccessapicheck.h > /bin/sh: access/viraccessapicheck.h: No such file or directory > make[2]: *** [Makefile:15067: access/viraccessapicheck.h] Error 1 > make[2]: Leaving directory '/root/libvirt/build/src' > make[1]: *** [Makefile:1957: all-recursive] Error 1 > make[1]: Leaving directory '/root/libvirt/build' > make: *** [Makefile:1850: all] Error 2 > I reproduced on Fedora too...