z-logo
Premium
Identification of New Alleles for Resistance to Soybean Mosaic Virus in Soybean
Author(s) -
Li D.,
Chen P.,
Alloatti J.,
Shi A.,
Chen Y. F.
Publication year - 2010
Publication title -
crop science
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.76
H-Index - 147
eISSN - 1435-0653
pISSN - 0011-183X
DOI - 10.2135/cropsci2009.06.0302
Subject(s) - soybean mosaic virus , germplasm , biology , allele , potyvirus , potyviridae , resistance (ecology) , horticulture , plant virus , botany , genetics , virus , agronomy , gene
Soybean mosaic virus (SMV) is one of the most prevalent viral diseases in all major soybean [ Glycine max (L.) Merr.] growing areas worldwide, causing substantial yield losses and seed quality deterioration in soybean. Seven strain groups of SMV (G1–G7) in the United States and three resistance loci ( Rsv1 , Rsv3 , and Rsv4 ) have been identified in soybean. The objective of this research was to screen diverse soybean germplasm in attempt to identify new alleles for SMV resistance. A total of 253 soybean accessions collected from 26 countries were screened with six SMV strains in the greenhouse. The results showed that 157 accessions were susceptible to all six tested SMV strains, 75 accessions were resistant to some of strains, while 21 accessions were resistant to all strains tested. Among the resistant accessions, seven showed complete resistance to six strains and presumably carried Rsv1‐h , Rsv4 , or combinations of Rsv1 , Rsv3 , and Rsv4 ; 14 showed resistance or early seedling stage resistance to six strains and presumably carried the Rsv4 allele; 50 accessions exhibited similar reaction patterns to known alleles: two Rsv1 , 22 Rsv1‐k , 16 Rsv1‐y , one Rsv1‐t , and nine Rsv3 Twenty‐five accessions showed distinct reaction patterns and presumably carry new alleles. The resistant accessions identified in this study will be valuable germplasm resources for breeding SMV resistance.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here