RE: where should I report kvm kernel bug?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: Avi Kivity [mailto:avi@xxxxxxxxxx]
> Sent: Wednesday, January 04, 2012 1:08 AM
> To: Konstantin Ryabitsev
> Cc: Ren, Yongjie; kvm@xxxxxxxxxxxxxxx; ftpadmin
> Subject: Re: where should I report kvm kernel bug?
> 
> On 01/03/2012 06:28 PM, Konstantin Ryabitsev wrote:
> > On Tue, 2012-01-03 at 12:10 +0200, Avi Kivity wrote:
> > > I'm surprised bugzilla.kernel.org isn't responding.  Copying
> > > ftpadmin@xxxxxxxxxx for ETA (though that address isn't responding, either).
> >
> > Hi, Avi and Ren:
> >
> > Unfortunately, we don't currently have an ETA for bringing up
> > bugzilla.kernel.org. We are still awaiting some hardware deliveries
> > before we can recover that service.
> 
> The KVM developers suggest a virtual machine in the meantime?
> 
> > I suggest you ask KVM developers
> > where they would prefer to have the bug reported.
> 
> Ren, please use the qemu bug tracker temporarily, just make sure to mark
> it as a kernel bug.
> 
Thanks, Avi and Konstantin.
I'll use qemu bugzilla to track kvm bug temporarily.

> > Sorry for lack of responses -- the holidays always make it more
> > difficult to respond in time.
> >
> 
> Thanks.
> 
> --
> error compiling committee.c: too many arguments to function

��.n��������+%������w��{.n�����o�^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux