search for: msg00385

Hi, Have you seen this: http://gcc.gnu.org/ml/gcc/2008-06/msg00385.html There is a new branch for converting gcc to C++. Best regards, --Edwin

On Thu, 19 Jun 2008 09:44:46 +0300, Török Edwin wrote: > Hi, > > Have you seen this: http://gcc.gnu.org/ml/gcc/2008-06/msg00385.html > There is a new branch for converting gcc to C++. > > Best regards, > --Edwin The sad thing is that they seem to be replacing one unsafe language with another, presumably with enormous effort. The only hopeful sign in that thread is the proposal for using Cyclone instead, st...

On Wed, Jul 2, 2008 at 2:13 PM, Hendrik Boom <hendrik at topoi.pooq.com> wrote: > On Thu, 19 Jun 2008 09:44:46 +0300, Török Edwin wrote: > >> Hi, >> >> Have you seen this: http://gcc.gnu.org/ml/gcc/2008-06/msg00385.html >> There is a new branch for converting gcc to C++. >> >> Best regards, >> --Edwin > > The sad thing is that they seem to be replacing one unsafe language with > another, presumably with enormous effort. > > The only hopeful sign in that thread is the pro...

...est what can we do. I have found below links on google while checking for the vcpu pid's error https://www.redhat.com/archives/libvir-list/2013-June/msg00214.htm<https://www.redhat.com/archives/libvir-list/2013-June/msg00214.html> <https://www.redhat.com/archives/libvir-list/2013-June/msg00385.html> https://www.redhat.com/archives/libvir-list/2012-August/msg01405.html https://www.redhat.com/archives/libvir-list/2012-August/msg01413.html Can you let us know if any of the above patches fix our issue. Thanks Abhinay On Thu, Aug 22, 2013 at 3:19 PM, Daniel P. Berrange <berrange@redh...

I have some Xen systems running Xen-4.1.1, dom0 linux-2.6.38 patched (it''s gentoo''s xen-sources) and domUs running linux-3.0.4 (vanilla sources from kernel.org). Block devices are phy on LVM2 volumes on DRBD-8.3.9 devices. Not immediately after boot, but after some I/O load on the disks I start seeing these in the domUs: blkfront: barrier: empty write xvdb1 op failed blkfront:

Hi Daniel, Thanks for your immidiate reply. The starting of virtual guest was ok on our machine. We are facing this issue while executing the "cpu-stats <domain name>" command. I have collected the debug logs as you suggested and attaching the same. <<libvirt_testing_starting_VG.log >> --> Log collected while starting the virtual guest