similar to: Re: virt-v2v stuck EDAC sbridge

On Mon, Sep 11, 2017 at 06:38:14PM +0000, Seth Tanner wrote: > The virt-v2v machine is running inside openstack, so there is nested > virtualization. To the best of my understanding all of the > appropriate flags have been set to support nested virtualization. Ah OK, it's likely to be a bug in nested virt. Unfortunately nested virt is a bit of a minefield, and often has bugs. Also

On Fri, Sep 08, 2017 at 06:33:58PM +0000, Seth Tanner wrote: > [fedora@virt-v2v-fedora ~]$ virt-v2v -ic vpx://AXIA-EFT%5cstanner@192.168.28.9/Axia/galleon.axia-eft.local/?no_verify=1 "Axia-DEV" -o glance -on Axia-DEV Some of the debug info is missing here. Can you run it with ‘-v -x’ added to the virt-v2v the command line. Rich. -- Richard Jones, Virtualization Group, Red Hat

On Wed, Sep 13, 2017 at 02:39:05PM +0000, Seth Tanner wrote: > Rich, > Thank you for your assistance. Switching to bare metal resolved the issues we were having. > > If you want me to continue testing in nested virt, I am happy do so. If not thanks again for the help. Glad it works now. Nested virt testing is useful, but it's not really a virt-v2v or libguestfs concern,

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #8 from Philippe Condé <conde.philippe at skynet.be> --- Hello, I desactivated kscreenlocker which resolve the reactivate problem. But the problem of corrupt screen when starting different programs remains and is worst since the last zypper dup. I found this error still related to nouveau when the two screen got corrupted ov

On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote: >Hi Linus, > >Up to now we see the below boot error/warnings when testing v4.14-rc6. > >They hit the RC release mainly due to various imperfections in 0day's >auto bisection. So I manually list them here and CC the likely easy to >debug ones to the corresponding maintainers in the followup emails. >

On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote: >Hi Linus, > >Up to now we see the below boot error/warnings when testing v4.14-rc6. > >They hit the RC release mainly due to various imperfections in 0day's >auto bisection. So I manually list them here and CC the likely easy to >debug ones to the corresponding maintainers in the followup emails. >

The man page for libguestfs says: export LIBGUESTFS_BACKEND_SETTINGS=force_tcg will force the direct and libvirt backends to use TCG (software emulation) instead of KVM (hardware accelerated virtualization). However, our application has many services (run by different users) which make use of libguestfs tools, and it is painful to have to set this environment variable for each script and

Even though force_tcg works, I intend not to run it on emulation. Is there way I can run it over kvm? The other observation is, without force_tcg if I use the machine type as *pc-i440fx-2.**1*,accel=kvm it works fine. The default machine type for my host *pc-i440fx-2.8, *which seems to crib. On Sat, 24 Mar 2018 at 09:46 Tanmoy Sinha <tanmoy.sinha@gmail.com> wrote: > Yes it works if I

On Fri, Jan 31, 2014 at 04:02:03PM +0200, Rom Freiman wrote: > Hey everybody, > Any news about the topic? I could not find anything relevant yet. Don't know about the kernel bug, but in (very very) recent versions of libguestfs it is now possible to force TCG by doing: export LIBGUESTFS_BACKEND_SETTINGS=force_tcg which should work around this bug. See:

Am 21.01.16 um 17:41 schrieb Jan Beulich: >>>> On 20.01.16 at 16:01, <andreas.pflug at web.de> wrote: >> Initially reported to debian >> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810964), redirected here: >> >> With AMD Opteron 6xxx processors, half of the memory controllers are >> missing from /sys/devices/system/edac/mc >> Checked

I haven't yet done as much experimentation as Andreas Pflug has, but I can confirm I'm also running into this bug with Xen 4.4.1. I've only tried Linux kernel 3.16.43, but as Dom0: EDAC MC: Ver: 3.0.0 AMD64 EDAC driver v3.4.0 EDAC amd64: DRAM ECC enabled. EDAC amd64: NB MCE bank disabled, set MSR 0x0000017b[4] on node 0 to enable. EDAC amd64: ECC disabled in the BIOS or no ECC

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u1 Severity: important I already posted this on the xen-devel-mailinglist but no one seems to have an answer. I'm posting it here because perhaps someone using Debian and Virtualization might have an idea about this? Since Debian 8 I observe that live migrating a PVM on XEN 4.4.1 (also 4.5.1) and Linux Kernel 4.1.0 (also 3.18) requires

What does the following EDAC problem means? The machine is a AMD 64bit box running Centos 5. It looks like some problems aroung AMD DRAM Memory controller. But what does it really mean b/c most of my AMD boxes has these messages in /var/log/messages. Please help. ... Aug 1 23:29:40 ccn128 kernel: EDAC MC: Ver: 2.0.1 Jun 12 2007 Aug 1 23:29:40 ccn128 kernel: EDAC MC0: Giving out device to

In order to support ZFS, we upgraded a backups server with a new, ECC motherboard. We're running CentOS 6 with ZFS on Linux, recently patched. Now, I want to enable EDAC so we can check for memory errors (and maybe PCI errors as well) but so far, repeatedly pounding on the Google hasn't yielded exactly what I need to do to enable EDAC. One howto was covering PCI and edac, but

CentOS Errata and Bugfix Advisory 2014:0768 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0768.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f9238919a8e55753462b1690cc36a16b0a0c29260663dd5fe3e9ee0ae7a187c9 edac-utils-0.9-15.el6.i686.rpm

Yes it works if I use force_tcg env variable On Sat, 24 Mar 2018 at 4:37 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > > On Fri, Mar 23, 2018 at 05:35:38PM +0000, Tanmoy Sinha wrote: > > Thanks. Reading the defect and the associated thread in > > https://bugs.launchpad.net/qemu/+bug/1661386, I enabled performance > > counters in VMWare guest settings. Now the

Hi All, We have installed CentOS 5.3 x86_64 in an HP DL585 server with AMD Opteron 64 bit processor and 16 GB RAM. The kernel version is 2.6.18-128.el5 . Now this has thrown an error message in /var/log/message, Jul 3 21:41:11 db1 kernel: EDAC k8 MC0: general bus error: participating processor(local node origin), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem

After update from centos 6.6 to centos 6.7 and reboot it, I have get a lot of this error into /var/log/messages: > May??3 11:27:20 s-virt kernel: EDAC MC0: CE row 2, channel 1, label > "": (Branch=0 DRAM-Bank=2 RDWR=Read RAS=6093 CAS=896, CE Err=0x10000 > (Correctable Patrol Data ECC)) > May??3 11:27:21 s-virt kernel: EDAC MC0: CE row 2, channel 1, label > "":

On Mon, May 15, 2017 at 02:02:53AM -0600, Jan Beulich wrote: > >>> On 14.05.17 at 00:36, <ehem+debian at m5p.com> wrote: > > I haven't yet done as much experimentation as Andreas Pflug has, but I > > can confirm I'm also running into this bug with Xen 4.4.1. > > > > I've only tried Linux kernel 3.16.43, but as Dom0: > > > > EDAC

Hello, I upgraded to CentOS 5.1 and everything went smoothly (Thanks for the awesome work!). But after rebooting, I get the following error: EDAC MC: Ver: 2.0.1 Nov 30 2007 EDAC e7xxx: error reporting device not found:vendor 8086 device 0x2541 (broken BIOS?) I found http://edacbugs.buttersideup.com/show_bug.cgi?id=21 with google but no solution. Is it safe to ignore the error or remove